Spider

It’s one of those pads you put on top to keep dirt from getting in between the keys

I bet it’s more to do with how little Americans own their own culture. Copyrights in the USA used to expire after 30 years, after which it became public domain. Or in other words, culture was returned to the people as a whole.

Nowdays the copyrights last beyond a lifetime, and Americans grow up in a world where they almost never experience relevant pop culture outside of being owned or controlled by someone. When you find American content, you don’t think of “American culture” you think of “This is owned by Disney” or “This is owned by Paramount” and so on and so forth. You have original authors and content creators, being the gods of the world they created, and everyone else are “fan artists” or “fanfic writers,” being implied to be lesser. Those fan artists will be fan artists their entire lives, and their works will never be ‘canon’ in the eyes of the Owners. If you like Harry Potter but not Rowling, too bad. The public cant reclaim it.

That’s not how culture works though. Culture remixes, reinspires, deconstructs, rebuilds, and memes on. That’s how everyone did stuff before the advent of recorded media. The good stuff is repeated and boosted. In a way, the Internet culture that emerged in the 90s sought out to rebuild what was lost after the 1890s.

A lot of the time its impatient management who want the fastest solution right now, demanding their jenga tower built from hollowing out the middle and never allowing time to fill in the gaps with any new blocks.

But i’ve also seen just plain inexperience from devs who have never seen a project become technically bankrupt. Some people just carry the expectations for a short lived app into a constantly iterated long lived app, not realizing that is the way to crunch and missed deadlines.

Compounding the inexperience issue is the use of bad architecture. Architecture is a bigger picture thing, not something to bang together a bunch of use cases and a bunch of factories. The purpose of architecture is to keep development easy and smooth for now and the future. If it doesnt feel nice to work in, it’s not doing its job. If devs keep trying to cheat it, its time to add convienience tools to encourage them to do it right.

Clean Architecture for example is very nice, it really shines in projects intended to be iterated continuously on for over 5 years and many more. It mitigates the pain of replacing and upgrading old obsolete stuff. Using it for one marketing campaign app that’s going to live for only 3 months is overkill though. For very short projects, you can see how its the wrong tool for the job.

Selecting the right architecture involves understanding the patterns used and knowing what problems those patterns were meant to solve. Thats the way to know if those problems are relevant to your project.