Events Search and Views Navigation
February 2017
Evolving Architecture @ IPIJ Meetup
During development phase its very easy to cross the design boundary – we want to take care about all possibilities and potential changes that can happen in our project. On the other hand when we are under the time pressure we take shortcuts which could in the end increase cost of even simple changes. How to deal with “overdesign”? How (at the same time) don’t close for improvements and changes? When we should make crucial technical decisions and when accept technical debt? This session is about true stories, mostly about huge mistakes, but also sometimes about decisions which in the end were very successful. The session for all who don’t want to end up with project that need’s to be rewritten to add a new button. The session for all who cares.
Find out more »May 2017
Do not make these mistakes! @ Chillout meetup #6
Chillout Meetup #6 Agenda Paweł Młynarczyk, "The Programmer's Diary - there and back again", Daniel Pokusa, "Java: Do not make these mistakes!" Both talks have one shared concept - journey. We will try to share our knowledge on different abstraction level. Paweł wants to share his journey as a professional developer and explain how evolve, how learn continuously. In the other hand I want to share my observations from last 4 years of teaching young colleagues how to "write in java". I…
Find out more »June 2017
Evolving Architecture @ Bielsko Biała JUG
Evolving Architecture, 18:00 - 19:00, ATH, Block L, Room 120 When developing a system, it is very easy to cross a certain boundary - on the one hand we want to predict all possibilities and changes that can happen in our project. On the other hand, when we are under the time pressure, we take shortcuts which could in the end increase cost of the smallest changes. How to deal with "overdesign"? How, at the same time, not to close…
Find out more »July 2017
Orchestrate Your Choreography! @ Silesia JUG
When we speak about orchestration we should think of conductor in philharmonic orchestra. Basically His role is to show rhythm to all musicians. In the other hand "Swan Lake" don't need conductor for dancers. They know when its their part, and which steps they need to do. Its all because of choreography. You can find a lot of examples which use this two fundamental ways of keeping processes in correct order. You can find them in Event Driven Architecture, Microservices,…
Find out more »