So I made an FB post on my wall a few weeks ago:

Years back as a mid-level dev in an undisclosed company, certain support personnel would constantly email our bosses about how they spent X number of hours overtime resolving certain client issues. They'll email that every single day without fail.

Meanwhile their support issues are handed down to us devs, who would look for root causes and offer resolutions and or bug fixes. This is on top of our usual development work, and the additional workload impacts that work and causes delays, because the support tickets are always "priority".

Come evaluation time the support team gets lauded for their efforts, but the dev team gets berated for the "slow progress" of their output. To be honest I'd love to do the same thing that the support people did, but we've got no time to email; neither do I like kissing ass.

Big mistake.

Lesson learned: trumpet your work. People seem to like the perception of working more than actual effort. ;)

Hint: I was being sarcastic ;)

If your workplace needs their work to be trumpeted for people's recognition to be visible, it's not a good sign, at all. Managers should be able to recognize contribution whether or not their subordinates speak at all.

Introversion should not be a liability.

In IT all work monitoring has been moving towards automation: tasks and issues are encoded on ticketing systems, coding can be seen and monitored using version control, work done can be verified using automated testing tools. Eventually such tools would very likely be available for non-IT jobs at well.

However if you are in an IT workplace where noise indicates effort, you are definitely being short-changed.

Jon Limjap

Microsoft MVP for Visual Studio and Development Technologies |Technical Advisor at PageUp | Philippine .NET User Group Lead | Photographer | Scale Modeler

Manila, Philippines