So, how 2017 was for me? In a short answer, it was a good year. Professionally and personally was an interesting year. I switched jobs, I helped developers to learn TDD, I helped organizations to improve their agility, I started a podcast with a friend, I learned some Spanish2, I gave talks in tech conferences, I lost 14 Kg and I ran 500 Km.
Na Estrada DevOps podcast
Old gramophone, by Peter Heeling
Na Estrada DevOps is a podcast about DevOps, its practices, influences, and tendencies. I don’t remember when Fernando invited me to join him in this podcast, but it was one of the most fun things I did this year, no doubts.
The first episode was streamed in March and we recorded 16 episodes in total. With the help of special guests, we talked about Continuous Delivery, Infrastructure as Code, Test-Driven Development, Domain-Driven Design, about the role of Quality Assurance professionals and even about Design Thinking!
Implementing Domain-Driven Design Workshop
Vaughn Vernon’s IDDD Workshop: recommended!
In April I attended the Vaughn Vernon’s Implementing Domain-Driven Design Workshop. If you have the opportunity to attend a workshop with him, do it!
Vaughn allies a profound understanding of Domain-Driven Design with his vast experience in software development, explaining in simple language the strategies you have available to tame the complexity of your domain.
A true master.
Yes, I have a reasonable explanation for the talk’s subtitle.
It has been 5 years without giving a talk in a public technical conference. I had forgotten how fun it is to deliver content to a lot of people you never saw before.
I invested a lot of time to prepare both talks. The DDD introduction talk needed 16 days or more of work (research, the discovery of the narrative, preparation of the script and design of the slides). I got happy with the end result, it is my best talk to date. This talk was recorded at The Developers Conference São Paulo and is available online.
User Story Map all the things
User Story Mapping proved worth as a way to do a value-stream mapping.
After joining Easy, I helped to kickstart a transformation initiative with the goal to create collaboration and engagement in the product value stream through simple processes that will help the team to understand the whole picture of the product. The idea is to visualize improvements opportunities in the product development flow through a Kanban system and to feed it with right-sized stories discovered with Story Maps and defined in Story Workshops.
The initiative is in its very first steps but the usage of User Story Mapping did spread like wildfire. The early results are heartwarming, people are reporting a better communication, a better understanding of the new products to be developed and more easiness to prioritize what must be built.
However, the more interesting usage was to create a value-stream map of how we work. After explaining to one of my work colleagues that we would do a value-stream map, she suggested that we could use User Story Mapping for it. It worked like a charm, kudos to Helene Romanzini!
Write a failing test case, make the test pass, refactor it.
In the last three years, I had the opportunity to help other developers to learn Test-Driven Development in a more structured way, as a routine activity inside the companies I worked.
The creation of an environment of continuous learning is the most rewarding professional activity for me. And it is also something that pushes me to go further since I always learn something new when I help others to learn.
This year I had the opportunity to start a code kata in a team of 12 developers and the format is more than proved. Special thanks to Nelson Senna, which gave me precious recommendations of exercises.
Is that all? And 2018?
2017 was, in fact, a great year. It was the year that I finally worked on my work-life balance. It was a slow process that started after I decided to quit my previous job in January of this year. I disciplined myself, I started to eat better, started doing exercises and then the rest followed.
I lost weight, I had read almost one book per month, I enjoyed more time with my family, I made new friends and I stopped being busy all the time and got more productive.
Sure, it could have been a better year. My team fought against relegation, my favorite pub3 closed but what really saddened me was the phenomenon of entire families that started to live on the streets of the country. The coup d’état and the huge political turmoil worsened people’s life
But I am optimistic. First I hope we have the restablishment of a democratic government with a transparent election process. Then I hope that we use this as a learning that a democracy is a fragile thing to finally get back to the civilizatory process that was aborted in 2016. We need more rights and we need social justice, not the opposite.
Optimism is a strategy for making a better future. Because unless you believe that the future can be better, it’s unlikely you will step up and take responsibility for making it so. If you assume that there’s no hope, you guarantee that there will be no hope. (Noam Chomsky)
Professionally and personally I don’t have big plans. I hope to publish my findings on public speaking, User Story Mapping, Kanban and Test-Driven Development, I expect to participate more in technical conferences and to code more frequently. And if none of this happens, I will be more than happy to keep the regularity of the podcast.
For all, a great 2018!
Want to discuss this post? Reach me at Twitter!