Richard Bach once said “A professional writer is an amateur who didn’t quit”

In that phrase I think the word “writer” can be easily substituted with “programmer”.

In one view nobody has born trained to be a programmer or a software developer.

You must focus, practice and never stop learning. If you really want to be a programmer, you can’t quit.

You can be a professional in any area. There’s professional video players, poker players etc. However, this clearly does not mean the same thing.

Of course, there is a sense of “professional”, which is quite straightforward and under which this definition is tautological – to make a living out of what you are doing.

In one book there’s a section on “Hiring an agile professional” where Bob Martin, is known for speaking about the need for “professionalism” in software development.

(An interesting contrast: The Institute for Project Management has “professional” designations for project managers, but only provides the title of “practitioner” to holders of Agile certificates).

Professionals do not have bosses. Professionals are business partners. They can be hired, but they are not workers run by masters. Instead, they are experts who know how to best achieve what their employers need. You hire doctors and lawyers, but you don’t control them, right?

So, what does it mean to be a professional programmer? What does it mean to be a professional? Some definitions simply say that being a professional is “making money with skill”, but real professionals also have a set of qualities that are often described as “professionalism”.  – Sarah George.

I had a feeling that this analysis is crucial. Whatever the status of their “professional” requirements is, a flexible movement in practice leads to a redefinition of these professional groups. Specialties that did not exist several years ago are now in great demand among large and small companies: the master of the struggle, the owner of the product, Agile Coach, DevOps Engineer, etc.

A simple understanding of these changes requires a conceptual framework that has not yet been appropriated by software professionals and would make this study worthwhile.

This is not quite a glamorous profession, developing software.

The agile community can be described as a collection of “tribes”, I unequivocally recognized aspects of power / monopoly;

who is and who isn’t a member of the community?

This is widely underestimated among agile tribes, who occupy an “open” position; This isn’t without problems and contradictions. Many years of debate, mainly about “who has the opportunity to decide whether someone will move or not.”.

I can affirm that we can’t influence where agile goes. if it disappears (as some predict it will) or change the world (as others claim) or maybe it turns into a productive field of research of software. If we can’t understand how it evolved to where it is now we can’t predict what It’s going to happen later.

To finish this article, I chose a phrase of our manifesto.

“As developers, as team leaders, as product owners, we refuse to let our work responsibilities be dictated by what we see as outdated thinking”. We are “uncovering better ways of developing software”-  Manifesto