News for hackers. Stuff that matters.

hnhmp

The idea that it was worse back then has been thoroughly debunked. The unfortunate truth is that property values have soared (due to lack of supply), inflation continues as it does, and wages have totally stagnated. Those combined together mean that however bad it was for families back then (and I'm sure it was bad! Housing insecurity is something folks should never have to face, and I'm sorry you went through it too), it's just worse for people today, full stop. This isn't the oppression olympics, I don't want to tell you that you didn't have it bad, or anything like that. But it just sucks to be facing a very real problem today and have people incorrectly tell you that it was worse before. Not only does the existence of a problem 50 years ago not negate the existence of a problem today, but people in politics and on the internet want to tell us that it's not as bad as we think it is, when in reality it's much worse than they think.
While I don't disagree with the notion of breaking up big companies, a have a small bone to pick about the last thing you said. The American dream was never intended to apply to more than a very specific subset of the population; those that we see with the majority of wealth today. It's already worked for those it was meant to work for, and consequently it will never be fought for again. At least, not by those with any real power today; they got what they wanted and have been pulling up the ladder on everyone else ever since. Let's quit trying to buy into the American dream, and try buy into a just and fair society for all. If only that were the goal all along :/
Re:How to Build Software Like an SRE on Wednesday October 19, 2022 @10:30AM (#33262772)
imo this is seeing this a bit too black and white. Like, ops is _paid_ to get things back on track ASAP. Whereas devs are generally given more time and have the space to think about the elegant solution. And, sometimes one-off issues are just that - one and done problems that probably won't ever arise again. In that case, especially on a lean team, is it really worth the time to elegantly solve an edge case? Especially when 6 other things are on fire? Just my two cents.