3 ms·

This attitude works only if your team is not toxic and others in your team are not taking credit for the work. In my company, if I try to do a lot of work it w

by msoad 5y ago

This attitude works only if your team is not toxic and others in your team are not taking credit for the work. In my company, if I try to do a lot of work it will backfire. I will out that my work is being celebrated by some no-talent PM and promoted by my sneaky manager without my knowledge. They then bring in all the "high priority" issues from "the top" to me to fix. I learned that those people don't understand how software is built so I'm just coasting and doing the absolute minimum. Less credit stealing and less high priority feature requests from the top. I still get Exceeded Expectations rating every year. Because I pretend my work is so difficult and takes so much time...

mixmastamyk 5y ago
Put “Project X by msoad” in the header. ;-)
stjohnswarts 5y ago
The only meetings I usually call are to discuss cool things I've added to the code base and I make damn sure management is in on the invite. Leave a paper trail, never be shy about letting people know what you've done.
lr4444lr 5y ago
I get it. There are definitely bad companies to work for. But there's a difference between working at a company where things are fundamentally just for value producers even though there are some bad actors who can't be removed, and a company that is ultimately spiraling downward because there's no capable leadership at the top to keep people focused on what really matters to the business. I'm not saying to subject yourself to torture: just recognize every day how you can actually deliver value for other people and the bottom line, and do it. Even if you're not getting credit, suggest to a higher up that you might not be able to do X effectively anymore because Z is in your way, and see how fast things change. It is a big difference if "X" is "deliver the feature we promised the 500K client" or "get the nightly report automated on time" than if it's "rebalance the cluster" or "streamline the CI pipeline".

by msoad 5y ago

mixmastamyk 5y ago

Put “Project X by msoad” in the header. ;-)

stjohnswarts 5y ago

The only meetings I usually call are to discuss cool things I've added to the code base and I make damn sure management is in on the invite. Leave a paper trail, never be shy about letting people know what you've done.

lr4444lr 5y ago

I get it. There are definitely bad companies to work for. But there's a difference between working at a company where things are fundamentally just for value producers even though there are some bad actors who can't be removed, and a company that is ultimately spiraling downward because there's no capable leadership at the top to keep people focused on what really matters to the business. I'm not saying to subject yourself to torture: just recognize every day how you can actually deliver value for other people and the bottom line, and do it. Even if you're not getting credit, suggest to a higher up that you might not be able to do X effectively anymore because Z is in your way, and see how fast things change. It is a big difference if "X" is "deliver the feature we promised the 500K client" or "get the nightly report automated on time" than if it's "rebalance the cluster" or "streamline the CI pipeline".