Thomas Sundberg


Thomas Sundberg is a consultant based in Stockholm, Sweden. He has a Masters degree in Computer Science from the Royal Institute of Technology, KTH, in Stockholm. Thomas has been working as a developer for more than 20 years. He has taught programming at The Royal Institute of Technology, KTH, one the leading technical universities in Sweden. Thomas has developed an obsession for technical excellence. This translates to Software Craftsmanship, Clean Code, Testing and Automation.

Thomas is also a speaker at different conferences and developer venues, including eXtreme Programming XP, Agila Sverige, Öredev, Turku Agile Day, Agile Central Europe, GeeCON, Java Developer Day, Agile By Example, Scandinavian Developer Conference and Agile Testing Days.

Thomas runs a blog where he writes about programming, Software craftsmanship and whatever problem he wants to share a solution about. It can be found at

Presentation I:

(Remote) Pair programming

Language: EN

Programming is often something that is done in solitude. Problem solving is something that often is done in a group. Programming is always about problem solving. It would therefore be natural to do programming in groups. The group must not be too large and there must be at least two persons to make up a reasonable group. A pair turns out as the natural choice.

Some of the benefits with pair programming are

  • Problem solving
  • Continuous reviews
  • Quality
  • Learning
  • Lower project risks
  • Satisfaction

There is also a myth that pair programming is twice as expensive as having one person solve each problem. I will show why this is just a myth and that the actual direct cost has been shown to be 15% higher. I will also follow up and show why the total cost during a computer programs life cycle gets significantly lower with pair programming.

Pair programming is most efficient when the pair sits next to each other. This is not always possible. I will therefore perform a pair programming session with a remote partner to illustrate that it is possible to do pair programming remote.

Presentation II:

How to fail a software project fast and efficiently?

Language: EN

Software development is an industry that has been around for a little bit more than 50 years. There are a lot of really smart people working in this industry. How is it possible that these smart people are so good at failing? How can we as an industry continue year after year with failing or really slow development?

The answer is embarrassingly easy, we tend to apply methods and techniques we don’t understand or that don’t bring any value.

There are many anti patterns that can be applied to software projects.

They tend to fall into these categories:

  • Architectural
  • Development
  • User interface
  • Organisational
  • Management

We will look at a selection of these anti patterns and see why they are so bad and the problems they contribute with.

Just looking at bad examples may be depressing. But if you can identify a bad example in your own project or product then you have a chance to do something about it. Understanding and accepting that you have a problem is always the first step to fix it.

  • jdd


Złoci sponsorzy

Srebrni sponsorzy

  • EPAM
    • j-labs
      • UBS
        • Sii
        • Sponsorzy

          Sponsor Afterparty

          Sponsor Internetu i Gamezone

          • EPAM
          • Patroni medialni

            • Teetbee
            • helion
            • Polish JUG
            • Poznan JUG
            • SDJ
            • pcfoster
            • pcfoster
            • pcfoster