Discontinuing opsZero DevOps as a Service

2019-07-29

I will no longer be pursuing DevOps as a Service anymore and instead will be focused on one-off jobs moving forward. This is for a couple of reasons:

  1. DevOps as a Service has a lot of variabilities that makes it impossible to make repeatable. This makes it impossible to schedule tasks.
  2. We really only want to deal with Kubernetes and AWS Lambda and solving issues for it.
  3. I am also generally no longer interested in variable questions being asked, and hyper-focused on getting people to the goal of deployments and CI Pipelines.

What are the pros and cons of this?

Pros

  • We will be much more effective in doing the small set of things that will create the most value by being hyperfocused on Productizing Kubernetes Setup.
  • We will be able to change trajectories much faster because we will no longer be beholden to existing ways of doing things.
  • We will have much more time to have high-quality interactions with clients as opposed to having to do a bunch of tasks that are not core critical.
  • We will be able to much more effectively train people to do the few tasks that we can really focus on.
  • DevOps as a Service will no longer be a “job” and hopefully that will mean less stress on weekends and such and not having to be “on-call.” The on-call portion of DevOps as a Service does take a psychological toll which is not fun.

Cons

  • We will not be having repeatable revenue and that means more sales work to move forward.
  • We will need to figure out more regular revenue streams than is possible at the moment.