He started out as a software developer in the late ’90s and later moved on to the role of architect. He now guides organisations in their cloud adventure, with a strong focus on cloud native software development.
Watch the teaser of his keynote presentation!
Work is already well underway for next year’s unconference. Read on to learn more about what happens when, the confirmed keynote, call for speakers and new website.
Timeline for 2014
We’ve created the first iteration of the plan for this year. In case you were wondering, here are the key milestones between now and the end of 2014:
- Sep 03: New website goes live
- Sep 03: Call for papers opened
- Nov 03: Registrations opened
- Nov 10: Program announced
As we announced in May, we already have confirmed one of the keynote speakers for 2015. Simon Brown is a renowned architect and trainer on agile architecture and author of Software Architecture for Developers. With a schedule as busy as his, we’re sure glad it matched our dates for next year’s I T.A.K.E Unconference.
Call for speakers open
We have opened the call for speakers. For next year we decided to keep the topics that you hold dear: architecture, design principles, TDD etc. and also add some new areas that are becoming more and more popular these days: mobile, big data, scaling architecture etc. Visit the page to learn more.
If you know somebody that has something valuable to share with our audience, we’d appreciate it if you shared the link for the call page.
We hope you enjoy the new website we’ve created. Based on your feedback during the past two years, we decided to come up with a new design that is accessible on all mobile devices. We’d like to thank our partners at Gorilla Studio for their effort and creativity with the new design.
We’re really excited for next year’s edition! So far things look great and we are committed to delivering the best edition yet to all our attendees. See you there?
Do you like the new website? Have any questions about the call for papers or the unconference? Let us know in the comments.
Until recently, layered architecture was the most common way of organizing large applications or modules. We’ve learned from practice that it has limitations:
- business rules tend to escape or be duplicated in UI and/or data layer
- switching from a database to another is very difficult
- adding another UI to the application (eg. mobile or smart client) requires heavy changes
- changing a library used by the application with another is often complex and risky
A new architecture style has appeared in the recent years that tackles this problem: Hexagonal Architecture, or Ports & Adapters. Its intent is to allow more flexibility by cleanly separating business rules from everything else.
Johann Martinsson and Rémy Sanlaville have described the basics of Hexagonal Architecture and then shown an example of such an architecture.
Enjoy their presentation @ I T.A.K.E. Unconference 2014 edition. Curious about 2015 edition?
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.
- IMPORTANT: Register to the contest latest one day before I TAKE Unconference by sending an email to email@example.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
To simplify the jury’s decision, the performing kata has to conform to the following constraints:
- 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)
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:
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.
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.