885 karma · joined August 5, 2024
Exactly. Which is the reason why code that increases maintenance friction and costs, or decreases the product's operability or fitness for purpose, does not properly serve the end of advancing the business. Not in competitive industries anyway.
There's this whole manufactured narrative going on geared toward reframing the quality of code design and structure as an aesthetics problem. If you think code design and structure is an aesthetics problem, you will not understand the pushback.
A much more interesting question, I think, is why bad AI code is perceived as a worse problem than bad human code.
My observation is that bad human code ultimately slows down its own maintenance: the speed at which the human can add bad code decreases as the human adds more bad code. So it's a self-limiting problem. Whereas AI will quickly and efficiently add extra layers of bad code to work around the issues introduced by its own earlier bad code. If you let that go on, you can end up in runaway complexity scenarios where only AI can maintain the code at all, until even it can't. There have been a lot of arguments on HN that such scenarios are not a problem because AI will keep getting better, but to me this amounts to a Ponzi scheme for tech debt, which I find undesirable.
And that's not to even mention the externalities.
So, basically, depending on whether you care about all of the above, or not, the machine that supercharges your LoC-per-day metric will be seen as a good thing or a bad thing, and it's not a divide that can be reconciled because it boils down to what individuals care about. We can all agree about the end of writing code, but that doesn't mean you can't be wrong about the ways to get to that end, I guess.
So, cool nerdy blog posts on HN, cool nerdy puzzles on Cracking the Cryptic, etc.
Having been sorta involved in hiring in the same sorta market, I can respect how astute their approach is.
I wonder how widespread that phenomenon is. Perhaps it's no wonder the prominent actors are trying to rush to IPO...
Not saying they're equivalent, local models still decohere much quicker as the context grows in my experience. But... Interesting.
I started doing exactly this and it's been invaluable.
The hardest thing in software engineering is solving the right problem. The ability to identify the right problem to solve, is IMO, what distinguishes the top senior engineers. And we could have endless discussions about what constitutes the right problem, but for the sake of this discussion, let's reduce it to: the problem whose resolution adds the most value to the product for the amount of complexity and afferent costs that it incurs.
Once upon a time, long ago, I worked on a Web product whose original junior designer had figured it would be neat to be able to manage the backend with LDAP tools. So the database schema and structure that the product used mimicked that of OpenLDAP, with compound CN keys, and the entire codebase had to deal with that structure whenever reading from or writing to the DB. LDAP compatibility was not the right problem to solve when designing the DB schema.
But software that solves the right problems can be hard to identify because, quite often, how it does things seems so obvious that it's not readily apparent what other designs might have been chosen.
Now, the thing that usually keeps the blast radius of wrong-problem designs limited over time, is the very friction that they introduce. Development slows down, including the development of more wrong-problem designs. It's a self-limiting phenomenon.
And that's one major thing which worries me about LLM coding agents:
They paper over this friction. They don't repair it; they just make it so its cost is deferred.
So you gradually end up with codebases that grow unboundedly complex for the value they provide, with no controlling mechanisms.
You end up with juniors who never face the feedback loop from which they'd develop the engineering instincts and the taste for what makes a problem the right problem to solve in a given design.
At scale, as a field, you might end up forgetting there ever was such a thing as solving the right problem.
And I don't know what to do about that. Plan for an early retirement, maybe.
[1] https://www.reddit.com/r/programming/comments/1tapmvi/mass_n...
Do you perchance have a source for this? Is the profitability assessment comprehensive, including hardware amortization? I've found it hard to track down actual hard numbers for the cost of inference.
Because self-determination was the defining component of every agile deployment I've ever been involved in or personally driven. I don't think I can really picture what something calling itself agile yet lacking this component would even look like, honestly -- hoping you will forgive me this failure of imagination.
By construction, nothing in the game is far away. You're only limited by how much you've figured out. And having the spark of understanding occur can take place at any time, including while you're away from the keyboard.
So it's mostly about following your curiosity wherever it leads you, and from there you keep digging all the way, safe in the knowledge that in 22 minutes at most any screwups will be rolled back. And then you can try again, or, better follow your curiosity somewhere else. There's no lack of things to figure out, and some of them are completely optional. But... Figure them out anyway, the reward is worthwhile.
"Thank you for remembering me."