3 ms·
Don’t sweat too much. Automate things as much as you can (adopt a DevOps philosophy), make sure you can switch laptop anytime (everything is backed up to the cl
by rmnclmnt 4y ago
Don’t sweat too much. Automate things as much as you can (adopt a DevOps philosophy), make sure you can switch laptop anytime (everything is backed up to the cloud, password manager, git repos, etc) and run your app exclusively from a cloud provider (no on-premises). For customer support, they can usually wait a bit for a response.
If there is too much to handle, it means there is some cash flowing in and might be time to get a first employee (or outsource some tasks).
- another-dave 4y agoAs another take — I'd say automate judiciously. If you're a team of one, the benefits of things like CI/CD and containers are reduced. They're definitely still worthwhile, but that needs to be weighed against how comfortable you are setting up/maintaining these to begin with. If they don't divert too much energy because you're already well versed in them, they're probably a win. But needing to shell into a couple of EC2 boxes & manually deploying/upgrading stuff might be a safer bet for some people. You don't want to answer a P1 ticket at 3am & be getting some esoteric Kubernetes error and have no-one to ask. I think it's tough to learn & adopt new ops tools as a team of one if they're things that are on the critical path.
- rmnclmnt 4y agoYes I should have balanced my comment with « use the things you’re comfortable with ». From my perspective, setting up a QA suite + CI/CD + CaaS type hosting is done in an hour at the beginning of the project. But yeah you’re right YMMV. However, I disagree with the small benefits of DevOps for a solo dev: if done properly, you start to have complete 8+ hours night sleep!