Enjoy the following series of interviews with the speakers, top-notch software crafters from across Europe, joining I T.A.K.E Unconference, Bucharest, 19-20 May. Discover the lessons learned and what drives them to challenge the known path in their field.
Andrey Adamovich, Software Architect at Aestas IT, is a software craftsman with many years of experience in different lifecycle phases of software creation. At I T.A.K.E Unconference 2016, he will share more patterns for infrastructure-as-a-code and visualizing codebases.
#1. Share with us 5 things you did that helped you grow & become the professional you are today
- Leaving my first workplace, where I have worked for 5 years
- Becoming an active public speaker
- Co-organizing local communities and conferences
- Developing open-source libraries
- Writing a book
#2. What challenges will the participants find solutions to during your session at I T.A.K.E Unconference 2016?
Visualizing codebases: Seeing big picture in a big code base with simple tools
Patterns for infrastructure as code: Give some hints on how to improve quality of “infrastructure-as-code”
#3. What else would you like to share with participants
Developer | Entrepreneur | Open-source Enthusiast | IoT Player | DevOps Believer | Visualization Lover
Want to join Andrey and many more software crafters from around Europe?
Join I T.A.K.E Unconference 2016!
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.
Call for Speakers Opened
Send your proposal to become a speaker at I T.A.K.E. Unconference 2019. This year we are interested in specific topics, and choosing one of them might get you closer to becoming a speaker.
To increase your chances to become accepted, here are some tips:
#1. Get into the attendees shoes
If you have a very clear idea of who your audience is going to be, make the exercise to think from their point of view. They choose to attend your session, and they expect the best value from their investment.
#2. Customize, customize, customize
Every audience is unique, so craft your proposal according to what you know about your audience and about the event. Try to bring an original approach for each session you submit.
#3. Pay attention to details
When you apply, make sure you have an excellent title, a clear description of what you want to present and a strong personal bio.
#4. Invest time in your application
Although it might seem at hand, making a proposal takes time. Make sure you follow the guidelines offered by the organizers and when in doubt, ask for more details. Make sure you offer the details requested in the application.
#5. And a little extra thing
You’ve seen the call, you got your information in order and you are pretty sure you want to make a submission.
You can read more in detail about our tips here.
Have any questions about the call for papers or the Unconference? Let us know in the comments.
In-Process or Inter-Processes Communication at Deploy Time
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.
Florin Coroș, Co-Founder and Partner iQuarc, is a passionate software architect and developer who has been working for more than 10 years in a wide variety of business applications using Microsoft technologies. At #itakeunconf, Florin is sharing more about In-Process or Inter-Processes Communication at Deploy Time.
#1. Please share with us 5 things you did that helped you grow & become the professional you are today
There might be a fortunate series of events, which fit nicely with my personality and abilities.
One of the things that helped me a great deal, was the fact that I changed the contexts and projects often. Even if I worked for the same company and the same technologies for about 10 years, I have changed the projects, the clients and my role at least once in two years. It wasn’t something that I had planned, but I always wanted to learn and experience new things.
Change is always challenging and creates opportunity for learning and for professional growth.
Another important thing for me, I think it was the fact that I always look for professional models. First, I discovered Uncle Bob, then there were Martin Fowler, J.B. Rainsberger, Roy Osherove, Kent Beck, Juval Lowe, Jurgen Appelo, Richard Campbel, and many others (I remember having a slide with some of these guy’s pictures in one of my first talks I’ve given at a conference ☺ ). Reading their books and articles, and then trying to apply their ideas in my day to day work, inspired and helped me.
Attending to training and conferences is another important thing. The TDD workshop with J.B. Rainsberger, which I attended back in 2010 was a few years jump ahead in my career. After, there were many other high-quality training I had the opportunity to attend, like the IDesign Master Class with Richard Campbel, a workshop with Dan North, or a Requirements course with Kay and Tom Gilb.
Coding just to practice is another thing that makes a difference. I learned this at the Code Retreats and I’ve kept this good habit. From time to time I take a few hours and I just write code with the purpose of learning or practicing. It always pays back.
#2. What challenges will the participants find solutions to during your session at I T.A.K.E Unconference 2017?
In large enterprise applications, there is always the challenge of decomposing the system. From performance considerations we may end up loading all the services in one or two processes, ending up with a monolith, which doesn’t scale and it is costly to maintain. At the other end, we have one process for each service resulting in too many inter-process call hops to handle one user request, which is bad for performance and it may be costly to maintain.
I’ll show a way, which I’ve applied in some projects I’ve architected, on how to separate this communication concern from implementing the business functionality.
#3. Recommend for the participants 3 sources you find inspiration from and would help them better understand you
- My blog of course ☺ onCodeDesign.com . There, it is more about me and my thoughts
- .NET Rocks (https://www.dotnetrocks.com/) is a podcast I recommend especially to .NET developers, and also to any geeks
- As a hobby, I recommend learning and playing GO. Even if it a time-consuming game, it is a very good exercise for the mind.
Want to meet Florin, +30 international speakers and ~300 software crafters from around Europe?
Register now for I T.A.K.E Unconference 2017!