This year's coding agents are good enough to make large-scale code migrations a solved problem. See Bun's 500K-line Zig-to-Rust rewrite. Now the bottleneck is what happens after you move the mountain of code. An agent may write a million lines and make the tests pass. 1/3
2
4
27
4,998
But what do you do after that? And how do you approach this if your test coverage is thin? Here's how we migrated lovable.dev (400 routes, 850K lines, 42M monthly visitors) from Next.js on Vercel to TanStack Start hosted on Lovable itself. 2/3
1
10
279
In 20+ years in the industry, I've never seen software development change as fast as it's changing today. Lovable is a cool place that lets you work at the cutting edge and find out what the future of software development looks like [1/2]
1
4
24
4,595
AI writes 90% of my production code now. Speedup: 3-4x for prototypes, but only 1.5x for prod. The bottleneck moved from writing code to reviewing it. You still have to read every line. Field notes from 6+ months of coding with agents: 1/x
1
1
74
On code review: It's the new bottleneck. Every agent gives you a week's worth of not-great code in hours. You have to review it all. Your team has to review it all. Stacked PRs, better PR hygiene, AI self-review all help. 3/x
1
52
Full post: quality, testing, code review, team dynamics, and what actually changes when agents write your code: open.substack.com/pub/alexan…
41
Alexander Lebedev retweeted
Only brave and skilled designer+developer can win the battle against IE7/IE8 incompability. I hope one day that skills would become obsolete
1
Great languages still have ugly aspects. #python datetime libs suck and #ruby unicode support is even worse
Never try updating data in two external systems within single transaction. This is very fragile and you'll regret it deeply.