[codeptualize]

What works for me is to assume there is always an explanation, then go look for it.

Could be anything from an actual good reason to do it this way, or some other factors like cost, or maybe even just lack of time, or the best of multiple bad options.

Postpone judgement until you have a good understanding. You could still come to the same conclusion but it will likely be much more nuanced.

Basically empathize with whoever build it or was involved.

Also design/build stuff yourself, do user testing and get feedback; it’s humbling haha.

[jrs235]

Like Chesterton's fence [0].

I get annoyed when other younger/new hires come in and just start bashing and saying how stupid this is that is/was and that the person that did it was dumb or an idiot or incompetent without them first learning the history, context, and environment the decision(s) were made in. And they're typically not wrong. If the decision(s) were made today, I typically agree 100% with them.

[0] https://en.m.wiktionary.org/wiki/Chesterton%27s_fence#:~:tex....

[jrs235]

*they're usually not wrong about how stupid the current situation is, but they're wrong that someone is stupid, dumb, or incompetent. Hindsight is 20/20 and historical context is important.