Professionalism is for Amateurs
thenextweb.com
thenextweb.com
Professionalism, to me, implies a certain standard of conduct: Delivering what you promise, when you promise it. Communicating clearly. Refusing unethical requests. Not flaking out at a critical moment. Keeping your cool even when you're a bit frustrated. Refraining from conduct that will discredit your employer, clients or partners. Being clear about your degree of expertise on a given topic.
Now, this sort of professionalism isn't the only virtue in life: You also need to care passionately about what you do, speak plainly and honestly, and enjoy building stuff. Professionalism is never enough. But the opposite of "professional" isn't "amateur," it's "unprofessional." And I, for one, do not enjoy working with unprofessional colleagues or clients.
The amateur does the job when and how he sees fit. The professional does the job when and how the client requires.
Passion may exist in either. What one does when there is not passion makes the difference.
That definition is this: "Professionalism" is the recognized respect that should be given to those individuals, processes and companies labeled as such due to their earned credentials in a particular field.
It's a definition created specifically with the intent of preventing the questioning of the status quo; an overdeveloped argument to authority, basically.
Here's a thought - how about someone who's a passionate professional?
- Wearing a suit, shirt and tie
- Writing lots of documents that nobody reads
- Having source control, automated build process and unit tests
- Always saying yes to a customer
I also know quite a few "real" professionals (doctors, lawyers, professionally qualified engineers) - using those standards I'm quite happy to state that I'm not a professional if anyone asks.
[Edit: Obviously I do think one of those points above is important!]
I think that the whole article is the definition, if not explicit than at least inferred from the examples. Not that I think that the only proper definition of 'professional' is: boring, limited, uninspiring (the author seems to suggest that).
On the contrary - there are some things that discern professional software development from unorganized mess and I'd rather have them in place: source control, automatic and repeatable build and deployment, regression tests etc.
So do tradesmen.
You can act and behave like a pro and maintain the personality that the author's looking for. Being professional doesn't mean you're only subscribe to the conventional thought processes big business types may subscribe to.
professional standards: the skill, competence, or character expected of a member of a highly trained profession
use of professionals: the use of professionals instead of amateurs
Maybe you mean "beaureaucrats", or some other word; but not "professionals"
Original thinking is a bit trickier to understand. Both examples in the post use companies with vested interests in supporting their existing business models. Having a vested interest tends to "color" views towards ideas that disrupt the model. Of course, this provides opportunity for someone with at least a moderate skill level and a lot of ambition to branch a market.
> Curious to know what his definition of software engineering professionalism was after four years of MIT education, we probed a bit deeper and established that the way that he thought about professionalism did not differ from the thinking of a Mary Kay cosmetics saleswoman: wear nice clothes, drive a clean car, and don't say anything that might offend anyone.
Philip may be hard to work with, but he's a great writer.
Amateur: comes from a French word meaning: "lover of".
Etymology's very deceptive. It's generally not a good idea to use it to discover the "true" meaning of a word, whatever quality that "true" meaning would have over the common acceptation.