4 ms·
> Where does the idea come that you're only "working" when you're coding? When performance review time rolls around, it can be very hard to get credit for all
by kd5bjo 6y ago
> Where does the idea come that you're only "working" when you're coding?
When performance review time rolls around, it can be very hard to get credit for all of those other things. Coding, on the other hand, has products with direct business value that you can point to and say, "That's what I did this quarter."
- bgirard 6y agoYou have to look into where that overhead falls: 1) Things that everyone has to do like HR/Legal compliance. 2) Things that you should have opted to avoid like useless status meetings. 3) Things that are productive but have in-direct business value. That's largely a bug in the review process if it doesn't value those.
- ironmagma 6y agoOne huge waste of time is red tape. Corporations love adopting procedures that are directly antithetical to getting work done in a timely manner, like “IT support” tickets that consist of getting access to an internal database, even if that database contains no sensitive information. These do not affect teams in an even way, since some projects’ critical paths will depend on these labyrinthine workflows more than others.
- ozim 6y agoSo let's go with typical reply: if you work in such place that does not understand that and don't want to pay for it, you should pimp up your resume and find better place.