The debugger doesn’t even come close

All the good borland devs were poached by Microsoft. VC5 and 6 were the spiritual successors of the Turbo XXX family of IDEs.

Here's one that hit the frontpage recently:

https://blog.k10s.dev/im-going-back-to-writing-code-by-hand/

That's indeed a good example.

However I find their claim "I've lead teams of really competent engineers and I can leave them without supervision for months and come back and not feel like throwing away the entire code base." dubious. We all know how much effort it is to keep the quality of even small patches consistent.

Design, architecture, style and refactoring still require significant involvement. Providing only a description and a criteria will likely produce hopelessly messy code, which is also what you get with most corporate dev teams.

Litigation

> This requires using the extremely unintuitive `git rebase --onto A B C` invocation.

Unintuitive yes, and I'm not going to disagree with you on UX, but it's not a particularly difficult thing to learn if you use a rebase centric workflow and this is a command I use daily.

P.S. don't forget to use --update-refs (or add to your .gitconfig) ;-)

> Not any more.

`git add -p` FTW

Large volumes of training data is a blessing and a curse, especially when you consider who wrote it.

> Changing the default behavior for all of your users with no notification is pretty unforgivable

How else is a poor programmer gonna hit their KPIs and get that promo?

> Analyze if it's malware how exactly?

By spending thousands and thousands of tokens of course :-)

Can we get OpenCode support back as well?