I feel like the “we don’t know what this function does” meme is kinda bad. There’s no reason beyond maybe time crunch why you shouldn’t be able to dissect exactly what it does.

Despite this, the notion of a load-bearing function is still very relevant. Yeah, sure, you know what it does, including all of the little edge case behaviors it has. But you can’t at this time fully ascertain what’s calling it, and how all the callers have become dependant on all the little idiosyncracies that will break if you refactor it to something more sensible.

It has been several times now where a part of my system of legacy code broke in some novel fantastic way, because two wrongs were cancelling out and then I fixed only one of them.

One can more or less envision the President as the CEO of Federal Government, Inc. and executive orders as internal memos to the employees.

If you don’t work there, following the memo is not your problem.

But if you do any kind of business with someone who does work there, you can be hit by the secondhand effects.

Security questions don’t care what you put in there. It’s not an exam. It’s basically just an alt password.

I just generate a string of alphanumeric text from my password generator and stuff those in there. If I lose my password vault somehow I’m cooked anyway, so.