Jrockwar

Interestingly what I’ve said here ☝️ ️comes with an interesting implication. There used to be a type of software “engineer” that couldn’t actually think through a problem and implement a good software solution. They were valuable because they could refactor, write code, but not think through a problem. These are the people who have the most to lose at the moment, and also the ones that find the least value on AI, because AI only does really well the single thing they could do.

I appreciate the intent behind that sentence, and the problem is that is written (or said) by people who don’t understand coding.

Syntax was never the hard part. Code syntax is a set of rules that you can teach a machine and it’s “easy” enough for an LLM to grasp it. The problem here is that this phrase does a “code = syntax” but ignoring all the difficult things that actually are in the code. Architecture, design, tradeoffs, translation of vague requirements into concrete software components…

All of those things are terribly hard, and the reason why many LLM-first coding projects get abandoned at 70% and then companies need to hire a Software Development consultancy to mop up their mess.

What they forgot to add: in the same time, they’ve also managed to create more bugs than they’ve fixed, thanks to AI.

Well, MacBook Pro or also Mac Studio. Pre shortage, you could spec out the Mac Studio with 512 GB of RAM, if you had stupidly deep pockets.