@aidenybai I think the correct answer is "it depends". Early return at the start of the function is good, but once you get into the function logic somewhere and potentially have a required return object it's less clear, and early return can easily introduce bugs.
@fjzeit My memory isn't as good as yours, but I think lowest cadence is definitely less than yearly (new products), and max is maybe circa 30 (4 major releases, and weekly patches, but not all of them got out).
@fjzeit Also, I feel the people who just say "do everything right all the time" clearly work in places very different to every job I've had. There's _always_ some kind of downward pressure to use less time. You can only push back so much in most places.
@fjzeit I've seen it lots, often in code that's run flawlessly for years. A lot of our quality desires are based on things like maintainability... If no-one ever needs to maintain it, does it matter? (Obv, guessing what will need maintaining is so hard we just assume everything will)
@fjzeit My big problem is they replace one basic rule with another basic rule. I've seen nothing to say weight loss isn't calories in calories out, but that calories out bit is all over the shop, and I highly doubt it's all thyroid function.
@fjzeit It's legacy when you don't like it any more. Could be that you don't like the language, or the style. It's a way of abdicating responsibility (potentially reasonably).
@fjzeit For me, clearly a pattern...
Java + C -> C++ -> C# -> C++ -> C# -> C++ -> C#
Miscellaneous scripting (tcl, python, JavaScript, typescript) and occasional x86 asm throughout.