[oddsockmachine]

I'm already seeing this in the company I recently joined: 80-90% of code is generated/prompted. Big PRs, very little review or oversight. Absolutely nobody considering long-term architecture (and IMO nobody capable of such). In general, there's very little critical thinking involved at any stage, just throw error messages back into the LLM, rinse and repeat. I'm hoping there's a world where people with skills are useful in getting these projects back on track, but perhaps as a society we're learning to accept this reduction in quality.

[weatherlite]

And how do u sum up the tradeoffs so far, or is it too early to tell ? Do u see lots of unacceptable shit making into production that wouldn't have before A.I for example ?

[oddsockmachine]

Observations so far:

- "micro" level code is adequate. A new feature typically works as expected, and code is well documented. But macro level everything's wacky: no architectural consideration, lots of duplication, dead end paths, dead code. Nobody ever took the time to understand the context surrounding a change and figure out the most appropriate way to integrate it.

- there's no consideration for infrastructure, or how the code is run (my world). Last week we ddos'd ourselves after someone implemented a 1/s poll that runs on every open browser tab, worsened when the frontend's reconnection logic fired 1/s with no exponential backoff.

- zero critical thinking... First thing everyone did during that incident was to ask their LLM of choice why the platform was down. Investigating by hand (and my findings thereof) was dismissed, because surely Claude knows best.

I'm too old for this stuff.

[whateveracct]

Your codebase is essentially becoming bytecode