Everyone Can Be a Full-Stack Engineer
Summary
I think that theres a better model for developing modern web apps, one in which individual engineers get to own their feature, all the way from the top of the stack to the bottom. I think the next problem we may run into is actually a product one, of, I said we were building these really interesting reactive, interactive apps, but the architecture diagram Ive drawn here is really only about loading data and writing it. Asana had an in-house Pub/Sub system they built themselves, and broke up the data model into these fine-grained Pub/Sub topics, and used those to push around information, so that anytime youre viewing content in the app, you would see it change in real time. Once you remove all the unnecessary complexity, it is completely feasible for engineers to work all the way from the schema layer up to the UI, and think about an entire product feature. I think, yes, having a single software development life cycle is a often pretty simple model for most teams, unless youre getting up to some huge scale and really want to separate deployments into more granular units.