Agile Zone is brought to you in partnership with:

Michael Norton (doc) is Director of Engineering for Groupon in Chicago, IL. Michael's experience covers a wide range of development topics. Michael declares expertise in no single language or methodology and is immediately suspicious of anyone who declares such expertise. Michael is a DZone MVB and is not an employee of DZone and has posted 41 posts at DZone. You can read more from them at their website. View Full User Profile

Being a Boss

04.23.2013
| 3603 views |
  • submit to reddit

In some manner or another, I've served in roles frequently referred to as "boss" for over 20 years. In a few cases, I owned the company, in whole or in part. In many more instances, I held some rank that granted me authority over the work-lives of others. I've learned a great deal over the years. And I am definitely still learning.

If you'll indulge me, I'd like to share what little I have learned about being a boss.

The first lesson - Don't be a boss.

Be a mentor, a guide, a confidant, a facilitator, a shield, and a coach. But don't be a boss.

Nobody likes a boss.

boss 1 (bôs, bs)
n.
One who makes decisions or exercises authority.

v.tr.
To give orders to, especially in an arrogant or domineering manner.

v.intr.
To be or act as a supervisor or controlling element.
boss 2 (bôs, bs)
n.
A cow.

On second thought, some people do like cows.
Published at DZone with permission of Michael Norton, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)