Yesterday we did a training about the maven tool. One of the team members explained to us some topics including: lifecycles profiles and how to create one slowTests for integration tests (this client only) downloadJavadoc downloadSources convention over configuration scopes of the dependencies (test, runtime, compile, provided) tricks about the tool: order of the dependencies (especially junit, hamcrest) plugins and how to build one destination folders target, classes, test-classes, etc Note: this post was created a posteriori, with the original date

Yesterday at the clojure meetup we1 did the mars rover in clojure and today I’ve tried my hand at it again. Original, from the three of us here and my results here Jorge Ávila, Jesús Díez and I ↩︎

Last Friday we did a kata1 using a projector the string calculator 2 using pair programming, TDD and some mob-programming for the last refactoring. We used a projector (beamer) so everyone could see it. I tried to take really small baby steps but the adding part was done in ~6 cycles3 We’ve all learnt about shotcuts, live user templates for the IDE 4, TDD methodology, other ways of tackling the problem, how to refactor as a group, clean code, etc

A quote from the Mythical Man-Month: Chapter 13: The Whole and the Parts […] In System/360 engineering models, one saw occasional strands of purple wire among the routine yellow wires. When a bug was found, two things were done. A quick fix was devised and installed on the system, so testing could proceed. This change was put on in purple wire, so it stuck out like a sore thumb. It was entered in the log.

I’ve just written a new kata, about a persistent linked list. It is using the same project as for the linked list kata. For now, only the add, contains and size methods are implemented. If you have any comments or code review, please let me know

The toolsmith Frederick P Brooks, Jr quoted / explained a theory explained by Mills and Baker1 around 1971-72: Chapter 3: The Surgical Team […] but the team be organized like a surgical team rather than a hog-butchering team. That is, instead of each member cutting away on the problem, one does the cutting and the others give him[her] every support that will enhance his[her] effectiveness and productivity. […] Brooks, F.