4 ms·
We have a checklist system. Depending on which files are on your commit or which database objects are modified, you're presented with a checklist specific to th
by Damorian 7y ago
We have a checklist system. Depending on which files are on your commit or which database objects are modified, you're presented with a checklist specific to the things you're changing. When something goes really wrong, the outcome of the post mortem often includes adding to or changing the checklist for the affected files/filetypes/team/whatever. It's not a perfect system, but it beats reading our long, confusing wiki pages.
- admerox 7y agoI like this system a lot. It convert postmoterns into actionable checklist for next project. My only concern is that the checklist might get too big. But definitely, better than expecting people to go to wikis to avoid past mistakes
- jve 7y agoCan you tell me more - how/where do you present checklist before commit?
- Damorian 7y agoWe use in house project tracking software to manage development, bugs, documentation, Etc. that it's built into. These checklists are verified by another developer as part of code review before the branch is allowed to merge to the release/main branch. There's only a couple of "generic" checks (one for security things, another that's automated that enforces coding standards), at least for our team. A small bug fix may only have 2-4 checklist options, but a larger enhancement may touch enough things that there may be 20-30 checklist options.
- pdexter 7y agoIs this automated?