foto: JDD Facebookk
This with no doubts interesting conference was held in Krakow on 13-14 of October and was mainly but not only oriented for Java enthusiasts from over the World.
This is going to be first part of Java Developers Days overview with some numbers, most interesting (as for me) ideas and short conclusions. Second part Marta Wożniak promised to write – and I truly believe her.
So let me start from numbers which are really great:
– 4 presentations threads;
– about 54 presentations itself;
– about 8 workshops;
– More than 300 attendees (from my prospective, but numbers could be slight different).
Detailed agenda You can find on official website – http://14.jdd.org.pl/agenda/agenda/13/, I’ll point only on several topics.
So first day of conference started for us (me and Marta) from 1 p.m. (flight was delayed for almost 5 hours due to weather conditions in Krakow) with “Using Ascii Art To Analyze Your Source Code With Neo4j And Oss Tools” topic from Michael Hunger. This one was really interesting so I’d like to add some details.
Main idea was in presenting your code as a graph database in which everything is connected in nodes through directed typed relationships. If we can represent our program in this way we’ll be able to run local queries for utilizing relationships which could be really helpful during analyze.
Another good point is possibility of labeling those nodes with chance to put one or more labels on every single node itself. One of several applications which can help us with this is Neo4j. I think it’s not a really fresh idea of visualizing source code but really great one in case of checking architecture of product and finding bottlenecks in object dependencies.
Next was “Jak Wciągnąć Eksperta Domenowego W Wir Modelowania – Wizualne I Lingwistyczne Techniki Ddd” from Sławomir Sobótka – that talk was pretty much about splitting domain experience and user experience. So in general we usually have just one expert from client side both for user and business cases, but the most profit we can get if split those two responsibilities between real life experienced people instead of one and involve them both into process.
Another soft skills topic was “Conversation Patterns For Software Professionals” from Michał Bartyzel. Here we met the right idea of using patterns in our day-to-day conversations with business. If I’d try to summarize this we’ll get next scheme:
- Need (usually business need).
- Why do we discover needs?
- I want to avoid (usually troubles from client side), which constructions are used by clients:
– I’m afraid that…
– I don’t won’t…
– I’m not sure…
- I want to achieve (clients goal) are expressed after:
– … we could design,
– I’ll use,
– We’ll test,
- Patterns for conversation: benefit / role / goal or problem/ role /goal
At the end of first Conference day we all had a chance to attend integration bowling party in nice place just in the center of Krakow.
Second day was pretty intensive so I visited all 8 presentations in the row.
– Co Twój kod mówi do Ciebie (What does Your code tell You) – by Mariusz Sieraczkiewicz,
– Introducing Groovy into Java project – by Yuriy Chulovskyy,
– High Performance Logging – by Peter Lawrey,
– Working with logs – by Krzysztof Otrębski,
– Docker.io – Versioned Linux Containers for JVM Devops – by Dominik Dorn,
– Continuous delivery: capitalizing high quality automated tests – by Szczepan Faber,
– Agile Transformation – How to Change Minds, Deliver Amazing Results and
Enjoy The Journey! – by Obaidur Rashid,
– Multitenant Search – by Pablo Barros,
In short most influenced as for me were almost all of them let me underline several most interesting ideas.
From “Co Twój kod mówi do Ciebie (What does Your code tell You)” topic I’ve got some obvious but at the same time important ideas about refactoring and keeping our code as clean as possible without digging too deep.
“Introducing Groovy into Java project” – was such kind of presentations after which You definitely want to try that by yourself – I’ve tried and let me insist – power asserts in Groovy that’s really something.
“Docker.io” – really interesting concept of organizing integrations and delivering processes within every simple project. I’m sure this tool or rather set of tools (if I can say in that way) has a great potential future value.
During “Continuous delivery: capitalizing high quality automated tests”I had feeling like Alice in Wonderland – from one side everything is pretty common (I believe almost everyone in IT at least heard about Mockito framework) and from the opposite side it was like a little miracle.
Don’t believe me – but time between latest changes committed into framework and when You can actually can get the latest version – about 10 minutes. That’s what I really can name Continuous delivery. All process based on free recourses: GIT, TRAVIS (as CI server), BINTRAY (as JAR repository) and GRADLE (as a build tool).
“How to Change Minds, Deliver Amazing Results and Enjoy The Journey!” once more time underlines problems which are still exist while implementing Agile in teams. Even we know a lot about, someone tried, another guys were on training but when we’re face real life things become more complicated.
General expression from those two days is really positive and impressive. Organization also was held on a really high level. And I’d like to finish my part of story with the quote:
“A single conversation across the table with a wise man is worth a month’s study of books.” – Chinese Proverb
Thanks for reading! If you have a friends who are a Java fan and couldn’t be at JDD, I really encourage you to share this with them!