"what if objects were actually designed for a bad user experience, instead of a good one? she recalled in a 2018 TED talk. That was my ‘eureka’ moment."
Or, she stumbled upon some article or the very Wikipedia page about it:
Another take on the matter is: interruptions are inevitable, so reducing the "recovery penalty" is key, and can be learned.
That's something that you learn to do when you have a kid: suddenly, your periods of 4 hours of focus free time (for coding, exploring tech, whatever) during the weekend just _disappear_. You only get max 30 minutes of free time in a day; this is extremely frustrating initially; there is no boss to complain to, no meetings to blame, no solution but to deal with it. Progressively, you learn to switch tasks much more efficiently, by making regular check points, so that you can get interrupted any time and get back to deep work _quickly_.
Talking about monetization strategy, there is a world where we would not have to remember "Zillow" or "Spotify", and instead ask for real state or music related actions, and have OpenAI "decide" for us what is "the best" options... As in "the option that paid the most to get promoted".
There has been a move in the past 8 years away from Java on the back end, notably to Go, by several large engineering organizations, which made the move, "motivated" by the example of companies like Google or by projects like Kubernetes, and seduced by the promises of a language simple to learn, build, and deploy.
Sincere apologies, I mixed ibuprofen and paracetamol.
Ibuprofen is forbidden for pregnant women in the last 4 months in France at least - and by "forbidden", I mean "strongly advised against in a case of self medication".
We won't own games anymore, we won't be able to sell/acquire used games, we won't be able to play disconnected.
I'm curious whether Nintendo will be following the same path.