This is a really interesting post. Before I was a software developer, I worked as a licensed civil engineer. When I think about what is "professional", my former work informs my thoughts.
Certain types of work involve public trust and accountability. As a Civil Engineer, if I was acting "professionally" I was contributing to that trust. If I was acting "unprofessionally" I was deteriorating that trust. Ideally this would mean--if I tell the truth and deliver a safe design that is professional, if I lie to the client, take bribes, deliver a sloppy design that is unprofessional.
But people use shortcuts to make judgements, so the evaluation often comes down to "do you conform to my idea of an engineer?" This others people unnecessarily and is counterproductive.
So when I think "professional" now, I ask myself if the person is acting like their work matters, if they would be proud to put their name on their work, and if what they are doing is ethically sound. But you are right, that is not necessarily what others will hear if I use that word.
I really like using the lens of being reliable and trustworthy. I think you're right that this is what is really at the core of the idea of being "professional".
A friend told me, "if you charge for what you do, you are a professional".
That was going to be my definition. Literally, if you get paid to do something, that makes you "professional".
For me, professionalism has a very simple definition. It means to not get caught up in the turmoil of the current situation (server on fire, customer yelling at me, being passed over for promotion, etc.), but instead to stay focused doing the job.
In the above examples with the server on fire, it would be unprofessional for me to say nothing/go home, leaving someone else to deal with it. The professional thing to do would be to hit the fire alarm and follow fire safety procedures. If a customer was yelling at me, the obvious unprofessional response is to yell back, to join in the tantrum. A professional might ignore the yelling and focus on solving their problem. Or if not possible, politely tell them to call back later. In being passed over, the unprofessional might retaliate in various ways. But the professional keeps doing their job well. (It is not unprofessional to discretely look for another job if this is a pattern. It is professional to give adequate notice rather than walk out.)
Professionalism does not mean to sacrifice all other aspects of life for your job, or to suppress all your emotions, or that you can't have friends at work, or that you should treat your co-workers coldly. It simply means that for the time you are at work the priority should be performing the profession. In our business, that can often mean a lot of collaboration and learning unfamiliar perspectives to solve a problem. Professionalism is not about me.
Now professionalism as I have defined here is not easy. I have missed the mark many times, especially when I first entered the work force. It takes practice.
This process can take 5-10 years or so.
Sorry for mistakes, if any.
A professional does the right thing for the world and then waits to get fired: brendansterne.com/2013/07/11/do-th....
I really liked that. Thanks!
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.