Today I have done a brown bag session about refactoring legacy code. It includes: legacy code definition. There is no agreement about this in the team. the legacy code change algorithm (source is Feathers, Working effectively with legacy code). Plus an example about it. working with legacy code experience with it. The slides are available here (PDF format) We also did a practical session, whose experience report is here

I’ve grouped all small posts related to the self-study from July 2015 into a single post Clojure made simple I’ve watched this talk by Rich Hickey at the Java One. It references the talk Easy made simple polymorphism without inheritance; single dispatch on the first parameter Productive pair programming I’ve read this article about pair programming, using the driver & copilot technique, written by Carlos Blé Building Automated REST APIs with Python Investigating QA automation for REST APIs, I’ve read these slides about it

Books I’ve read this quarter Q2 on 2015: Flow by Mihaly Csikszentmihalyi. Blog posts under the tag flow Growing Object-Oriented Software Guided by Tests by Steve Freeman and Nat Pryce. Blog posts under the tag goos. Read in the ‘@deAprendices’s reading club’. TDD in Java, by Viktor Farcic and Alex García. I’ve reviewed this book. Books started, not yet finished (WIP): The Well-Grounded Java Developer by Benjamin J.

We’ve read the first chapter from the Practical Object-Oriented Design in Ruby, by Sandi Metz. These are the concepts and links brought up during the discussion: Walking on water and developing software from a specification are easy if both are frozen. Edward V Berard, source is Wikiquote Two cited papers on metrics for design: A metrics suite for object oriented design by Chidamber and Kemerer A validation of object-oriented design metrics as quality indicators by Basili, Briand and Melo The video for the ‘churn’ as a measure:

Today I have facilitated a brown bag session about refactoring legacy code applications, as this is the case with one of the applications we maintain and add new features to. The contents of the session: Briefly exposing the problem to the team, me taking the role of the Product Owner (PO) Ask the dev team to add an easy feature Do it without tests, as it was so simple that they thought they could do it (using mob programming) Ask if they were satisfied by the patch / fix.

Today we have done a brown bag session about Docker. One of the team members explained to us the latest news, topics and how tos, including: the difference between a container and an image diffing image contents AUFS (Another Union FS) persistent vs non-persistent (volatile) filesystems running CMD and other commands on the instance problems of running with permission = root (or its group) downsides of it how to compare it with a virtual machine