Reading GOOS (XI)

These are the links mentioned in our last conversation about the 15th chapter:

• Talks:
  • La economía del refactoring. Una visión desde la gestión económica del proyecto. by Xavi Gost
  • MIT 6.001 SICP, 1986 Lecture 3A by Harold Abelson
• Posts:
  • Object Functional Patterns at C2 Wiki

Reading GOOS (X)

These are the links mentioned in our last conversation about the 14th chapter:

• Talks:
  • Design How Your Objects Talk Through Mocking by Konstantin Kudryashov
• Posts:
  • JMock v. Mockito, but Not to the Death by J. B. Rainsberger
  • Is it possible to do strict mocks with Mockito?

Reading GOOS (IX)

These are the links mentioned in last two weeks conversations about the 12th and 13th chapters:

1. Posts and Papers
   • Decorator Pattern in C2 Wiki
   • Aspect Oriented Programming in C2 Wiki
   • Object Collaboration Stereotypes by Steve Freeman
   • What the tests will tell you by Steve Freeman
   • Getting It Right By Betting On Wrong by Sandi Metz
2. Talks
   • Workflows of Refactoring by Martin Fowler

Reading GOOS (VIII)

These are the links mentioned in this week's conversation about the 10th and 11th chapters:

1. Code samples
   • Source code for the book by Steve Freeman
2. Posts and Papers
   • ArrayBlockingQueue Java Documentation
   • Mock Roles, not Objects by Steve Freeman, Nat Pryce, Tim Mackinnon and Joe Walnes
   • Clean architecture / never test the GUI? from Clean Code Discussion Google Group
   • Robert Martin compares GOOS outside in approach with his inside out approach from Growing Object-Oriented Software Google Group
   • State vs Interaction Based Testing by Nat Pryce
   • Mocks Suck from Growing Object-Oriented Software Google Group
   • Outside-In vs Inside Out – Comparing TDD Approaches by Matt Wynne
   • Reflective Design by James Shore
   • Some mocks by Steve Freeman
   • Perfecting OO's Small Classes and Short Methods
   • Presenter First: Organizing Complex GUI Applications for Test-Driven Development
   • Mocks and Tell Don’t Ask by Ian Cooper
3. Talks
   • Clean Architecture by Robert C. Martin

Reading GOOS (VII)

These are the links mentioned in this week's conversation about the 8th and 9th chapters:

1. Code samples
   • Kata Roar by Guillermo Pascual
   • Simple Pet Store by Vincent Tencé
   • Growing OO Software in Ruby by Brian Marick
   • GOOS in Ruby by Kerry Buckley
2. Posts
   • Taller Diseño modular dirigido por pruebas by Eduardo Ferro and Nestor Salceda
   • Simple Web Development In Java by Vincent Tencé

Reading GOOS (VI)

These are the links mentioned in this week's conversation about the 7th chapter:

1. Posts and papers
   • Traits: Composable Units of Behaviour by Schärli et al
   • Shotgun Surgery
   • Refused Bequest
   • EncapsulatedCollection by Martin Fowler
2. Talks
   • Primitive obssesion and Value objects conversation between J. B. Rainsberger and Corey Haines (part 1)
   • Primitive obssesion and Value objects conversation between J. B. Rainsberger and Corey Haines (part 2)
3. Books
   • On Lisp by Paul Graham

Reading GOOS (V)

These are the links mentioned in this week's conversation about the 6th chapter:
Posts and Papers

• Encapsulation Definition in C2 Wiki
• Information Hiding Definition in C2 Wiki
• Encapsulation Is Not Information Hiding in C2 Wiki
• Tell Above, and Ask Below - Hybridizing OO and Functional Design by Michael Feathers
• The Four Elements of Simple Design by J. B. Rainsberger
• Clean Code Tip #12: Eliminate Boolean Arguments by Robert C. Martin
• Is Dependency Injection like Facebook? by Steve Freeman
• Object-Oriented Theater by Matteo Vaccari

Reading GOOS (IV)

These are the links mentioned in last week's conversation about the 5th chapter:

1. Posts and Papers
   • Responsibility Driven Design with Mock Objects by Marc Evers & Rob Westgeest
   • Responsibility Driven Design with Mock Objects (talk slides) by Marc Evers & Rob Westgeest
   • A Laboratory For Teaching Object-Oriented Thinking by Kent Beck and Ward Cunningham
   • How I Learned to Stop Worrying and Love the Mock by Arlo Belshee
   • How to design not to duplicate procedural workflows between test and implementation? GOOS Google Group
2. Talks
   • Why You Don't Get Mock Objects by Gregory Moeck

Reading GOOS (III)

These are the links mentioned in this week's conversation about the 4th chapter:

1. Posts
   • Beyond Test Driven Development by Liz Keogh
   • Walking Skeleton by Alistair Cockburn
   • Design as Knowledge Acquisition by Alistair Cockburn
   • Elephant carpaccio by Alistair Cockburn
   • Forget the walking skeleton – put it on crutches by Gojko Adzic
   • Another way to think about geeks and repetitive tasks by Jon Udell
   • Simplicators by Nat Pryce
   • Ports, Adapters and Simplicators by Nat Pryce
   • Walking Skeleton on C2 wiki
2. Talks
   • Decisions, decisions by Dan North
   • Fractal TDD: Using tests to drive system design by Steve Freeman

More links next week.

Reading GOOS (II)

These are the links mentioned in this week's conversation about the second chapter:

1. Talks
   • Boundaries by Gary Bernhardt
2. Books
   • Object Design: Roles, Responsibilities, and Collaborations by Rebecca Wirfs-Brock and Alan McKean
   • On Lisp by Paul Graham
3. Posts
   • Tell Don't Ask by Martin Fowler
   • Tell, Don't Ask in The Pragmatic bookshelf
   • Telling, Asking, and the Power of Jargon by Dave Thomas
   • Keep It DRY, Shy, and Tell the Other Guy by Dave Thomas and Andy Hunt
   • Law Of Demeter in C2 Wiki
   • The Law of Demeter Is Not A Dot Counting Exercise
   • JMock v. Mockito, but Not to the Death by J. B. Rainsberger
4. Some code smells
   • Shotgun Surgery in C2 Wiki
   • Inappropriate Intimacy in C2 Wiki
   • Refused Bequest
5. A kata
   • Kata Lonja

More links next week.

Bonus:

• Jason Gorman refactoring Feature Envy
• Jason Gorman refactoring Inappropriate Intimacy
• Jason Gorman refactoring Message Chains
• Jason Gorman refactoring Subtle Message Chains

Reading GOOS (I)

I'm reading Growing Object-Oriented Software Guided by Tests along with several friends from the Aprendices community.

In the next months I will be posting here resources to complement the book that are mentioned during our conversations about each chapter of the book.

These are the ones mentioned in this week's conversation about the preface and the first chapter:

1. Talks
   • Better is better by Steve Freeman
   • Design How Your Objects Talk Through Mocking by Konstantin Kudryashov
   • BDD con Javascript by Carlos Blé
2. Books
   • Test-Driven JavaScript Development by Christian Johansen
   • Implementation Patterns by Kent Beck
   • Specification by Example: How Successful Teams Deliver the Right Software by Gojko Adzic
3. Posts
   • Iterating and Incrementing to 'Get What You Need'
   • Visualising Test Terminology by Nat Pryce
   • Robert Martin compares GOOS outside in approach with his inside out approach debate at GOOS Google Group
   • Passive View
   • Big, Complex, and Tested? Just say “WHEN”. Software Development Using Presenter First
4. Test Pyramid
5. The Four Elements of Simple Design by J. B. Rainsberger
6. Putting an Age-Old Battle to Rest by J. B. Rainsberger

As you can see, we started talking about the book and then drifted a bit to talk about other somehow related topics.

More links next week.

Bonus: Michael Feathers and Steve Freeman on Design

Agile Development Course 2013 beCode

I meant to write this post right after the course but, well, better late than never.

Last year I attended the Agile Development Course taught in Valencia by Ricardo Borillo, Xavi Gost, Emma López and Miguel Ángel Fernández from (at least in that moment) beCode.

From April 5th to June 1st I travel from Barcelona to Valencia by train every week (the classes were from 16:00 to 20:00 on Fridays and 09:30h a 13:30h on Saturdays) to go to class. It was a lot of effort but I considered that it was totally worth it.

The course syllabus was composed of four parts each of them taught by a different person:

• Methodologies with Emma.
• QA with Miguel Ángel.
• Tools with Ricardo.
• Code with Xavi.

Bit by bit we entered the world of the Agile Manifesto, XP, TDD, refactoring, design and implementation patterns, git, SOLID, BDD, retrospectives, user stories and many other interesting things. The classes were great both because of the contents and the experience of the teachers. They always enriched every matter with their own experiences as agile and extreme developers.

My course mates were a group of very nice people mainly from Valencia and Castellón. I think that only Nico and I were coming from other provinces. Some of them have become good friends with whom I still keep in touch: Nico Cortés, Paulo Clavijo, Fermín Saez and Gabriel Moral.

During those two months I learned, read, discussed and practiced a lot and I got to know many things that I'm still working hard to learn. But, even more important than all that, was finding that there were better ways of making software at the reach of my hand.

This course was a game-changer for me. If there's a new edition this year I recommend it to anyone who wants to learn about software development with an Agile flavor.

To finish I'd like to thank both the teachers and all my course mates for having made this course so great.

----------

PS: Another indirect outcome of this course was the Aprendices community created by some of the students. At the end of the course, we decided to create the community so that people from outside the course could participate in our reading club and also see all the interesting links we have had shared during the course. The community was named after the caption that Fermín Saez uses in his LinkedIn profile. This is how Aprendices came to life last June.

Interesting Panel: "Commenting TDD, where did it all go wrong"

This week I watched this great panel commenting Ian Copper's talk TDD, where did it all go wrong:

• Commenting TDD, where did it all go wrong (in Spanish)

After watching Ian Cooper's talk a month ago, we started to try to bring together some of the more experienced members of Aprendices to form a panel in which they could debate about the ideas in the talk.

In the end a group of Spanish experienced TDD-practitioners joined the panel to share their experiences in TDD, BDD, design and many other things.

Thank you very much from here to all of them: Luis Artola, Miguel Angel Fernández, Enrique Amodeo, Guillermo Pascual, Javier Acero, Ricardo Borillo and Eduardo Ferro.
Also many thanks to Jaume Jornet for kindly taking the moderator role.

Interesting Panel: "¿Cómo usamos git en nuestro día a día?"

Last month Pepe Doval and some other Aprendices members held a very interesting hang out where they talked about the way they use Git:

• ¿Cómo usamos git en nuestro día a día?

This was the first Hang Out that arose from the Aprendices community.

I'd like to personally thank Pepe Doval, Raúl Tierno, David Vílchez, Nicolás Cortés, Gabriel Moral and Carlos García for taking part in it.

Interesting Talk: "It's not your test framework, it's you"

I've just watched this interesting talk by Robbie Clutton and Matt Parker:

• It's not your test framework, it's you

We've found many of the advices to make BDD sustainable that they give in this talk, in the book we're currently reading in Aprendices Reading Club: Gojko Adzic's Specification By Example.

Interesting talk: "Challenging requirements"

I've just watched this great talk by Gojko Adzic, the author of the Specification by Example book that I'm currently reading:

• Challenging requirements

Thanks to Guillermo Pascual for recommending it in the Aprendices community.

Some talk highlights:

Refuse solutions to unknown problems:
understand what the real problem is and solve that.

Refuse suggestions to use a particular technology:
you know IT better than they do (if not, why have they hired you?).

Don't rush into solving the first problem they give you:
keep asking "why" (or "how would this be useful") until you get to the money.

Know your stakeholders:
who is going to use this and why?

Don't start with stories!:
Start with a very high level example of how people will use the system.

Great products come from understanding the real problem and whose problem it is.