>The engineers who thrive will be the ones who can resist the temptation to over-engineer when the marginal cost of adding complexity drops to near zero.
I think this isn't being discussed enough in the SWE world. It wasn't too long ago that engineers on HN would describe a line of code as "not an asset but a liability". Now that code is "free" though, I'm seeing more excessively verbose PRs at work. I'm trying to call it out and rein it in a bit but until engineers on average believe there is inherent risk here, the behavior will continue.
I'll read more of the articles but very first bullet point raised my eyebrows
>Freezing Russian reserves in 2022 introduced confiscation risk to assets previously considered risk-free
Is this actually new? Didn't we freeze Iranian assets back in 1979? Wouldn't be surprised if there were other examples.
There's an older article that gets reposted to HN occasionally, titled something like "I hate almost all software". I'm probably more cynical than the average tech user and I relate strongly to the sentiment. So so much software is inexcusably bad from a UX perspective. So I have to ask, if code will really become this dirt cheap unlimited commodity, will we actually have good software?
> To be fair, I was able to get it to work pretty well after giving it extremely detailed instructions and monitoring the "thinking" output and stopping it when I see something wrong there to correct it, but at that point I felt silly for spending all that effort just driving the bot instead of doing it myself.
This is the challenge I also face, it's not always obvious when a change I want will be properly understood by the LLM. Sometimes it one shots it, then others I go back and forth until I could have just done it myself. If we have to get super detailed in our descriptions, at what point are we just writing in some ad-hoc "programming language" that then transpiles to the actual program?