4 ms·

> I normally work about one day trickle out my changes during the the week. The other days I only open my computer for standup and if I get an IM. There is a t

by jlj 6y ago

> I normally work about one day trickle out my changes during the the week. The other days I only open my computer for standup and if I get an IM. There is a term for this called "sandbagging." > I don't feel what I'm doing is ethnically wrong, because the company is evidently pleased with my current productivity, but I find it unsatisfying and like a waste of my time on earth. Sounds like you have a motivation and procrastination problem. Pleasing someone or some organization != ethics. > The dev tools, docs and tech debt impart such a slow iteration speed Help streamline how the dev tools are used. Tools alone don't solve for much, they need a solid and frictionless process to follow. Document that process to help yourself and your team. Find some common threads or repetitive issues in the tech debt and fix it without waiting for someone to ask you to fix it. Those kids of work may even help get you promoted and open up more interesting projects.

gajjanag 6y ago
> Those kids of work may even help get you promoted and open up more interesting projects. Do you have any anecdotes in support of this view? My general understanding is that working on such things (if it isn't part of your explicit job description) is usually met by at best gratitude from other people, but certainly not promotions. And there are definite risks: since it is time spent not on your "actual" job, it can show up in performance cycles especially with a mediocre manager.
- wtracy 6y ago
  This seems to be a common and expected way of getting promoted within Google: Their performance review system allows engineers to provide feedback on people from unrelated teams. I don't know if any other company where this strategy is likely to get you ahead.
- jlj 6y ago
  OP said he's working at 20% capacity for one because the tools and documentation are bad. If fixing those problems increases the team productivity by some non-trivial amount it's a positive data point for a promotion. At my current co, promotions and job levels are measured by increasing impact at an individual level, within a team, across teams, across orgs, etc. Cutting waste is everyone's job.

by jlj 6y ago

gajjanag 6y ago

> Those kids of work may even help get you promoted and open up more interesting projects. Do you have any anecdotes in support of this view? My general understanding is that working on such things (if it isn't part of your explicit job description) is usually met by at best gratitude from other people, but certainly not promotions. And there are definite risks: since it is time spent not on your "actual" job, it can show up in performance cycles especially with a mediocre manager.

wtracy 6y ago
This seems to be a common and expected way of getting promoted within Google: Their performance review system allows engineers to provide feedback on people from unrelated teams. I don't know if any other company where this strategy is likely to get you ahead.
jlj 6y ago
OP said he's working at 20% capacity for one because the tools and documentation are bad. If fixing those problems increases the team productivity by some non-trivial amount it's a positive data point for a promotion. At my current co, promotions and job levels are measured by increasing impact at an individual level, within a team, across teams, across orgs, etc. Cutting waste is everyone's job.