@dwayne
To me, a useful product that doesn't generate revenue and shuts down because it can't afford to pay for maintenance costs is crazy.
Not saying the team is unjustied but just that it's sad that it happens
To a complete newb: If you wanna deploy multiple projects in serial fashion, what parts of the stack can you "consolidate" the costs of so that you're saving money maintaining the lot of them together?
Vibe coding sort of solves for the code. But there's higher level technical stuff about overall organization and infrastructure and devops that feels less clear.
If you wanna be a high speed deployer (of many completely unrelated projects: apps, sites, games) in the vibe code era, how do you ideally meta-organize and structure your portfolio of projects to maximize cross-utility and minimize time and costs?