Improving your Test Driven Development

Jakub Nabrdalik

Software developer

For the last 15 years I've worked in software houses and large enterprises creating dedicated applications for external and internal customers in languages like Groovy, Java, C#, PHP, and using plethora of technologies. I do everything from analysis, programming, modeling, architecture, coaching to managing projects. That’s what you usually call a developer these days. Some of the systems, I've worked on, include Mobile Banking, Finance, Telco, eCommerce, Data Management Systems, Content Management Systems and Enterprise Resource Planning.

I built an IT branch of a corporation in Poland, from the scratch, which I've grown to 50 people and managed for 2 years, hiring people, designing development and support processes, empowering self-organized teams, coordinating with development centers in other countries, driving big changes and setting up a proper hacker culture.

Now I'm a team leader at Allegro-tech, where I have a perfect blend of everyday hands-on coding, mentoring programmers, managing a team and driving development of a few products.

My main interests are in Domain Driven Design and Test/Behaviour Driven Development, which I’ve practiced since 2005, gave a lot of talks on conferences and workshops, and wrote some articles. I love Software Craftsmanship, the serious, responsible, scientific and pragmatic approach to development.

I gave more than 60 public talks and workshops on conferences, universities and user groups, both Polish and international, helped to organize a few from scratch, shape a few by being in program committees. I was one of the leaders of Warsaw Java User Group, Warsaw Groovy User Group, Warsaw Spring Labs.

I have a long history of driving changes in organizations from the inside. I’m not afraid of managing people and processes, building culture, mentoring. I gave several talks on Agile and Scrum, wrote some articles as well.

But my focus is on software development. I’m very direct, down to earth kind of guy.

I’ve been using TDD/BDD at work for the last 12 years, I also teach and mentor teams on this subject. I’ve found that misconceptions and errors in this field are shared, and that most of us make the same mistakes.
Give me 45 minutes of your time, and I’ll try to address the most common problems, hoping to improve your TDD/BDD situation as much as possible.
I’ll show you how to solve miscommunication and lost art of requirement gathering, by focusing on readability, introducing just enough of Domain Specific Language, and sorting out what is important and what isn’t with the power of Spock.
If you are not using TDD/BDD, this might also interest you - you’ll know how to start the right way.

1. 本場次為English