35
A 20-year-experienced CTO’s Advice “Don’t Be a Humble Developer”
(javascript.plainenglish.io)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
In my personal experience I have gotten much more praise from Big Corp company when the work I did was more visible to management. The best work I've ever done was completely ignored because it was more technical and difficult for management to understand what the work was about.
And it wasn't just about explaining the work, it just wasn't that interesting to people who aren't technical.
It was after getting an award for doing some extremely easy work, that I realized that it's much more important that you communicate what you do, than actually doing useful work. And this sucks real bad, because if you do good work, it means you have to spend a bunch of time outside of that work just explaining it and acting like it's a big deal, and you can easily beat the system by overrepresenting easy work, because you have a lot more time to explain what you did.
Just my experience with my Big Corp, it may not be quite like that everywhere.
We had a saying at one of my former employers, "You don't get a medal for preventing a fire". We worked so hard to prevent problems before they happened, but a lot of managers just thought of us as a pain in the neck. The only time anyone got wider recognition was for fixing problems after they had some serious impact. A lot of the time those problems would have been easily preventable. It really seemed like the teams that were constantly having major issues in production were constantly being hailed as heroes by management.
If you do things right, people won't be sure you've done anything at all