Software project tasks, such as adding a new feature or fixing a bug, are often described in a ticket system. It's easy to read the ticket description and then jump right into coding the solution. However in order to work efficiently, there are a number of things to consider at different times while working on a ticket.
When working on your next ticket consider checking off each item in the following checklist. This will allow you to be a more effective developer.
Make sure the ticket is:
- well defined
- finite and has a definition of what it means to be done
- limited in scope and only focused on one task
- complete with assets
- considering edge cases
- needed. What is the ultimate goal? Is this the right goal?
When considering approaches, think about:
- evaluating proposed solutions
- Occam’s Razor (simple, not complex)
- deployment plan
While working on a ticket, be aware of:
- biting off too much
- time spent
- spinning wheels
- scope creep
- security implications
Review your work for:
- naming conventions and consistent styles
- adequate tests
- code citizenship. Leave it better than you found it.
- compatibility with production. Ask will this break anything?
Have something to add to this checklist? Please leave a comment letting us know!