12 ms·
You do need automation on any project. At least, deployment automation. It doesn't have to be a full fledged CI with Jenkins or something. Just a bash script th
by kulikalov 6y ago
You do need automation on any project. At least, deployment automation. It doesn't have to be a full fledged CI with Jenkins or something. Just a bash script that runs on your machine, creates a docker image and deploys it to Google Cloud or AWS. The goal is to be able to clone a repo and run the deploy script right away without any manual actions. If you can't do this - you'll be hunting accidental bugs all the time.
Basic DevOps isn't hard. If you don't know how to do it - go learn it - it totally worth it.
Oh, also, you don't need developerS. Having more than 1 (2 tops) devs working on a project incurs a huge management overhead. I don't know what is your project, but if you need more than one dev for MVP without pmf, then it's the shortest route to run out of money.
- ujhb 6y agoAnd where would you draw the line where you need to invest in at least a single devops engineer?
- kulikalov 6y agonowhere. That's the point. Your backend (or full-stack) engineer must be capable of doing devops on his own. You may need someone to deal with it, if you have bunch of devs. But this is certainly NOT anywhere close to the MVP phase.