3 ms·

In my experience we as an industry just can't stop ourselves from moving deck chairs on the Titanic. We swing from monoliths to microservices and back. From se

In my experience we as an industry just can't stop ourselves from moving deck chairs on the Titanic. We swing from monoliths to microservices and back. From server rendering to client apps and now some bastardization of both via RPC calls. I've seen this happen most often due to moving too quickly upfront and not putting in the time to really plan for later. We ship fast above all else but end up with a pile of tech debt and a team that's built skills around those very same tools and patterns that are causing problems at scale. Shifting later is extremely tricky (and interesting if you know what you're doing), but you often have a team that is ill suited for the next architecture and paying customers potentially with SLAs that make migrations difficult and risky.

EA-3167 3y ago
It's an industry with a very specific funding model for a large number of companies... a desire to tap into VC funding. In turn VC's want only one thing: to hit the lottery. The result is a panicky, endless cycle of overpromising and underdelivering. Everyone wants to be a new Google/Apple level success story, few want to admit that this is an increasingly mature and sometimes moribund industry.
- _heimdall 3y ago
  On the startup side that's for sure, though in web development more broadly we're all just trying to ship the next site or maintain the last ones. VC funding definitely pushes a certain type of incentive on startups building dev tooling, hosting services, and frameworks. Those companies do one heck of a job convincing the devs shipping sites that we need to use the new hotness because everything else is old and busted.