Building enjoy.dev - the best way to build with AI. Yapping at piped.video/@lessbitter, piped.video/@atmoio, and shipacademy.com.

Pinned Tweet
I’ve spoken to over 50 people 1:1 over the last several months to better understand how they code with AI. It’s an absolute mess. Here are the top 8 mistakes I see. 0:00 - Intro 1:19 - Mistake 1: Talking to 2026 models like they’re 2025 models 2:43 - Mistake 2: Devising funky metaphorical factories to orchestrate your agents 3:59 - Mistake 3: Treating context as sacred 6:02 - Mistake 4: Treating previous conversations as sacred 7:59 - Mistake 5: Having a todo list 10:00 - Mistake 6: Using funky tools 13:47 - Mistake 7: Stressing over code quality 24:27 - Mistake 8: Using branches and worktrees
169
127
1,901
328,720
Claude Ultracode is super intelligence.
230
296
4,162
512,375
Does a CEO need to understand his employees’ code? Vibecoding is 2025. Evolutionary coding is 2026. Let the code’s DNA evolve to find solutions that satisfy environmental pressure (tests). Genomes are an absolute mess but they work.
I have a very strong feeling that these voices that says "Do not look at the code or code doesn't matter" will fade away soon. There is no freaking way you can build, maintain and operate products where you don't understand or can't reason about your own code. Code quality isn't only about its visual appeal, it's also about understanding how the heck everything works. And all these "Explain the codebase" skills are pure headache.
63
10
172
26,500
i'm tempted to soften the message around AI doomerism and say, look! everyone gets more leverage now! if you were 1x you're 10x now! but in the real world technology can displace. amazingly it's still not clear how AI will affect developers/designers/knowledge workers. this lack of resolution is reassuring. it might mean displacement is a myth. or maybe the models really sucked up until literally this month. that's a real possibility. i do know this: if you wanted to hire someone to pentest your server, would you rather hire a designer with AI, or a security researcher with AI? and if you wanted a design that converts, would you want a backend engineer prompting it, or a designer/marketer? one thing is certain: generalists can now rule the world.
57
12
340
22,949
Designers quoting this hanging on for dear life reminds me where most developers were in late 2025. “There’s more to design than X or Y.” “Sure AI can do A but can it do B??” Developers have since learned not to set aside particularities as reserved domains. It’s a strange new world. AI is better than us at most things. It’s super bitter. It’s super bizarre. It’s super science-fictiony. There’s lots to argue about AI. But technical superiority is no longer one of them.
I've worked with brilliant designers in my life and Astra/Opus outshine them 10x when it comes to not only design aesthetics, but remarkably creative UX solutions, in 1/1000th of the time. If we were being doomerish about it, Astra and latest Opus mark the death of designers the way models in 2025 ended coding.
58
6
231
61,038
I've worked with brilliant designers in my life and Astra/Opus outshine them 10x when it comes to not only design aesthetics, but remarkably creative UX solutions, in 1/1000th of the time. If we were being doomerish about it, Astra and latest Opus mark the death of designers the way models in 2025 ended coding.
183
36
995
360,165
On the other hand, if the agents are doing all the coding, wouldn't you rather hire a designer who can prompt, than an engineer who can prompt?
17
3
157
28,146
Agent code quality may look worse to a human observer, but in my experience agent build quality is better. Features have less bugs on launch and tend to "just work", whereas human-driven builds always tended to be myopic and fail for embarrassing reasons.
It takes a while to build the confidence, but there's no future where you're manually reviewing every line of agent code. Not much acceleration in that. You need adversarial agent reviews, you need automated testing, and maybe you spot check. That's it. From prompt to production!
61
16
400
42,207
Humans were so bad at coding that companies had to use React Native because two native apps was just..too much. It was too much.
42
22
527
58,921
In theory you can now just build the iOS app carefully then have a fully autonomous agent build and keep the Android app in sync.
10
63
7,998
Best early SaaS advice: Don’t offer an annual plan. Monthly only.
147
21
1,322
116,212
New products are riddled with subtle UX frustrations and onboarding issues that will tank your entire operation if you wait a full year to find out churn.
9
3
164
13,571
If you set aside the politics, the propaganda, the fear-mongering, the economics, and the intellectual property theft, AI is pretty cool. It really shouldn't be possible. It shouldn't work. But these fuckers can use computers like Pantheon uploads.
16
10
184
25,573
I’ve spoken to over 50 people 1:1 over the last several months to better understand how they code with AI. It’s an absolute mess. Here are the top 8 mistakes I see. 0:00 - Intro 1:19 - Mistake 1: Talking to 2026 models like they’re 2025 models 2:43 - Mistake 2: Devising funky metaphorical factories to orchestrate your agents 3:59 - Mistake 3: Treating context as sacred 6:02 - Mistake 4: Treating previous conversations as sacred 7:59 - Mistake 5: Having a todo list 10:00 - Mistake 6: Using funky tools 13:47 - Mistake 7: Stressing over code quality 24:27 - Mistake 8: Using branches and worktrees
169
127
1,901
328,720
i'm appalled by how solo builders are approaching agentic engineering today. i've spoken to several people over the last couple months 1:1 to get an idea for how they're building with AI. every single one of them is vibecoding like it's january 2026. they're writing huge specs. they have a kanban board neatly organized with hundreds of todos. they're having their agents take detailed notes after every change. i'm like, what are you doing?? why are you giving it specs? why do you have a todo list?? if you're starting a business, code is the least important part. half of these people are worried about AI code quality. i'm like, what are you talking about?? why the fuck do you care about code quality??
266
25
1,142
262,641
It's impossible for Jev to be good.
93
53
1,096
103,548