The Google incentive mismatch: Problems with promotion-oriented cultures

Re:The Google incentive mismatch: Problems with promotion-or... by Firmwarrior on Wednesday May 04, 2022 @07:11PM (#31267064)

Well, you have to maintain things after they're made. New things are usually made out of multiple old things. Figuring out how stuff works, then fixing and reusing, supporting, or replacing it is the bulk of every programming job I've done or heard of.

I can't even conceive of what programming job wouldn't be describable as "grunt work" from the point of view of some hypothetical super-genius. Writing "new" code that just does the same thing as something you're tossing out, but with a different set of mistakes? Cutting-edge science work is mostly glue code between hardware and spreadsheets or databases. Cell phone firmware is mostly repurposing and updating the old firmware. Anything involving a GUI is going to be a massive time-sink getting the GUI to work the way the non-technical people using it want it to work.

How much time do you spend in any given year figuring out how to operate debuggers, find the right log files, narrow down some crash, etc?

[ Parent | on HN ]

Re:The Google incentive mismatch: Problems with promotion-or... by edmundsauto on Thursday May 05, 2022 @01:45AM (#31269965)

As you said, those are required components of shipping software. I don’t consider them grunt work, any more than I would consider being a janitor as a grunt.

Grunt implies a heirarchy and a job that anyone can do. It’s pejorative. There is work that I don’t enjoy doing but needs to be done well (cleaning a toilet). I appreciate those jobs even more than what I do!

My point is that you should try to shift to language of “work I don’t enjoy” rather than “work that is beneath such an exalted 10x programmer such as myself”. Because that’s how I interpreted your original comment.

[ Parent | on HN ]