chris clarke

Compiler Warnings

This post about Compiler Warnings made me laugh.

Driving in to Trouble

Testing edge cases.

Every time I run in to something that gets in my way, slows me down or just annoys me I write it down on a card. If I run in to the same problem again - I add another notch to the card (like a tally). A colleague has a principle of Three Strikes and You’re Out - that is, if you come across the same problem three times you have to fix it. I also find it useful to take these cards along to retrospectives or stand-up meetings. Fixing these things that get in the way has really had a positive effect on productivity and made the team more interested in fixing bad things rather than taking the extra time and effort to work around them.

Awesome Clock

Building Circles with Googles Rounded Corners

Cool ideas

Found a few cool ideas following rachel’s blog, including silly hats for broken build. Also, liked the use of a status, such as ‘In Progress’ or ‘Customer Preview’ for each story on planning boards.

Having a further look around I found a fellow James-Shore-fan, who had come up with a interesting idea to be used at the end of a retrospective - a ROTI (Return On Time Invested) histogram.