JDD, Warsjawa, Agile Prague and Cambridge Agile Conferences

Table of Contents

Vacation time is over, and it’s time to get back to hard work :)

I have the privilege to speak at three conferences, so if you would like to meet me and talk, don’t hesitate—join the conferences as soon as possible.

Agile Prague Conference

My first talk will be about refactoring and the concept of Natural Course of Refactoring in Prague on 16th September. There is a big chance that I will show more advanced examples with many tricky and non-trivial transformations. More details about the event can be found at Agile Prague 2014 Sessions.

Agile Cambridge Conference

The second activity will be a workshop on Soft Skills for Tech guys in Cambridge on 2nd October. If you want to learn how to use a very useful model to handle conflicts, just come. More details about the event can be found at Agile Cambridge 2014 Programme.

JDD Conference in Cracow

In addition to that, I will be talking at a great Polish conference in Cracow called JDD, which I have been with for ages (from the beginning). The talks will be held in Polish. The first one will be “How your code speaks to you” and the second one, with Michał Bartyzel, about “Strategic Refactoring”. More details about the event can be found at JDD 2014.

Warsjawa Workshop

Ohh… I forgot. Warsjawa! Yes, there will be a great opportunity to put hands on the keyboard and repair legacy code during the “Working with Legacy Code” workshop. More details about the event can be found here at Warsjawa.

Ouch! Now I realize that it will be a very busy time :)

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)

Tags

Related Posts

Why Agile Fails

Introduction

Implementing a methodology from the Agile family is not at all easy. The problem usually lies in management, who upon superficially understanding what it’s all about, perceive the new method as a promise that from now on, everything will magically work better. It doesn’t matter if we have subpar team members and adhere to the principle that “any specialist can be replaced by a finite number of students.” It doesn’t matter if there’s complete disregard for knowledge management and skill development in the team because there’s never time for that. It doesn’t matter if people working on projects are shuffled between projects—after all, it’s about interdisciplinarity, and everyone should know everything.

Read More

Technical Leader Worries: Team Members Are Whining

Understanding Team Complaints

It’s very annoying when you hear whining from your team. They complain about boring work, stupid company security policy, wrong management decisions, customers not knowing what they want and changing their minds, and project managers crowding them. Doesn’t it sound familiar?

Read More

Natural Order of Refactoring Explored Part 2: Compose Method

Compose Method

Analyzing methods, such as the one presented in Part 1, often leads us to understand the main points of the algorithm contained in them. This insight paves the way for the next step: try to split a large method into smaller steps by extracting them into separate methods (refactoring using the Extract Method). Thus, the original method will consist of a sequence of calls to these new methods. With the right naming conventions, you can achieve code that reads like a book.

Read More