- Write code that works, most of the time at least.
- Keep documentation up-to-date unless no one's going to read it anyway.
- Use TDD, but don't both to hook up CI.
- Hire a ScrumMaster (certified of course), and then tell him/her what to do on the team, based on your (uncertified) ideas of scrums from all those rugby games you watched last year.
- Test files should exist to give the appearance of caring and design.
- Popular libraries should be included to give the appearance of being cutting-edge.
- Always use the words agile, rock start, and ninja in your job ads whether they apply to your existing team or not
- Use the Presenter pattern because ... um... you should
- Replace your daily standup with your daily pivot.
Created
September 7, 2012 18:50
-
-
Save btaitelb/3668537 to your computer and use it in GitHub Desktop.
programming pretty good practices
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can we call this the "Ben Test" as the successor to the "Joel Test."