3 ms·
One thing that has always struck me about compensation is that it is incredibly infrequent where I can actually implement the type of fundamental changes a comp
by salawat 7y ago
One thing that has always struck me about compensation is that it is incredibly infrequent where I can actually implement the type of fundamental changes a company most needs due to most opportunities for major throughput gains being hidden in the mires of interdepartmental communication breakdown.
I've actually gotten grudgingly bored of technical implementation/testing as at this point, I can look at a set of specifications, and generally have the code that underlies it it be almost immediately apparent. Migrations are a bit more interesting, however, at the end of the day, I get the most out of untangling or unobstructing human communication pipelines.
The work is irregular, generally novel, completely underappreciated, and nigh impossible to get anyone to agree to let you do regardless of the throughput increase you can enable. Especially if politics/an imagined threat to someone's budget becomes a sticking point somewhere in the chain.
So often times a job degenerates to the work an office will allow you to do.
It is one of the things I miss about startup culture sometimes. It's amazing how much a couple of people can get done with a process based on the right abstractions and a tailored vernacular/set of efficient protocols.
- UncleMeat 7y ago> One thing that has always struck me about compensation is that it is incredibly infrequent where I can actually implement the type of fundamental changes a company most needs due to most opportunities for major throughput gains being hidden in the mires of interdepartmental communication breakdown. Then solve those problems. At higher levels, solving organizational problems is a job expectation for engineers. "Process is preventing me from having impact" is not an excuse.