Skip to content

Instantly share code, notes, and snippets.

@btaitelb

btaitelb/gist:3668537

Created September 7, 2012 18:50
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save btaitelb/3668537 to your computer and use it in GitHub Desktop.
Save btaitelb/3668537 to your computer and use it in GitHub Desktop.
Download ZIP
programming pretty good practices
Raw
gistfile1.md

Programming Pretty Good Practices

  • 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.
@jpfuentes2
Copy link

Can we call this the "Ben Test" as the successor to the "Joel Test."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment