It's totally fine to say "the code works, that area is stable, let's not mess with that code". I make those kinds of tradeoffs on a near daily basis. But let's be real, "perfectly functioning code" is an ill defined, moving target. What looks like perfectly functioning code to a sibling team or a PM, could be a massive liability to someone who actually knows the code.

But then again I'm writing OS and performance critical code. A 1 in 1 million bug is easier to ignore in a throwaway log viewer website.

Let’s not nitpick here. Worldwide human suffering and tragedy is equivalent to the end of humanity for most.

We can sit here and armchair while in the most prosperous, comfortable era of human history. But we also have to recognize that this era is a blip of time in history. That is a lot of data showing humanity surviving sure. But it’s also a very small amount of data showing any kind of life most would want to live in.

Many people online share similar experiences. Wonder how much money this wide-scale fraud saves them.

You're right, human review and thorough design are a poor approximation of proving assumptions about your code. Yes bugs still exist. No you won't be able to prove the correctness of your code.

However, I can pretty confidently assume that malloc will work when I call it. I can pretty confidently assume that my thoroughly tested linked list will work when I call it. I can pretty confidently assume that following RAII will avoid most memory leaks.

Not all software needs meticulous careful human review. But I believe that the compounding cost of abstractions being lost and invariants being given up can be massive. I don't see any other way to attempt to maintain those other than human review or proven correctness.

In other words you can’t vibe code in an environment where evaluating “does this code work” is an existential question. This is the case where 7k LOC/day becomes terrifying.

Until we get much better at automatically proving correctness of programs we will need review.

> According to the Numbeo Health Care Index in 2025, Taiwan has the best healthcare system in the world, scoring 86.5 out of 100,[6] a slight increase from 86 the previous year.[7] This marked the seventh consecutive year that Taiwan has ranked first in the Numbeo Health Care Index.[8]

Other engineers I've seen (a smaller sunset) have that job description more as an observation of their skills and influence. Their mandate isn't to influence, they just do. They are respected for their vast knowledge, historical success, and insight. So they naturally are heeded by most, and consequently they broadly influence the org.

Both cases sound miserable in their own way, but if I had to choose I'd much rather land in the latter. The latter still involves some politics, but at least it sounds like you're not wasting your life playing stupid games.

What appears to be "blind support" is people desperately clinging onto what tiny bit of representation they have. It's sad for both sides. It's Stockholm syndrome mixed with political pragmatism. It sucks, but the current political landscape in the US has entrenched itself so deeply in a local minima that people feel like they have to work backwards to make progress. Just see how any discussion of a third party is seen as a psyop to get that side to have a spoiler effect.

What personally has me worried is the derivative and 2nd derivative. How much is my current comfort sustained purely because of the momentum of systems made possible less than a lifetime ago (post WW2 reconstruction). So ironically your comment induces more stress in me. The idea that just as recently as the 20th century, times that my grandparents were conscious for, that many people lived through that much suffering. To me it seems incredibly easy to end up right back there.

A coworker once told me his view of his commute drastically changed when he realized he could take the ferry to work. He got fresh air, it was less cramped, and it only took an extra 5-10 minutes.