Never forget that LLMs are just next token predictors. The harnesses are what's getting uncanny. And credit/blame assignment? Just assign a surrogate for now, let them deal with the consequences ffs.

It's not like we're in a rush to bring software out there asap, and we still have some people who measure software success by LoC. Something doesn't add up.

If you already juggle multiple dependencies in your life (small children and/or in school, elder care, other dependents and special situations, dual study), or simply have too many interests, hobbies and love to do more things outside your work, remote work just feels revolutionary, to the point you just resent going to the office.

Having AI generate massive code and shoving it to your teammates' plates should be considered irresponsible. Yes, test code is verbose, but it should be accompanied with an adequate description of what is currently tested. Otherwise it's just AI having fun in your codebase.

Automated PR merges could still work, please just don't with multiple thousands of LoC changes. Both LLMs and humans have a context size limit.

Producing massive changes in a codebase has never been impressive. LoC has always been a bad measure of progress, and yet, modern frameworks, popular tooling and haphazard business logic almost dictates that you blurt out as many LoC as possible. Software engineering wasn't supposed to be this verbose.

See, I didn't need to write in German, but you instantly understand my point better. Gleich und gleich gesellt sich gern, that's also true when it comes to speaking the same language. But you can't create born-and-raised Germans from immigrant adults, and attempting to fix them at every opportune moment just gives the impression that being better at German somehow gives you an air of superiority. In some cultures, this is just straight up bad manners, so is quoting single sentences and writing essays about them while missing the forest for the trees.

You missed the point. Just take an immigrant in front of you next time and see him make two mistakes in a row in one sentence while casually talking to him (maybe he's tired, maybe he's lazy but who's to judge). You'd inherently think less of him, deep down, wouldn't you?

If you live in an unfurnished apartment or buy your own sooner, then you also get to see how the service sector currently sees all white-collar workers: Cash cows who don't know how to hold a screwdriver properly. Add on top of that the joys of building a family in Germany and the associated paperwork and multiplying appointments, and suddenly you find yourself living that NPC life, being yelled at on the street for insisting on their rights, misreading the situation and thinking you broke the most superficial law. While having the privilege to pay into the tax system that drains your take-home pay, of course. Being a rule follower yourself doesn't always shield you from all these.

That's PoC-level, happy-path-only engineering and LLMs are very dangerous at inserting subtle hardcoded values and cheats along the way, which makes it really hard to spot them later on. You need a system to whack them before they infect your codebase terminally, be it hyper vigilance, more SCA, more TDD, SDD... Otherwise you'll wake up one day with a production incident at 3 am and wonder how that code was even allowed in the release bundle.