4 ms·
I don't have a complete answer right now, but I would consider the following ideas. * Can you deploy (not build) with a push of a button * Can you deploy the
by varikin 9y ago
I don't have a complete answer right now, but I would consider the following ideas.
* Can you deploy (not build) with a push of a button
* Can you deploy the same artifact to test, stage, prod, etc with no changes?
* Can all developers easily check metrics and logs for production?
* Can all developers access production?
* Are servers pets or cattle?
* Are developers allowed to choose the tools that best suit themselves?
* Who gets paged?
* What happens the day after page?
* How is server config managed?
* Are schema changes to the database automated?
Obviously, these are not all yes/no questions and should be simplified, but it is what is on the top of my head. Some if it is based on the idea of a 12 factor app and on using immutable images (docker, amis, etc) and some is based on devops/sre models of working. For example, who gets paged and what happens the next day is all about process. Fixing and forgetting the issue is not acceptable.
- deleted 9y ago[deleted]
- thehardsphere 9y agoI think these are good questions, but I don't think they could replace the questions in the Joel Test because they're very specific to host-your-own-SaaS-product development. The Joel Test questions are applicable to pretty much any kind of software development someone could do.
- olalonde 9y ago> * Can all developers access production? That doesn't seem like a good idea...
- toomanybeersies 9y ago> Can all developers access production? I don't think that's necessarily a good idea, for various data disclosure, security, and safety reasons. In fact, I'd say that a better question would be if developers are able to diagnose and solve problems without having to access prod. For example, a company may have an anonymised copy or partial copy of prod for developers to work with.
- voska 9y agoIt is when your CI process will prevent any breaking changes.