10. JEREMY GREEN @GREENHORNET79
GET IT ON PAPER
• Eliminates guessing
• Sets guidelines for what is expected
• Greatly improves consistency between projects
• More “brain space”
11. JEREMY GREEN @GREENHORNET79
HOW TO WRITE A PROCEDURE
1. Do the task as you normally would
2. For each step you complete, describe it in detail in a
1-2-3 step checklist.
3. Evaluate each step to see if it can be simplified or
improved.
4. Experiment with different techniques
5. If you find an improvement, update the original working
procedure.
27. JEREMY GREEN @GREENHORNET79
START SIMPLE
1. Create text file in a shared Dropbox folder
2. Add my workflows in a checklist format
3. Saved text file
4. For every repeating task in project, repeat steps 1-3.
34. JEREMY GREEN @GREENHORNET79
ENGAGE IN DEEP PRACTICE
1. Try something that is slightly beyond your comfort zone
2. Slowly struggle through learning the new technique
3. Repeat until you can do it correctly over and over
37. JEREMY GREEN @GREENHORNET79
CHOOSE A PARTICULAR STRUGGLE
1. Pick a target
2. Reach for it
3. Evaluate the gap between between the target and the reach
4. Return to step one
47. JEREMY GREEN @GREENHORNET79
QUALITY IMPROVES WITH EFFICIENCY
• More time and energy to focus on code quality
• More time and energy to problem solve
• More time and energy to learn new techniques
51. JEREMY GREEN @GREENHORNET79
• Keep all notes and todos for a project in one place
• Use code snippets
• Develop locally
• Use a starter theme or framework
• Speed up your computer
• Learn how to use your tools better
• Create project templates with checklists
• Learn keyboard shortcuts
• Create canned email responses
• Use build tools like Grunt or Gulp