Ask HN: Have we screwed ourselves as software engineers?
I generally agree, but two things I&#x27;d like to point out.<p>If you&#x27;re using python for the web you&#x27;re already part of the complexity problem, atleast from the perspective of someone deploying php 15 years ago.  I use python for web development, and I love it, but deploying webpages used to be copy an apache config and  ftp&#x2F;scp your files to some location.   Now we need app servers and reverse proxies, and static files are served differently, and even though I&#x27;ve gotten used to it over the last decade it does&#x27;t mean it&#x27;s good.<p>The other thing is that MonoRepos are pushing back against complexity for the sake of complexity. Why create a new repo when a directory will work just fine?  I think a ton of people got repo crazy because their coporate jenkins server only allowed one project per repo,  but it is trivial to check the latest git hash for a directory and base your deployment on that. ...I have a project I inherited that has 14 repos for a webpage with maybe 5 forms on it.   I&#x27;ve mostly handed it off at this point, but everytime I have to look at it I end up preaching about monorepos for weeks.