And…it’s a wrap: 2 days of intense & complex program, almost 300 participants, +30 sessions & +30 speakers. During the 2nd day of the event, 16 speakers from 11 countries shared their knowledge on Microservices, Autotesting & Design, Quality Practices, Architecture & Technical Leadership.
Watch the videos from the event here. Find below the presentations from day 2. The slides from day 1 are here.
Continous Deployment
Andrey Adamovich – Patterns for infrastructure as a code
Tugberk Ugurlu – Zero Downtime Deployment Golden Rules & Docker Changes the Way You Develop and Release Your Scalable Solutions
Thierry de Pauw – Continuous Delivery is more than just Tooling_Its a Culture
Thomas Sundberg – Definition of Done – Working software in production
Autotesting & Design
Thomas Sundberg – How deep are your tests
Franziska Sauerwein – Introduction to Outside in Test Driven Development (London School)
Alexandra Marin – Error-proof your mobile app
Ricardo Mendez – Flexibility Through Immutability
Quality Practices
Houssam Fakih – Never Develop Alone – always with a partner
Andrey Adamovich – Visualising Codebases
Architecture
Milen Dyankov – Microservices and Modularity
Clement Bouillier, Jean Hellou, Florent Pellet & Emilien Pecoul – Workshop around CQRS & Event sourcing
Technical Leadership
Hugo Messer – How to successfully manage remote teams
Flavius Stef – Is management dead
A few thoughts from the participants
- Very glad I attended, well worth the trip from UK
- It was a very well organised event. I really enjoyed it, the speakers have been inspiring and well prepared 🙂
- It was a pleasant learning environment – I hope you will continue to bring high-quality speakers in the event
Covariance and contra variance. Say what ?!
Enjoy the following series of interviews with the speakers, top-notch software crafters from across Europe, joining I T.A.K.E Unconference, Bucharest, 11-12 May. Discover the lessons learned and what drives them to challenge the known path in their field.
Alin Pandichi, Software Developer at MozaicLabs and facilitator of the monthly Coding Dojo meeting that is part of the largerBucharest Agile Sofware Meetup Group, will share during his talk at I T.A.K.E Unconference more about Covariance and contravariance.
#1. Please share with us 5 things you did that helped you grow & become the professional you are today
I’ll answer this with a little bit of story telling about how I became a software developer. The first two things that helped me were attending the computer science oriented high school and college. There, I learned the basics of computers and programming languages. I also noticed how effortlessly I was solving CS related problems, so maybe I was onto something.
Number three: I got my first job straight out of college, developing a Swing rich client application saving data with JPA. This put me face to face with real world problems. I was faced with the fact that continuous learning is a must in this industry.
Therefore, number four on the list is learning. For the first few couple of years, I kept devouring every Java-related article I could find on DZone. With each one, I found out something new: a useful tool, a Linux terminal command, a development methodology, etc.
Last, but not least, is getting involved with local software development communities. I started attending meetups such as The Bucharest Agile Software Meetup Group and the Bucharest Java User Group. Gradually, I became an active member of both, giving a helping hand in organizing their events. On top of that, I also got involved in the wider community of Global Day of Coderetreat. My talk at I TAKE 2017 is one of the occasional opportunities I get to share what I know.
#2. What challenges will the participants find solutions to during your session at I T.A.K.E Unconference 2017?
They will find it easier to understand the concepts of covariance and contravariance, and how they are applied in the world of programming. In my experience, it was very easy to forget what these two words meant. Not anymore.
#3. Recommend for the participants 3 sources you find inspiration from and would help them better understand you
I dream big, so my biggest source of inspiration is science fiction. My first serious SF encounter was with Frank Herbert’s Dune series. Out of the contemporary authors, I enjoy Neil Gaiman’s work very much.
Whenever I get a chance, I tune into Nick Francis’ podcast called Quiet Music. It is a blend of low beat music of various genres: electronic, jazz, instrumental, folk, light rock, and so on.
Cinema is one of my other hobbies. I am very much interested in following every film festival happening in Bucharest. Also, the Romanian cinema of the past two decades has offered many gems so far, and it continues to do so.
Want to join Alin and ~300 software crafters from around Europe?
Register now for I T.A.K.E Unconference 2017!
Rebecca Wirfs-Brock: Maintaining Your Code Clint Eastwood Style
Rebecca Wirfs-Brock is the object design pioneer who invented the set of design practices known as Responsibility-Driven Design (RDD), the first behavioral approach to object design. She is the lead author of two software design books and design columnist for IEEE Software. By accident, she started the x-Driven Design meme (TDD, DDD, BDD…). Although best known for software design, she is has a passion simply expressing complex requirements and effectively communicating software architecture.
Rebecca shared with the audience how to maintain your code in the keynote address from the first edition of I T.A.K.E Unconference. Watch below her remarks!
Code. Craft. Learn. Share. Repeat. Call for Speakers for I T.A.K.E Unconference, 5th edition, is open! Apply here.
Programming contest @I T.A.K.E Unconference
As for every I TAKE Unconference edition, we want to give a chance to the software crafters from the audience to showcase their skills and learn more in the process. And because we appreciate passion, we offer a prize to those who convince a jury of well-known international developers that they are the most skilled in the room.
This contest is not meant to be easy. It will require you to practice beforehand, so please read the instructions carefully.
It will also require you to register before the event.
Mechanics
- IMPORTANT: Register to the contest latest one day before I TAKE Unconference by sending an email to steliana.moraru@mozaicworks.com
- On the first day of the event, after lunch, you have max 15′ to do a performing kata in front of the jury.
- The winner will be announced at the end of the second day
Constraints
To simplify the jury’s decision, the performing kata has to conform to the following constraints:
- Only the following programming languages are accepted: Java, C, C++, C#, Python, Visual Basic .NET, PHP, Javascript, Swift or Ruby
- Only solo contestants are accepted. Sorry, no pair programming this time
- The kata has to showcase refactoring skills.
- The kata has to last max. 15′
How we will judge
The jury will judge your refactoring skills.
The ideal kata looks like this – you will get maximum point if you:
- clearly state the smells you see in the code
- pick one of the smells
- clearly state your plan to fix the smell
- fix it in small, safe steps
- run tests after each step to prove you didn’t break anything
- commit after each step with a clear message explaining why you made the change
- fix as many smells as possible within the time constraint
You will loose points if you:
- make big or unsafe changes to the code
- break the behaviour after changing the code
- don’t improve the code a lot
- don’t improve the design by the end of the kata (hint: we judge design using SOLID principles and the four elements of simple design)
Recommendations
To help you, we’ve thought out what we would do if we participated to such a contest. Here’s what we recommend.
1) Use one of the following codebases for the kata:
- https://github.com/emilybache/GildedRose-Refactoring-Kata
- https://github.com/emilybache/Tennis-Refactoring-Kata
- https://github.com/emilybache/Yatzy-Refactoring-Kata
- https://github.com/emilybache/Parrot-Refactoring-Kata
2) Practice beforehand on the structure we presented for the ideal kata. Ideally find someone to practice with.
3) Watch other people refactoring. YouTube has many videos on the topic, including using the recommended code bases.
Glossary
A programming kata is a repeatable exercise used to practice specific skills.
Performing kata means doing a kata in front of an audience.
Refactoring means changing the internal structure of the code without changing its behaviour.