ignassew retweeted
Reminder: this is all fake. Any time someone makes a claim like this, either they are lying, or every single programmer they know is completely awful and can’t program at all.
xitter.cf/alexalbert__/status/19…
Since Claude 4 launch: SWE friend told me he cleared his backlog for the first time ever, another friend shipped a month's worth of side project work in the past 5 days, and my DMs are full of similar stories.
I think it's undebatable that devs are moving at a different speed now. You can almost feel it in the air that this pace is becoming the default norm.
Replying to @thdxr
Have you tried next-ai-news.vercel.app? Everything is dynamic, zero caching, fetches from Postgres, all RSC, auth / identity on every page.
If a navigation is slow it’s one or more of;
- They’re not prefetching
- They don’t have fallbacks / loaders
- They have slow backends
ignassew retweeted
It's game over. We're toasted.
TODO: Buy the best rig on the market today. Download all software ever written by humans and still functional. Turn off the internet. Enjoy while it lasts.
Suppose that you need to write a 1000-LOC function. You ask Grok3, and it fails. In that situation, most devs would fallback to coding manually. I argue that, instead, they should keep giving the AI info, until it succeeds.
"Why? Won't it be faster to just type the 1000 lines?"
In some cases, perhaps. But you still want the AI to do it, because AIs are *way* less sloppy than humans. They don't flip arguments nor make silly syntax errors. They fail for different (and even complimentary) reasons that humans do: AIs fail because of bad reasoning.
So, if you just take charge of the reasoning, you can get the best of both worlds: your code will be in the perfect "AI-generated" shape, and it will have the correct logic, feed by you. This works very well for any reasoning model that exposes its thinking traces, because you can see clearly *why* the AI failed.
"Oh, Grok3 spent half of the reasoning trying to figure out where ids are stored. Well, I can just add that to the prompt, and try again."
Writing lines manually in 2025 is a harmful, fallback practice.
ignassew retweeted
Giving very young kids access to real laptops with high ceiling video games is such a cheat code. My kids bootstrapped reading, math, spatial reasoning, etc, just because they had a *need* to do it since the carefully chosen games I've put them in front of *demand* it of them.
ignassew retweeted
HELP PRESERVE OUR LIMITED SUPPLY OF UUIDS! instead of generating a new UUID, try to reuse one you already have!
We hired a part-time developer to help with the frontend. He worked at Klarna and did very well in the interview. After joining, he insisted we switch to next, started rewriting everything from scratch without approval. Couldn't even fire him, the guy just vanished 3 days later.
ignassew retweeted
this is actually amazing and also completely obvious
Just realised what a terrible person I am for not providing the copy-paste version, here it is:
cat ~/.zsh_history | awk '{print $2}' | cut -d";" -f 2 | sort | uniq -c | sort -nr | head -10





























