Managing Your Supervisor, Part Duex

Several months back I wrote about Managing
Your Supervisor
 and cited the fact that I miss writing code.  To their
credit, my team has not rallied to the call and provided me with an opportunity
to code in their projects (they know a bad idea when they hear
one)
.  However, I recently asked my supervisor to help me become
a better writer by editing my articles and suggesting new ways of writing for
this blog. 

One significant change in my life is our department’s reporting structure. 
I now report to a woman who’s career thus far has centered on journalism,
writing, and editing.  It is an interesting departure from a more traditional reporting
model wherein a software engineering team reports to a Chief Technical Officer
or similar techie.  Who better to guide my growth as a writer than the former
editor of a nationally respected newspaper?

Quick Aside

This structure has some positive effects, not the least of which is my own awareness
for the plights of my non-tech teammates.  Did you know, for instance, that
some marketing people actually have consciences?  Who knew? 

The Result

This previous
article
was the first writing sample that went through the capable hands
of my boss on its’ way to your screen.  The experience of receiving feedback
was fantastic and this is what I (embarrassingly) learned: The difference between
active and passive voice.

After this remedial lesson in the two voices, I want to go back and give my junior
high English teacher a smack.  This is obviously something that I should
have known my entire adult life.  I may as well tattoo on my forehead that I
am a product of a rural Texas public school.  To you, Mrs. Orr, my seventh grade
English teacher, I say, “Boo.”

Here is the good news, dear reader; I can now distinguish the difference between active
and passive voice, which is only a minor point when compared to the fact “managing
your boss” is not just a way to get by.  It can also be a way to improve yourself.

Proudly powered by WordPress | Theme: Code Blog by Crimson Themes.