Lean Coffee Notes
Matt Heusser
Cool Books
Thinking Fast and Slow, Kahneman
You are not so smart, David McRaney - Biases and what to do about it
You are now less dumb, David McRaney - Biases and what to do about it
Pragmatic Thinking and Learning, Andrew Hunt
Scrum: Twice in half the time, Jeff Sutherland (not great)
The peopel’s Scrum, Tobias Mayer
Quiet: The power of introverts in a world that can’t stop talking, Susan Kane
Zero to One, Peter Theil
Being Agile, Mario Moreira
The paradox of Choice, Barry Swartz
http://www.ted.com/talks/barry_schwartz_on_the_paradox_of_choice
Freakonomics, Steven Levitt
Mindset: The New Psychology of Success by Carol Dweck
As you Wish: Inconceivable Tales from Making of the Princes Bride, Cary Elwes
Beginning with Test Automation
Large enterprise, tried tools before, just restart
Ability to run tests in parallel is important
One obvious overhead is people ‘losing a vm’
If you search through your code for domains and what machines are being used sometimes you get kind of a shock.
Better to do one test all the way through CI end-to-end than slowly
We worked with one LeanDog client that did end to end overnight but headless and automated. Typical tools we used included fitnesse, cucumber, hudson.
We had 7,500 cucumber scenarios that ran over 550 hours. Crazy. Our approach was to go through the user interface. I’d suggest design and architecture. Better to test deliberately at all layers - you need a seat at the design table with the dev teams.
(Host) Devs want input from us on how to make things more automatable, including something like TDD perhaps with different words.
Devs want input about testability - code planning. Not just functions but how will you test security, performance, etc. We actually meet to see how far down we can push the tests.
At some level test automation is the original agile. We’ve always written tools to do some form of testing but only to the extent that it helps us. We abandon it when it doesn’t, which is sort of the idea of minimum viable product. I think testing infrastructure and architecture are under-explored. When developers write code they usually have some design principles; testers-turn-coders often don’t, so what they write is pretty brittle. As an industry I think we need to put more thought into architecture/design of the test frameworks.
Chris Woodruff
Date: Wed, 7 Jan 2015 06:14:45 -0800
From: matt.h...@gmail.com
To: code...@googlegroups.com
Subject: [CodeMash] Lean Coffee Notes
You received this message because you are subscribed to the Google Groups "CodeMash" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codemash+u...@googlegroups.com.
To post to this group, send email to code...@googlegroups.com.
Visit this group at http://groups.google.com/group/codemash.
For more options, visit https://groups.google.com/d/optout.