Hacker News new | past | comments | ask | show | jobs | submit
This is everywhere to my knowledge, and engineers are burning out left and right with stress because of how little anyone understands the code, and how much of a mountain of nobody knowing anything they have to handle. We are turning our critical infrastructure mechanisms into stochastic grey goo.

I find the engineers currently thriving are the ones who never gave a fuck about anything but their own advancement and are happy to drop weeks of work on others and take the credit.

> I find the engineers currently thriving are the ones who never gave a fuck about anything but their own advancement and are happy to drop weeks of work on others and take the credit.

Yes. if you have this attitude, great things will come to you. if you care or try to make sense of things, you'll be in misery

> how little anyone understands the code

Everyone's doing code reviews--well, not even code reviews; just PR reviews--so how are they supposed to gain an understanding of the system.

I review a PR, I see that one new endpoint was added to the API. It looks correct. I say "LGTM" in a GitHub comment.

The sprint's almost over, everyone's in a rush to do code reviews.

I look at another PR. Somebody added a button to the UI. The button looks correct. They get a thumbs-up emoji from me. I bet they feel satisfied.

I look at another PR. Somebody changed a timeout in the settings because some people complained about dropped connections. It's a really small change, so, approved.

At what point am I supposed to understand the system? I looked at a single API endpoint, in isolation, and then a button, and then a harmless looking settings change.

I was pressured to hurry.

Am I supposed to somehow get an understanding of the big picture through this?

Imagine if instead there was time to review large logical sections of the code together. Imagine if we focused our reviews on the overall code instead of on the lines in one random PR at a time.

loading story #50542689
loading story #50547979
loading story #50542019
loading story #50551035
{"deleted":true,"id":50541508,"parent":50539955,"time":1794972674,"type":"comment"}
Understanding is overrated, application code (user-space) is anyway just a way to make money. If you're making more money over time, you're doing it right. We're not writing kernel code or safety critical code, we can let AI do the heavy lifting of putting characters into a file.
loading story #50541100
loading story #50541644
There are plenty of apps that while not safety critical, are financially critical to people's lives. When you're working on an app that processes billions of dollars in payments per month you can't just yolo it.
loading story #50541830
It’s funny that anyone still thinks that these practices aren’t being applied to safety critical code in order to make money.
loading story #50541033
loading story #50543139