Quality Excites 2017 from my perspective. A few words about selected talks, overall conference organization and also a little bit about my talk- Evolving Architecture from quality perspective. As far as I know my talk was rated by conference attendees as the best talk of Quality Excites 2017 with rating 4.90! Thank You all!
Last weekend I have attended Confitura 2017 conference. This year not only as a participant, but also as a speaker with my “Evolving Architecture” talk! I must admit it was my dream to speak at this event someday. I don’t have enough words to explain this feeling 🙂 I always thought about Confitura as one of the biggest and the greatest Java events in Poland. Being a part of this was truly awesome! Here you can see my thoughts on presentations that I attended to.
What DevOps usually are responsible for? Why such a role starts to be more and more important during last time period? This speak is an approach to answer these questions. Its a talk for you if you want to find out if becoming a DevOps is right for you. You will also find out what technologies are used on daily basis and how to start career as a DevOps in world of complex systems and fast, secure deployments.
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.
Have you ever considered how your current project architecture will evolve in the future? Have you ever thought how your team will develop certain features for a client? How about possible over-engineering?
In general, we always try to predict all possibilities and changes that the client may require. In the other hand under time pressure developers are being pushed to do different kind of “shortcuts”, which can increase cost of developing new features. How to avoid over-design, but without closing your architecture for all sort of changes that your customer will need in future? When certain technical decisions should be made? When technical debt should be accepted, and when is a need to avoid it?
It will be a story about bad decisions and failures, but also about those decisions that can save the day.
Usually I don’t have time 🙂 Last year almost every month I tried to attend Agile Silesia meetings. But every month something happened and I just postponed my “first time”. So I decided to change my strategy. I sent an email if they want me to give them a talk… Read more »
Second time I was able to talk about distributed teams in agile oriented companies (First time I have this talk on InfoMeet event in Kraków). This particular talk is mostly my personal story of mistakes and problems that I had to face on my daily basis at work. IT Career… Read more »
Slides (in Polish) from my presentation about introducing Continuous Delivery in old legacy projects. I was very proud to give this talk three times so far: Infomeet Kraków 2014, Infomeet Wrocław 2014, CareerCon Kraków 2015 This talk was mostly about basic steps that can be very easily missed if you… Read more »
Video (unfortunately recorded by smartphone) and Slides from my talk about efficient maintaining your own IDE and personal developer toolbox. Video and slides are in Polish. This talk was prepared for IT HappyHours event (Wroclaw University of Technology) – 2.06.2014.