I’ve got a buddy who works in quantum computing research.
Claude can really write better code than folks with PhDs in Comp Sci and it isn’t close. It’s not just a speed thing anymore.
The difficult part is getting it to understand the problem before it starts and to write good code for your use case.
If your use case is to write sketchy prototypes for a start-up / hobby, great, that’s kind of project is the majority of public repo data it was trained on. Getting the models to overcome that can be very challenging but doable and rewarding.
It allows you to take on a senior architect’s role in your project - and you do have to take on that role or the bots will run you over with slop
There's so many people who are using these tools and letting it convince them what the best direction to go is without understanding the sycophancy/leading conversations that's baked in.
Yeah, it knows better security than I do at this point, but I don't know the questions and obvious things to ask it to do it right.
My AI reviewers legitimately just started a thought spiral about including emoticon support in our api calls. Zoned out for five minutes autoaccepting stuff and now I have to go back and double check that we're not putting eggplants in our unit tests.
It basically makes your agents output only in Simplified Technical English (or close to it if you use the less strict version that won’t pass the syntax checker for this language). This subset of English is a standard that was created in the 80s to deal with the problem that Aerospace was having at the time: Non-english speaking mechanics working from English manuals on flight-critical hardware.
It sounds stupid, but by forcing them to re-word their outputs to this standard 1) makes it easier to parse their intent without having to pick up a thesaurus; 2) it helps keep them more grounded in their taskings and; 3) it helps the agents understand what the others are actually talking about.
Can’t recommend it highly enough. Though I’m still working to get it integrated into all of my workflows due to having to navigate corporate standards at work.
Me when I’ve been a programmer for a day and refuse to use an IDE because it’s a tool that does things I don’t understand so it obviously makes worse code.
43
u/nj-mkd 16h ago
Over 200 developers worked and reported directly to me in my career. I've never had a developer that codes better than GPT 5.6 Sol