Focus on building your business and your product, not devops infrastructure. Unless your business is devops infrastructure.
Your initial technology stack should allow you to deploy code seemlessly from day 1. This is why Heroku is a great start for early startups, despite the drawbacks.
Having spent nearly a decade of my two decade career cleaning up totally broken developer-architected systems that were so poorly coded for performance that they could barely handle 10 concurrent users, I have to strongly disagree.
It's getting better, but most developers still focus on making it work right now over making it work right. They don't think about caching, or query optimization, or debug logging, or stateless scenarios for portability and clustering.
These are all things that need to be thought about before you start.
That said, a generic sysadmin won't be the kind of architect that is best, but they'll be thinking about more of that stuff than the devs, plus he can implement and manage your infrastructure. Seems like a win to me.
Focus on building your business and your product, not devops infrastructure. Unless your business is devops infrastructure.
Your initial technology stack should allow you to deploy code seemlessly from day 1. This is why Heroku is a great start for early startups, despite the drawbacks.