These indicators help in troubleshooting. If the indicator says the device should be swiveling, but doesn’t swivel, you know it’s broken. If there’s no indicator, you might think you’re just too stupid to put it in swiveling mode.

Old-fashioned switches, of course, solved this problem without LEDs.

Someone on the design team heard that squircles are the latest shit and put zero thought into implementing them.

Trying to keep up with you

1. No error messages, ever. Because apparently users hate information with all their heart and are at risk of burning down cities if they ever find out what the fuck went wrong with an application.
2. Disappearing scroll bars

The TV might refresh the screen 60 times per second (or actually refresh half the screen 60 times per second, or actually 50 times per second in Europe), but that’s irrelevant if the game only throws 20 new frames per second at the TV. The effective refresh rate will still be 20Hz.

That’s just a possible explanation. I don’t know what the refresh rate of Majora’s Mask was.

That’s me in the spotlight

Yes, way better. Thanks!

I think OP was going for fiction.

You just don’t know how much to eat.

Ugh. Why did ‘yellow text on white background’ not strike the creator of this as a bad idea?

Doesn’t matter if the mechanism that checks the repo and sends the trigger message to the runner is down.

The fewer magic blackboxes are around, the

• (happy variant) easier it is to train new people and the less mental burden there is on existing staff
• (sad variant) easer it is to fire people.

I marvel at the proficiency with which Microsoft tears down every piece of software it touches nowadays.

Sending “temporary” changes into your CI pipeline isn’t even stupid, it’s borderline malicious.

No? “Hey customer, I’ve deployed the changes you requested to the staging area. Is this what you had in mind? Keep in mind it only looks good and isn’t fully functional yet.”

The electron is rotating in the sense that it resists a tilting force.

https://www.youtube.com/watch?v=PdN1mweN2ds

Disclaimer: My knowledge of physics ends at the high school level.

That means that the HR account thinks what the employee account wrote is bad, too. Both posts are bad extremes.

As an employee, if i find a prospective colleague who doesn’t ask about what they’re supposed to be doing at all, I’d be wary of them, too.

Depending on the configuration, a linter may cause the compilation or a CI pipeline to fail.

Huh? If they’d do everything else faster, they’d only get faster to the boring stuff. How is that an incentive?

Yes, I’d rather have 35 different IDEs for every task I need to do. Much better than One To Rule Them All.

To be fair, the US thought that there were spies at Los Alamos, and they were right.