The Professional Developer

The Professional Developer

Last week I called a technician to repair an electrical shutter that was broken. The technician did a good job in general, but there was one particular thing he did that made me think of him as a true professional. Was it the tools he was using? No. Was it the technique? He was working fast, but no, it wasn’t that. It was the moment he asked me for a broom to clean up after him. That was when I realized he was a pro.

In a similar manner, what makes a software developer a pro? Is it the extensive knowledge of program languages or frameworks? Is it the speed of work? Is it the elegance of design? No.

Developers are pros first, when someone uses the software they wrote. To do that they need to talk with customers, get feedback and make sure the are delivering the right thing.

Developers are pros when their design is easy for other people to understand and use it.

Developers are pros when they know how to collaborate with other people, when they can put their ego aside in order to do a better job.

Developers are pros when they always develop good quality code. When they know not to succumb to pressure to do something messy.

Developers are pros when they thoroughly test what they do. When defects are a rarity, something utterly astonishing and perplexing.

Developers are pros when they never leave messy code behind. They clean up. And if that’s what it takes to clean up, they use a broom.


To view or add a comment, sign in

More articles by Yaki Koren

  • How to change mindset - the Jahnun lesson

    As a coach helping organizations become agile, I'm asked how to change the mindset of the people, how to help them see…

    1 Comment
  • How to Achieve Valuable Retrospectives

    “Oh no, it’s retrospective time!” This cry for help is not uncommon, I’m afraid, among practitioners of scrum. That is…

  • The horrible truth about software development estimation, and what to do about it

    The Horrible Truth In recent years I've been working with many software development teams and almost all of them…

  • A Beautiful Day For Unit Tests

    Writing unit tests on Legacy Code is an adventure. Today I spent several hours doing that with two developers, Mark and…

  • 5 steps to get unit tests going

    Once you start unit testing, you will find significant benefits to your design, throughput, quality and peace of mind…

    3 Comments
  • Setting Goals For Improvement - Leading vs. Lagging

    Many organizations are becoming agile to improve quality, throughput or many other good things that agile brings along.…

  • 3 steps towards better team work

    Working with teams I sometimes feel that teamwork is similar to the weather: everybody talks about it but not much is…

  • Legacy Code: Extract-FirstUT-Cover-Refactor-TDD

    Recently, I had the opportunity to work on legacy code with several teams from various organizations. I would like to…

  • Amusement Park Methods

    Sometimes you stumble upon amusement park methods. Remember the feeling when first going through the gates of a big…

  • Team Storming and Compost

    A team I am working with is in the storming stage of their development. Finally.

Explore content categories