4 ms·
These can help in software development, too. Everyone is so obsessed with speed, but often the thinking is short-term. Slow down a little bit and use a checkli
by alanh 10y ago
These can help in software development, too. Everyone is so obsessed with speed, but often the thinking is short-term.
Slow down a little bit and use a checklist when deploying. Use a checklist when reviewing code. Iterate so you aren’t wasting time or limiting your thinking.
- gnaritas 10y agoDevelopers have something superior to a checklist much of the time, automation. Deployment should be fully automated, no checklist necessary. But yes on non-automatable things like code review, a checklist is certainly a plus.
- retbull 10y agoAlso unit tests provide a type of checklist.
- cmdkeen 10y agoNot all parts of a deployment can be automated in every case. I've helped craft a checklist we use on our releases based on lessons learned over several years, an awful lot of it is about communication to end users / other teams. Especially if the release is one that involves downtime it's important to have consistent practices and clarity about who is going communicate what and when. Checklists are a good way to capture the "what could have gone better" outputs of retrospectives.
- gnaritas 10y agoFair points about client communication.