Yesterday, Manuel Rivero and I facilitated a workshop using the tire pressure TDD microexercise. (More microexercises can be found in this category, also here)
We scheduled the session as follows:
10 minutes introduction to the exercise 10 minutes to download the code and take a first look 10 minutes explanation about the exercise, what the problem is, etc 30 minutes for the attendees to explore the solution (on their own) 10 minutes for commenting the explored solutions, comments about it 40 minutes of prepared kata format 10 minutes of final explanations, questions and answers (Q&A) Total: 120 minutes or two hours, approximately
Books I’ve read this quarter Q1 on 2015, as inspired by Manuel, on this post:
Fifty Quick Ideas to Improve your User Stories, by Gojko Adzic and David Evans Fun retrospectives by Taina Caetano and Paulo Caroli Implementation patterns by Kent Beck Clean code by Robert C. Martin; again Books started, not yet finished (WIP):
The Well-Grounded Java Developer, by Benjamin J. Evans and Martijn Verburg Refactoring, by Martin Fowler, (with Kent Beck, John Brant, William Opdyke, and Don Roberts) Growing Object-Oriented Software Guided by Tests, by Steve Freeman and Nat Pryce Flow, by Mihaly Csikszentmihalyi (Note: I’ve written this list a posteriori, in May 2015)
This is the first post is of the growing-software series
A few weeks ago, while reading the book Growing Object-Oriented Software Guided by Tests by Nat Pryce and Steve Freeman, I finally understood why the software needs to be grown and not built:
A few days ago, I was thinking about new inspiration sources and this came to my mind:
In agriculture, at least in this latitude, there are different seasons.
Adrian Bolboaca has written a very interesting post on being a community bumble-bee. (Source can be found here)
He goes on to explain how he has visited many meetups all over Europe and the big chunk of information and experience he has learned from them.
He tells us about a selfish approach to organizing meetups:
When one teaches two learn
(apparently attributed to) Robert Heinlein, source
I share this feeling of learning while teaching, as long as you reflect and analyze (e.
Today we’ve discussed about code reviews on this open space
Notes These are my notes, in no particular order:
reduce information silos all around the company, as everyone [technical] can participate in these events raise the “just arrived” people’s knowledge [Difficult to hit the ground up and running, but these code review sessions can help] invest one person as ‘sheriff’ for the sprint: they will take care of static analysis tools (such as sonar) and continuous integration (CI; such as jenkins).
Yesterday we organized a TDD meetup at the FIB - Barcelona School of Informatics UPC, within Barcelona Software Craftsmanship sponsored by the Junior Empresa d’Informàtica. The meetup started at 9:00 until 18:00, with a one-hour pause in the middle.
Where Please make sure the meetup space (e.g., classroom, meeting room) is available and ready to be used at least 15 minutes before the meetup starts The organizer and the event host should be there in advance to prepare the physical environment (chairs, wifi, beamer, etc) as well as mentally: getting comfortable with the space, loading the presentation, prepare the speaker notes, etc.