I submit that architecture may yield to Conway's Law[1].

To your point, language design may have more todo with the cohort of the original language desingers.

That said, languages tend to add more baggage over time; does recent C resemble K&R very much?

Python with full type hinting is a far cry from the 2.4 stuff I first encountered.

[1] https://en.m.wikipedia.org/wiki/Conway%27s_law

I mean, I'd also posit that organizational/corporate organization--whether you think scrum or agile or whatever makes sense--is also likely related (on average: same as with literature here, not saying "in all cases") to cohort succession.

I hope I’ll live to see the future generation that fixes UI design. The last decade or so certainly broke it.

A hellscape of hamburger menus, heiroglyphs, and hidden errors.

I'd like to add "everything is controlled through a single button" to the gripe list, but I haven't figured out how to make it snappy and alliterative.

I understand why this happened -- mobile first design and then dogmatic application of space-crunch compromises to interfaces without a space crunch -- but yeah, I really hope we can roll back the worst of it without waiting for AR to reverse the screen real estate dynamics. How many generations of proprietary morse code combinations for single-button interfaces can fit between today and AR landing? Too many. Far too many.

It's a good idea, and could well be done. The hardest part might be identifying the date-of-birth of the people who wrote the software. Libraries preserve that for books. Code reuse might also be a tricky issue.