Does my framer ate occasionally drop? Yes. Does it matter? No! It's Cities Skylines, not Counter Strike.
https://www.reuters.com/article/us-microsoft-settlement/micr...
Honest question: do execs or companies in general ever suffer consequences for data breaches? Seems like basically no one cares about this stuff.
I regularly do things like:
if (0 && expression) ...
and: if (1 || expression) ...
to temporarily disable a conditional when I'm looking for a bug.Writing clear, concise code is *hard.* Writing just clear code, conciseness be damned, is a perfectly fine middle ground.
0 is to prevent mistakes where you declare a function, but forget to implement it. If that's really intended I like to put a comment "do nothing" in empty functions, even in projects without the ESLint rule, so future readers know what's going on.
1 is for consistency & readability. Imagine you read someone else's code like <div children="foo" />, and you see that it's self-closing, so you expect it's an empty div. Even more confusing when you have more than just one attribute. Or say you want to modify the code to add a new child, so you remove the self-closing and add the child, breaking the old children in the process. What is the reason for doing children="foo" in the first place anyways?
2 is to prevent infinite loops, it's good practice to keep an upper bound (in a single-threaded world like JS, infinite loops can be very deadly and hard to diagnose). I like NASA's ten coding commandments (this is #2): https://devm.io/careers/power-ten-nasas-coding-commandments-...
> should you complete 70% of your goals to 100%? Or should you complete 100% of your goals at 70%?
explicitly addressed in various articles and books. you average your scores across objectives and KRs to get a score. So the answer is both, looking for average score of 0.7
> if your key result is "migrate 100% of users to the new system" and you only migrate 70%, guess what? Now you're stuck maintaining two systems in perpetuity
so you're going to migrate all of your users in a big bang moment?? hell no. it'll be bit by bit no matter what. of course you're maintaining two systems, that's a sign of a good migration, not a bad one. the KR just helps you get done with it faster
of course there are valid criticisms of okrs, and many (most?) teams get them wrong.
but saying "okrs are bullshit" has become a common trope for new-age companies who use that as a way to differentiate themselves. do you really think Andy Grove and John Doerr are bullshit artists?