The same applies to software: it's common to criticize someone's work without knowing the context or the story behind the system. The typical triangle dilemma is budget, time, and quality.

I’m add to existing legacy Code. I can’t be judgy most of the time. Sometime I can suss out the first build then the additional features tacked on at later dates which is where things get messy.

I’m at the fourth update and I did a little clean up. I didn’t tear it and start from zero, but I cleaned it up so future me will be happier when the next change comes (and we now know they keep wanting updates to this)

The original way worked and was clean and I just assume that the next updates were done under some time constraints. A lot of code here just keeps working for years with no updates so it made sense to do it faster with less flexibility. Not everything needs to be great when more good enough functionality is more useful.

If it's supported, by who

Yes! And design, too…