It's been a while...
Introducing Devframe v1.0 🚀
The framework for building DevTools that can run everywhere, for any meta-framework, for both humans and agents.
Check out the announcement post and join our Discord 👇
https://t.co/IbZeGwemRe
🚨🎙️ Lionel Messi on the Ballon d’Or:
“I’m honestly very grateful to be nominated again. To see so many legends and former players supporting me, wanting me to win and rooting for me means a lot. I don’t take that love for granted.
“But if I’m being completely honest, I feel like I’ve done enough. I’ve won this award, I’ve achieved almost everything I dreamed of in football, and I don’t feel like I have anything left to prove.
“Of course, winning it would always be special, but at this stage of my career, I would actually be happier seeing a new player lift it. There are so many young talents who are doing incredible things and deserve their moment.
“If my name is called, I’ll appreciate it. But if it goes to someone else, I’ll be just as happy. Football is always moving forward, and sometimes it’s good to let the next generation have their moment.”
I built my last project entirely with Claude Code. I didn’t write a single line of code by hand.
It still took me nearly 3 months.
Why so long and not a day or week? Because building serious software has never been just about typing code.
Early on, there are tons of unknowns. As you build, test, and get feedback, you discover problems and requirements you couldn’t have anticipated.
I spent a lot of time reviewing Claude’s work, not line by line, but at a higher level: the approach, architecture, and design decisions. I constantly challenged it, debated its choices, and pushed for simpler, more robust solutions.
That’s software engineering.
AI helped me bring my vision to life without spending countless hours typing code, wrestling with syntax, searching through documentation, and figuring out the mechanics of how to implement things. Without AI, building this app would have taken me 5-6 months if not longer.
As I’ve said over and over, software engineering is not going away but AI is changing _how_ we build software. The tools are changing and the engineer’s role is evolving.
And this is why knowing how to build good software still matters.
You may not need to remember every API or piece of syntax anymore, but you still need to understand things like separation of concerns, coupling and cohesion, abstractions, data modeling, API design, error handling, security, performance, and testing.
When AI proposes an architecture, creates an abstraction, adds another layer, or introduces a dependency, you need enough engineering knowledge to ask: Is this actually necessary? Is there a simpler way? Will this scale? Is this secure? Will this become a maintenance nightmare six months from now?
AI can write the code. You still need to know what good code and good software look like.
I’m so glad your attention has been drawn to this situation at hand because I’m patiently waiting for MTN’s deadline to elapse before bringing it to your attention.
If you’re a victim of MTN’s data depletion, kindly fill this link https://t.co/kI0NOyRhOu
The first thing I do before building a feature is design the URL.
So I opened @v0 and made the URL visualizer I was always missing.
https://t.co/gHn3Y2bSJ3
Man, I love this stuff.
If I want to code by hand, I code by hand. If I want to code with AI, I code with AI. If I want Omarchy, I use Omarchy. If I want to build my own rice from scratch, I do that too. Rust one day, Java the next.
Don't forget why you got into tech in the first place. Remember that joy you felt writing hello world for the first time, or discovering that distro that just clicked, or trying out a keyboard that felt perfect?
It was euphoric. So why try to take that away from someone else?
Have opinions, argue about what's better, whatever. But I'll never understand being so judgmental toward someone for enjoying tech differently.
Some of y'all just need to roll one up and watch Surf's up or something.
Watching devs slander “vibe coders” is so tiring.
Sure, if you really want to prove a vibe-coded app is “bad,” you can run load tests until it blows past its DB connection limits, inject network chaos to expose missing circuit breakers, run 48-hour soak tests to uncover memory leaks, or audit a monolith under 50k users for unindexed queries, N+1s, row locks, thread starvation, and broken cache invalidation.
And after all that, you might discover something uncomfortable: 95% of software doesn’t need any of it.
Most people vibe coding aren’t trying to build the next Google. They’re turning an idea into functional software for 50 users, solving a problem, learning, or just having fun.
Software engineering is much deeper than pulling out enterprise-scale benchmarks to dunk on something someone built on the internet.
There’s distributed systems, performance engineering, databases, compilers, networking, concurrency, system design, and a thousand genuinely hard problems to master.
You don’t need to fight vibe coders to prove you’re an engineer.
Let people build. Then go build something hard yourself.
We all have ideas. Ideas are immortal. They last forever.
What doesn’t last forever is inspiration. Inspiration is like fresh fruit or milk: It has an expiration date.
If you want to do something, you’ve got to do it now. You can’t put it on a shelf and wait two months to get around to it. You can’t just say you’ll do it later. Later, you won’t be pumped up about it anymore.
If you’re inspired on a Friday, swear off the weekend and dive into the project. When you’re high on inspiration, you can get two weeks of work done in twenty-four hours. I
Inspiration is a time machine in that way. Inspiration is a magical thing, a productivity multiplier, a motivator. But it won’t wait for you. Inspiration is a now thing. If it grabs you, grab it right back and put it to work.
Inspiration is perishable.
WOW! Maybe we should make this the start screen?? Actually, yes. Yes we should. I'll find a way for this video to run as a video desktop one time on first boot. Bring the SIZZLE 🔥