This really got drilled into me after working in blockchain because your software might work perfectly on one node, but when you have 100+ nodes, you can see race conditions show up and they create obvious discrepancies which can create forks in the network. In fact any non-deterministic logic will create obvious forks. Building software that's fully deterministic is very difficult and you have to go against a lot of what you were taught.
There are very few software engineers who can write good code and I think a lot of it comes down to caring.
From the engineer's point of view, there are conflicting incentives and unfortunately, businesses have been rewarding the wrong ones. Most business leaders think of a star engineer as someone who can churn out large PRs rapidly, solving issues one after another. It's a dangerous way to look at it. Such engineers are almost certainly creating a lot of tech debt. TBH, I don't think this makes sense, even for startups, because the tech debt comes due much sooner than you'd expect and the costs compound rapidly and usually permanently.
The irony is that large PRs delivered at a rapid rate makes it look like the engineer cares about the project's success, but actually it's often the opposite; they do it subconsciously because they care about themselves and their lock-in factor. They know that complexity is how they can claim ownership over the code base.
I observe a similar dynamic with business people; some business people are laser-focused on value-creation, but many others are laser-focused on retaining control and will happily throw value-creation under the bus at the drop of a hat.
Unfortunately I feel like the past 10 years have significantly favored the value-extractor at the expense of the value-creator.
Also, I feel like AI has been creating more harm than good, in the hands of the average developer, because it tends to go for the complex solution and has a tendency to patch things up with more complexity instead of avoiding the problem altogether. AI agents do not value determinism enough. It's crucial to producing correct software.
Yeah, but I've worked at places which don't even care about the tech debt. Unless it's affecting the bottom line, we as engineers are implicitly told to just put up with it. From a business perspective I get it, though it's short-sighted... but from an interpersonal perspective, it's not right.