Yeah, I've found a sizeable portion of these people will gladly stall a project indefinitely by bringing a "but does it scale" mindset to a deployment that fits on an instance and a few AWS services.
Like no really, we don't need to argue about a 5 page git branch management and deployment policy for 4 developers. We don't need datadog or whatever for 100KB of text files. Editing that github action that takes 2 hours to generate a docker deployment from scratch is a massive waste of time. etc.
What we do need is something that generates revenue and an engineering philosophy that mainly comes from the rest-and-vest crowd isn't it.
No see, some guy from Heroku wrote a blog post about comprehensive build artifacts so now that's what we have to do. What don't you understand about comprehensive build artifacts? Maybe we can get on a long, long, long call to discuss how I'm right and you're wrong, I did work at $HUGE_COMPANY after all.
We can't possibly do things the wrong way, no matter how dumb our current practice is.
Like no really, we don't need to argue about a 5 page git branch management and deployment policy for 4 developers. We don't need datadog or whatever for 100KB of text files. Editing that github action that takes 2 hours to generate a docker deployment from scratch is a massive waste of time. etc.
What we do need is something that generates revenue and an engineering philosophy that mainly comes from the rest-and-vest crowd isn't it.