And…it’s a wrap: 2 days of intense & complex program, 300 international participants, more than 35 sessions & more than 35 speakers from United States, Europe and Asia. During the 2nd day of the event, 15 speakers from 10 countries shared their knowledge on Machine Learning, IoT, Evolutionary Design, Documentation for Software Developers, Impact Mapping and more.
Videos are available here. Find below the presentations from day 2. The slides from day 1 are here.
Romeo Kienzler – Realtime- Cognitive IoT using DeepLearning and Online Learning on top of ApacheSpark Streaming and Spark enabled DL frameworks (keynote)
Dan Billing – Testing or Hacking: Real Advice on Effective Security Testing Strategies (keynote)
Eduards Sizovs – Beyond Software Craftsmanship (keynote)
Dan Serban – Introduction to Apache Spark
Jakob Holderbaum – Managing Shared Secrets with basic Unix tools
Florin Coros – Decide between In-Process or Inter-Processes Communication at Deploy Time
Peter Kofler – Brutal Coding Constraints
Joe Wright – Tackling 16 years of legacy code with mob programming and Lego
Alin Pandichi – Covariance and contravariance. Say what?!
Patrick Baumgartner – Impact Mapping Workshop
Liviu – Stefanita Baiu – Journey to Agilandia – a BA Travel Kit
More slides and videos from day 2 coming soon
First two confirmed keynotes
Simon Brown, award-winning speaker and author of Software Architecture for Developers – a developer-friendly guide to software architecture, technical leadership and the balance with agility. Simon has provided consulting/training to software teams in over 20 countries, ranging from small startups to global blue chip companies. He blogs @ www.codingthearchitecture.com Tweet him @simonbrown
James Lewis, Principal Consultant, introduced evolutionary architecture practices and agile software development techniques to various blue chip companies: investment banks, publishers and media organisations. He blogs @ http://bovon.org More about his take on Microservices here where he worked jointly with Martin Fowler.
Have any questions about I T.A.K.E. Unconference 2015? Let us know in the comments.
[newsletter-form]
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.
Documentation for software developers
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.
Peter Hilton is a software developer, writer, speaker, trainer, and musician. Peter’s professional interests are business process management, web application development, functional design, agile software development, and documentation. He will present at #itakeunconf a session about documentation for software developers.
#1. Please share with us 5 things you did that helped you grow & become the professional you are today
The things that helped me grow the most were starting to do something that I later developed a lot further: travel, presenting, writing, management, and coding. These influences on my professional development were taking overseas assignments and later moving permanently to another country, presenting to colleagues and later at conferences, writing a tech blog and later a published book, leading a team and later taking on a management role. As for coding, the most important thing was to never-never give it up and always have something new to learn.
#2. What challenges will the participants find solutions to during your session at I T.A.K.E Unconference 2017?
My workshop will help participants address the hardest challenge in software documentation: learning how to take the first step from no documentation at all to the minimum viable documentation. The hard part is understanding what you can do, without wasting time on too much documentation.
#3. Recommend for the participants 3 sources you find inspiration from and would help them better understand you
iMy passion is figuring how to explain software and make it maintainable. I was originally inspired to learn more about this after reading Steve McConnel’s book Code Complete, as well as many other books about software development. I discuss my favourite aspect of making code understandable in my Software Engineering Radio interview on naming things.
I’ve always found talking to other people the best way to develop and refine my own ideas. This inevitably lead to conference presentations, for which my greatest influence is Kevlin Henney’s presentations.
Perhaps my greatest inspiration is the real world, which I enjoy exploring. My favourite way to learn about a new city and immerse myself in it is to explore its cafes, which I started doing on business trips and overseas assignments when I had a hotel room instead of a home to stay in. Writing cafe reviews on my own web site, before the likes of TripAdvisor was invented, was also how I started to explore writing. Today, there’s still probably as much writing about cafes as about programming on my own blog.
Want to join Peter and ~300 software crafters from around Europe?
Register now for I T.A.K.E Unconference 2017!