3 ms·
I assume that premature infrastructure optimization (complexity, complex automation, kubernetes, etc whatever you say) is same with premature optimization, both
by fendy3002 6y ago
I assume that premature infrastructure optimization (complexity, complex automation, kubernetes, etc whatever you say) is same with premature optimization, both are bad.
However same with optimization, there are some best practices that are good to follow, such as avoiding N+1 queries.
For me personally, that will be deploying with docker-compose, which usually yml already be created during development, and it'll be much easier to migrate later.
- jameshart 6y agoThis is of course a tautology. Premature anything is bad. That’s what ‘premature’ means. It means you did it too soon, before the optimal time. Doing it later would have been better. But there is an optimal time. And even if you did it too soon, if you eventually needed it, at least you’ve done it. Better that than getting to it too late, surely?
- heroprotagonist 6y agoAnd then there's the "I've already done it this way a dozen times and I'm comfortable with it. There are benefits to it and it's not that much extra effort to set it up from the beginning and save 10x effort down the line."
- 8note 6y agoYou need that to go with "also it doesn't add another failure point/upgrading dependencies work before it's needed"