Completely unexpected of what is there, I registered for Coderetreat that’s held at Nelkinda which was on 16th of July 2016. Facilitated by Siddhesh Nikude and Shweta Sadawarte it was a long but a really nice event. More than anything else I got to learn a lot from that event and I will write some of my experience here.

The session was split into code sprints and retrospectives. There was a 45 minute of code sprint followed by a 30-minute retrospective. For every code sprint and retrospective cycle, they kept two people to write one code to enforce pair programming. For the first code sprint retrospective cycle, the pairing was done by splitting people into two types, one were the ones who had done TDD before and the others who had not done TDD and/or had heard about TDD before. We were given a problem to solve. The aim of the code sprint was not to solve the given problem but to focus on the practices such as clean code, writing tests and following TDD. We were also free to choose the language of our choice rather than enforcing a language upon us.

code_retrospective
One of the retrospective, me in yellow telling what happened in the code sprint

The way the whole event went

Initially, I was paired with another student who was not very familiar with TDD. I started by introducing him the red-green-refactor cycle. But these are the things that I have learnt on my own and have not worked in an industry and/or done any projects this way to do it the right way. So I was not knowing if I am doing this the right way or not. Finally, at the retrospective session I came to know that I was doing this at least 90% of times the right way. The problem that was given to us was tic tac toe. We had to design a two player tic tac toe game. For eg: if player 1 plays, then, player 2 will play, then the player 1 and it will keep alternating till either of the players wins or if the board is full. So, we started from initially deciding how the board is structured and so on what kinds of methods to use to design this. At the retrospective session, we came to know about each other’s approaches and shared a lot of knowledge about the right way to do things and not so right way to do things. The initial discussion was about what data structure was chosen for the board. The people using Java chose ArrayList the others chose two-dimensional array. I chose Python List since I was using Python as my language.

For every subsequent code sprint, we had to delete the code and start from scratch. The approaches took a totally different turn when the discussion went to the clarity of code in the subsequent code retrospective. The expert programmers started bashing loops and how it makes the code unreadable. Even I like to avoid using loops, esp. in Python it’s really easy to use lambdas and different types of comprehensions. Hence, things that need multiple loops can be reduced to just a couple of lines of readable code.

In between, I switched from Python to Java because I was paired with a person who was unaware of Python and knew only Java. In Java, I had to go through the JUnit framework and tried to use functional programming concepts. As I come from a Python background, I am used to lambdas and comprehensions. I tried to do the same using the Java 8 lambdas and ArrayList on which I could run the lambdas. It was a crazy experience and a pretty steep learning curve since I’ve never used lambdas in Java before. Also, my partner was not very comfortable with lambdas and quite a lot of time was spent in both of us learning how it works.

Later I was paired with my friend Douglas Vaz who introduced me to a new way of writing code that is BDD. “BDD is TDD done right” this is the statement most of the blogs and or websites all over the internet contain. From what I’ve learnt, in BDD you don’t have to think about the implementation of the feature that you are going to test. Instead, just write a test about the behaviour or the flow of the feature that you are testing and then go on modifying the main code to pass all the tests.

This all was a very wonderful experience, what I’ve written here is barely scratching the surface, in reality, you have to be there to feel the way clean coding is done, esp. when you are paired with others. Finally, we sat and refactored all the code till we finished off the whole problem. The code on tic-tac-toe is really messy in spite of using multiple techniques and hence I’ve decided to rewrite the code in the right way and then post it here or maybe write another blog on that and put the link here.