Doctors and lawyers are also going away, it’s just harder to see as they’re not exposed as much to this technology yet, it’ll be more of a “flip a switch” moment for them.
Doctors might fare better since there are laws and regulations that require them.
They didn’t have to, they decided that it’ll be more stable to revert them for the holidays, so that they won’t be in the office fixing issues on Christmas.
Used Claude Code until September then Codex exclusively.
All my code has been AI generated, nothing by hand.
I review the code and if I don’t like something- I let it know how it should be changed.
Used to be a lot of back and forth in August, but these days GPT 5.2 Codex one shots everything so far. It worked for 40 hours for me one time to get a big thing in place and I’m happy with the code.
For bigger things start with a plan and go back and forth on different pieces, have it write it to an md file as you talk it through, feed it anything you can - user stories, test cases, design, whiteboards, backs of napkins and in the end it just writes the code for you.
Works great, can’t fathom going back to writing everything by hand.
Glad to hear. For me, the process does not converge — once code gets big enough (it happens fast, claude hates using existing code and writes duplicate logic every oportunity it gets) it starts dealing more damage every turn. At some point, no forward progress happens, because claude keeps dismantling and breaking existing working code.
Okay but has this process actually improved anything, or just substituted one process for another? Do you have fewer defects, quicker ticket turnaround, or some other metric you’re judging success?
Oh yeah, I’ve been a lot more productive, closing tickets faster.
These tools are somewhat slow, so you need to work on several things at once, so multitasking is vital.
When i get defects from the QA team, I spawn several agents with several worktrees that do each of the tickets- then i review the code, test it out and leave my notes.
Closing the loop is also vital, if agents can see their work, logs, test results it helps them to be more autonomous
I started in July-August and it’s a learning curve, you start with “i’ve got all the power” and gradually learn the limits of the AI models, so you start closing the loop and getting them what they need to make sure that they’ll output what you consider acceptable.
With each new drop, they become more and more powerful, so it’s easier and easier to jump in.
Follow him and https://jeffreyemanuel.com/ on X to keep up to date on the latest and most advanced techniques to work with AI. Learned a lot from them.
Is it not rather the opposite? His striving for unconventional "taste" (as opposed to boring convention) was probably a factor in him seeking "alternative" medicine.
in some sense i think it shows having taste. sometimes taste can be dangerous. you can only have a taste for say rock climbing equipment, by rock climbing, which exposes you to danger.
Presumably hot reload and IDE integrations that actually work. Xcode is really crappy compared to other IDEs, so platforms that can avoid it for most of your work tend to be an advantage. Xcode 26 generally broke anything that relies on indexing, like autocomplete, edit in scope, or refactoring, among others.
> React Native is popular because there’s a thousand times more React devs than native devs.
Exactly this. And they come cheaper. JS dominance in development stems from business logic, not from quality of development environment or tools, or developers preference.
reply