> By the end of fiscal year 2026, the company's workforce was slashed by about 21,000 employees – a decline of roughly 13% – from 162,000 to 141,000 workers.
I'm pretty sure watermarking is (or soon will be) a requirement for AI generated images in software used in the EU, as part of their regulations for AI transparency.
Picture a space station where there's an error when trying to seal the door and they proceed anyway and it explodes from the pressure differential as all the air escapes out to space.
I wasn't making an argument against growing your own fruit, I was just helping explain why a lot of people don't do it. Personally, I am trying to grow blueberries.
It's definitely science, and it definitely doesn't work that way for most people. Also, "a few years" is a long time between deciding you want fruit and getting to eat it.
UBI feels like a natural solution to what I assume is a ubiquitous problem in the workforce: A certain percentage of people are absolutely worthless in their job, and everyone would be better off if we just paid those people to stay home.
I see what you're saying but I don't think that's the answer for everything, because people also pay for conveniences, like a Ring subscription so that Amazon stores footage in their cloud for you.
The problem is centralization is more convenient for consumers. You can easily control your doorbell, your garage door, your security cameras with 1 app, and everything just works.
Open source and decentralized solutions need to be just as convenient and cheaper than centralized ones for consumers to choose them.
> A typical debugging session illustrates the pattern: I describe the bug by voice (Wispr Flow), Claude searches memory (claude-mem) for prior context on that area of the code, creates a task in Beads, and spawns a debug team (Agent Teams) with competing hypotheses. [...]
So at the end of this process, you've spent anywhere from $1 to $5 to fix a bug, and you don't have any of the knowledge you would have gained from being directly involved in the fix. It seems like this approach would keep a developer easily replaceable over time, regardless of how long they've been working with a codebase, because they build very little internal knowledge on it.
> What exactly is wrong with a world where software is borderline disposable?
One problem is that people don't like learning new software interfaces, and another is that communities help support software, but communities need stable, long-lived software to foster.
This may be an unpopular opinion but I like the effect where the cursor turns into the button hover state when you hover over them, like the pause icon button on the video.
Nice, I do this often enough that I created a bookmarklet to download an HTML file from clipboard after copying ChatGPT's code block.
I've also been using LLMs to create and maintain a "work assist" Chrome extension that I load unpacked from a local directory. Whenever I notice a minor pain point, I get the LLM to quickly implement a remedy. For example, I usually have several browser tabs open for Jira, and they all have the same company logo as the favicon, so my Chrome extension changes the favicon to be the issue type icon (e.g. Bug, Story, etc) when the page loads. It saves a little time when I'm looking for a specific ticket I've already opened.
Is this article from the future?
> Story by WALLA! MONEY
Who?