Want to do less work? Join a union and campaign for a 4-day work week or something. If the productivity benefit from AI is real, there's no reason you shouldn't be paid the same for less time because your output is the same/better.
484 karma · joined January 30, 2018
Want to do less work? Join a union and campaign for a 4-day work week or something. If the productivity benefit from AI is real, there's no reason you shouldn't be paid the same for less time because your output is the same/better.
They know that using terms like "rent" or "lease indefinitely" would reduce their revenue, so they squirrel away legal gotchas that no one ever reads to cover their arse. It shouldn't be allowed.
Just because something is legal doesn't make it ethical. Sometimes the ethical thing to do is ignore the legalities, which is why people are fine with advocating for piracy in cases like these.
> The radiator surface area problem also scales uncomfortably. At 838 watts per square meter, rejecting 1 megawatt of waste heat requires roughly 1,200 square meters of radiator. Deploying that much surface area on a satellite is a structural engineering challenge that gets harder with every order of magnitude. The ISS solar arrays span about 2,500 square meters total.
So even a 2MW data centre in space requires a cooling array rivalling the international space station. Starcloud launched a single H100 in November and they were unable to run it 24/7 due to heat buildup.
Even with novel solutions to make heat transfer to the fins more efficient, like phase-change liquids, the limiting factor is that the vacuum of space is a tremendous insulator.
https://thecoolingreport.com/intel/starcloud-orbital-data-ce...
https://satnews.com/2026/03/17/the-physics-wall-orbiting-dat...
> Importantly, the company did not mandate AI use (though it did offer enterprise subscriptions to commercially available AI tools). On their own initiative workers did more because AI made “doing more” feel possible, accessible, and in many cases intrinsically rewarding.
If it's no longer being maintained then put a depreciation warning and let it break on its own. Changing a deprecated feature just means you could maintain it but don't want to.
Alternatively if you want to aggressively push people to migrate to the new version, have a clear development roadmap and force a hard error at the end of the depreciation window so you know in advance how long you can expect it to work and can document your code accordingly.
This wishy-washy half-broken behaviour doesn't help anyone
If AI is somewhat successful at automating knowledge work, what feasible job could exist that doesn't require your mind or body?
Services like healthcare and plumbing aren't going away of course, but there's not enough demand to support an economy on those jobs.
In my opinion the whole economy needs a rethink regarding what our actual goals are as a society, and maybe AI will force that conversation to happen, but I'm sceptical if it'll be a well-considered consensus.
Or diversify in both directions - small US, and big and small international funds.
This is why a lot of government projects take so long, they don't see the value in keeping an in-house team of trained experts (see the difference in train line contruction costs in the UK compared to Spain), until you realised how good they were but you can't hire them back.
Are Uber/Lyft still cheaper after a 10-15% tip?
The flipside of removing them is you now need to hire experts/specialists to do the work properly, not fire them...
I wasn't aware of Intel's limitation when I built my first computer in 2016 so when I wanted to upgrade a few years later I wasn't expecting to need a new motherboard since it still had everything I needed - it felt so wasteful!
Instead I just waited for AM5 based on the longevity for AM4.I'm really hoping AMD support AM5 for a few more generations so I can do the same as you in 2026/7
So you would need at least (and with the efficiency loss of production, much more than) 1.5 Little Boy atomic bombs worth of energy to make a single gram of antimatter.
The historical financial punishments to writing buggy software are gone, and now it's infecting cars I'm concerned that safety standards will begin to slip and potentially injure someone.
Side note: I know a common response to buggy software is the market won't pay because it takes longer to develop etc. But writing robust software is a hard skill,and it you haven't seen an industry write robust software for a long time, why should you trust they still can?
In the UK government, before programming was considered a high-value skill, the vast majority of programmers were women. So much so that programming was measured in girl hours (which were paid less than man hours).
When it became clear that programming was going to be a big deal, women were systematically excluded, flipping the gender balance (although they had trouble hiring initially because men saw it as lesser work).
It seems like 9000 (and the newly announced Intel 200 series) have a lot of restructuring work and lay the bed for future generations to push further
> In September 2023 the government regulator, the Office of Rail and Road (ORR), had issued an improvement notice to Network Rail about overcrowding at the station, warning: “You have failed to implement, so far as reasonably practicable, effective measures to prevent risks to health and safety of passengers (and other persons at the station) during passenger surges and overcrowding events at London Euston Station.”
It's concerning to me that Hendy was the chair of Network Rail from 2015 before becoming Transport Minister, and here he is sacking someone after a comment about his former workplace. Should definitely be an investigation into his motives/incentives IMO
IIRC There is an alternate method of connecting to an endpoint which uses a 3rd node as a rendezvous point which is meant to be better, but I forget the name of the process...
These are not the actions of someone being protective of their skills to make more money imo.
Firstly the road structure is very different to the US, streets are much narrower and less car-centric so models are harder to train; secondly regulating it is much harder because the EU is a collection of countries, which is very different to a collection of states.
Thirdly non-car alternatives like trains and ebikes are a lot more viable due to a higher population density, many big cities (such as Paris) are pushing for better cycling infrastructure rather than better layouts for cars.
If it pays off, the fee doesn't matter because we made more money. If it lost money, well we did our due diligence so we were just unfortunate.
I've not read his book, but seeing an endorsement by Sean Carroll (a great physics communicator I've seen a few times on the YouTube channel Sixty Symbols), I'm very tempted to get a copy.
Voluntary fixes are necessarily smaller in scope and suboptimal as a result, leading to more complexity when those systems need to be changed later.
I'm also reminded of Casey Muratori's talk about software architecture being a reflection of the organisation that made it. Open source projects are at the extreme end where contributors and org charts are highly fluid, and communication between contributors is low-bandwidth, accelerating the complexity increase.