addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupsimageimagesinstagramlinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1outlookpersonJoin Group on CardStartprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

The Metrics Trap

  • Jul 15, 2013 · 7:00 PM
  • This location is shown only to members

If you have a large code base, you have to do something to start to grapple with it. Unfortunately, the work you do in the beginning does not make an appreciable difference. You have to adopt new testing, design, and investigative practices. Ease comes with a bit of time. This dark spot in the timeline of a project is often troubling for management and the team. Everyone wants to see and know progress, and is tempting to pick a set of metrics and use them as measures of progress.

This month, Michael Feathers will discuss various ways he's seen teams become trapped by this tendency and describe alternatives which make refactoring transparent with progress indicators which relate to real value.

Join or login to comment.

19 went

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy