The Roomba j7+ cord and object detection is working well for me, although it's (probably) more expensive than the Chinese offerings. Regardless, it was a huge step up from my precis Neato Botvac connected (which was probably 5-6 years old though).
Have you ever used a wireless vacuum? It may sound stupid, but it saves significant time and effort over a conventional vacuum; taking the clunky vacuum out, plugging it in, unplugging it and putting it back means it takes (much) more than twice as long to do spot vacuuming.
Personally I'm never going back to a corded vacuum if I can avoid it.
Even if it's true that in-person developers are more productive, you also have to account for the preference of developers. If developers prefer to work remotely, then the average in-person developer is probably likely to be worse than the average remote developer (since skilled developers will have an easier time to find the more attractive remote positions).
And as we all know, the difference between a skilled developer and a bad one is quite massive.
One thing many surveys/studies do is to include "trap" questions (I'm sure there's a real name for 'em) which disqualifies any participants that answer them incorrectly.
It becomes more of a discussion and is less likely to bruise egos. In my experience I've had more success getting things done by building concensus that way, but ymmw.
You can make the same argument about breaking changes. Code is constantly changing and needs to be updated, so breaking backwards compatibility is zero-cost?
In reality each change that requires updates to documentation (or code) is of course not actually zero cost.
In reality these types of changes often just make learning more difficult, because now you have to learn that it's called both "motherboard" and "mainboard". At least for a generation or two.
There's some things that the $150 goggles might have that the cheap ones don't (anti-fogging, UV protection, durability etc). Or they're just marked up, who knows.
Your original comment is simply poor. A better way to phrase it would be something like "a lot of scientific breakthroughs came from people who fought against the concensus" and leave it at that.
I wonder which modern information would be actually useful a thousand years ago. Things like electricity, cumbustion engine etc wouldn't be very useful, but perhaps something steam-powered?
One low-hanging fruit would be sterilization and hand-washing for medical operations, at least.
I've had issues with Outlook (or whatever Microsoft calls their mail service) placing my emails in the spam folder, so YMMW. Works fine when the receiver is using Gmail, though.
I would guess it's an absolute disaster for Firefox. While it's not going to make me switch from FF to Chrome personally, this issue is big enough for me to not install Firefox on non-techies computers. I bet a significant amount of people will permanently switch away from Firefox due to this too.
You write a lot of words to explain how the maintainer could justify his malice. At the end of the day it's still done out of malice, though.
Unless he's gone absolutely bonkers, he's doing this to intentionally cause damage. The reason for it does not matter, as the definition you posted helpfully points out.
Why? If that's indeed the law, then it's up to the website owner to comply. Whether it's Princeton or a private individual writing the email doesn't matter.
There's honestly quite a few developers that produce zero or negative value (e.g. by implementing the wrong things, introducing lots of bugs or significant complexity etc). 10x:ing them is not difficult.
The point about "karensdag" isn't quite true as the max compensation for it is significantly lower than 80% of your salary (afaik it's 810 SEK for that day).
This "volatility will come down as the market cap gets larger" keeps getting thrown around, yet Bitcoin just lost 50% of its value at a market cap of 1 trillion USD. What market cap is required for Bitcoin to stop being volatile?
For me it depends a lot on what kind of work it is. Architecture/design/troubleshooting or other mentally taxing work I agree fully, maybe 4h after lunch per day. I can easily put in 40h+ of productive work when implementing straightforward solutions though (coding, documentation, testing etc).