If there were serious macro consequences then maybe it would be an issue but from the point of view of the communities -- there aren't. Data centers don't bring a lot of permanent employment and tend to be given tax breaks. They are skeptical that data centers are the boon that these people claim they are -- and they are right to be so since people pushing these data centers have been wildly untrustworthy at best.

Saying "You can't stop it so you might as well get on board and hope that in the future you can convince shareholders/billionaires/US Congress to give you a pittance of UBI" is going to go over like a lead brick. There's no reason to trust that UBI will come if you give up any leverage you have, even if it is a minuscule amount of leverage.

> This doesn't make sense. The reason Congress is difficult is because of those same powerful people.

Its much easier to put someone who is aligned with your values into a local political position than congress. And its much more likely that your neighbors will vote in a way that aligns with your interests. And you won't get overridden by a congressman from several states away that has different incentives.

Yes, people building data centers can just shop for a new location. But resistance to data centers appears to be pretty correlated with living in communities that are good places to data center, at least anecdotally.

The world I'm looking in is one where citizens pushing back locally has seemed to get at least some measure of success, albeit spotty, whereas attempts to lobby Congress about AI has been screaming into the void. Frankly, I think your position here is completely divorced from what is actually happening in reality.

I don't see why you think that. Its something that:

1) These CEOs and people with power want

2) The populace has some degree of control over, since its local politics vs national.

That makes it an attractive way to push back against powerful people that they see as operating in bad faith. It seems like their chances here are much better than trying to go directly to congress and advocating for UBI.

At least in the US, the public simply does not trust that the United States government will consider such a thing. They won't even consider universal healthcare. No-one is going to go "OK we trust you, you can build your data-centers now and we'll talk about UBI once you've 'disrupted' our jobs."

Yes, a bunch of CEOs are making the rounds talking about it, but talk is cheap. Even if that talk is directed at congress. Have any of them even cleared the flow bar of funding research into how it'd work and what the policy would look like?

Every time a business tries to make a "connection" its really just an avenue to exploit or manipulate me. I've never had them making a connection for my benefit (i.e. take a hit to their bottom line).

I'm not asking for altruism but I am asking for them to drop the pretense and quit bullshitting me.

To be fair, there are plenty of situations where throwaway code is perfectly fine and/or defect risks are low enough to make the trade-off worth it. I don't think a lot of developers are thinking about it in that context, though.

(No unit tests aren't enough)

The problem is that this is increasingly seen as a non-productive workflow slowing everyone else down, so the pressure is growing for writers to just shove massive PRs out the door and reviewers to use LLMs to make that tractable. I suppose those advocates have more faith in LLM output compared to humans than I do.

> It's not about new technology for the sake of new technology, it's about taking pride in one's work what what that person created.

Thank god, I really want to say that I appreciate that you got what I said. A simple upvote didn't feel like enough.

Employees are humans, not robots. Its inconvenient, but if you want a world-class team then you're going to have to deal with the fact that people derive satisfaction from different things, and you're not going to be able to motivate them by beating them into submission about what they "should care about." This may involve having to think creatively about how to manage your people instead of treating them as fungible work units.

> Platform and internal dev teams have customers as well. I'm not terribly frustrated that you don't get this.

Respectfully, this response here is a perfect example of you not getting it and assuming that I am the one that doesn't get it. You have not said anything that I have not already heard and understood before. The fact that people have different values does not mean they "don't get it." But saying something like "Do the engineers not derive enjoyment in their jobs from making the customer experience better?" does imply that you don't understand other peoples' values.

The fact that you posted "Platform and internal dev teams have customers as well." indicates to me that you missed the point. Whether they are on those teams and whether they consider other engineers their customer is besides the point; they may not derive satisfaction from "delivering value" to those people regardless. That doesn't mean they don't care about their customers, which is the take away the median HN poster takes, but rather that they are not energized and motivated at the end of the day by delivering value to them.

> I've certainly worked with devs (and managers) who wanted to push new technology for the sake of using new technology,

Sure, everyone has. But the flip-side of this is a class of people who assume any tech improvement that doesn't directly move a metric is just an effort at resume-building. Just as often I've seen efforts and building a more robust system as unneeded resume building despite clear need (usually because the need is very hard to measure).

> and they should have found a side project as an outlet for this.

I mean, this is incredibly dismissive and exactly the attitude I was talking about. No-one is saying that engineers should be allowed to just do whatever to have fun. Work is work. But ideally you find ways to organize your team so that everyone is motivated and energized by their work, and doing so requires that you understand that not everyone is motivated by the same thing. But in these discussions, the attitude comes across as "everyone should be motivated by delivering good customer experience and if they aren't we shouldn't care."

If there's no opportunity to give these sorts of people fulfilling work, then fair enough. It *is* work. But the attitude displayed here is that we shouldn't even try and understand their values and think about ways to productively deploy that.

As an aside about customers, internal and external customers are, in my experience, treated vastly differently. We care about experience for external customers, but internal customers is usually all about velocity and trade offs. The bar is substantially lower, and rough edges are almost always ignored. So I am skeptical at the idea that we can just frame internal users as customers and all the discrepancies go away.

It also misses the fact that other people on my team are also my customers, because they have to maintain the system! And I am also my own customer, because I also have to maintain it!

Quite a few don't, no.

Different people derive enjoyment in different things and some of the best engineers do not find satisfaction in "delivering better customer experience" but in working with, and improving, cool technology. Its up to management to find areas of the business where they can deploy these people in a way that dove-tails with business success.

Its also the case that only working on projects that "deliver customer value", and having to justify every single endeavor through that lense, is how you end up in a local maxima in your tech stack, get mired in technical debt, and then get lapped by your competitors who have the foresight to work on foundational technology that enables future velocity.

To be frank, its endlessly frustrating that your median Hacker News poster doesn't get this, and instead prefer to brow-beat people about how they're caring about the wrong things.

This has not been my experience. What has changed is that its now looked-down on to denigrate people who choose not to have kids (in some circles), and that people are no longer treated as heroes for having children. It had historically been the case that people who chose to not have kids were browbeaten about their choices.

I have had no issues talking about my children at all even with people who have remained childless. This is because I respect other peoples' decisions when doing so.

It’s possible that sufficiently advanced “dumb” compilers and tooling could lower demand. Or that the supply of developers outstripped demand - that’s happened in other professions. We always joked about how we’re automating our own jobs. We just happened to live in a period of explosive demand growth for our skill set so it never mattered for us. But it was never guaranteed that growth would continue in perpetuity.

When mentoring a freshly minted dev, I always checked whether or not they were open to career and financial advice. And if they were, I would always make this point to them and tell them to think carefully how much of their massive tech salary they should be spending. I make it a point to keep abreast of what median salaries are for other job roles are viable and moderate my spending and saving accordingly, because there was always a possibility that the gravy train would stop.

It’s just that the median tech worker was more often to talk about moving fast and breaking things and making glib statements about buggy whips. If you were the sort of person to just shrug and say that a few leopards were the price of advancement then you’re probably not going to get a lot of sympathy. That is, unless you connect your current faceless state to your previous stance on leopards and admit that maybe you were shortsighted (generic “you” here, not you specifically).