Another idea: line up some dev consulting work that would enable you to spend more time per week (in aggregate) than the 2-3 hours per day you're spending now. Consulting offers higher hourly wages and more flexibility, generally speaking.
There are clear downsides too. You would need to source these contracts yourself and figure out health insurance for your family.
Indeed. Our goal is to make it as easy as possible for developers to enable CD. It's still super early in this space, as shown by the fact that most companies have homegrown tooling (usually some scripts on top of Jenkins). It shouldn't be that way. When you think about other categories within DevOps (observability, security, alerting) there are many out-of-the-box tools to choose from such that one would never say "I think I'll build an observability tool from scratch here".
I've implemented CI/CD at multiple companies on many platforms, including Argo and Spinnaker - specifically at startups with limited resources, managing a bunch of microservices or an application specifically for CD is usually just not an option. I love that it's modular and doesn't require any specific CI tool, and the simplicity of implementing canary without a service mesh or custom tooling is nothing short of amazing.
Hey Tara team. Ben here from Armory (YC W17). Love that you are tackling this very important problem for product and eng teams. We use JIRA (surprise!) as do all of customers. I've long wished I had the time and energy to think about and maybe even tackle the challenge you are facing - building a JIRA-killer. Go forth and conquer! I would be very happy to help in any way I can!
