3 ms·
The problem with this approach is that it's a risk. The risk is that he ends up doing it, the company reaps all the value while feeding him scraps, but now the
by noprocrasted 2y ago
The problem with this approach is that it's a risk. The risk is that he ends up doing it, the company reaps all the value while feeding him scraps, but now the bar has been raised and the company forever expects this increased productivity from him (or just takes the improved tooling he wrote and lays him off completely).
He's in a position that by the sounds of it he has the skills to automate away - he should take this opportunity to free up his own time so he can pursue other opportunities (whether a job search, studying or freelancing) while still collecting the paycheck.
- al_borland 2y agoThere is no risk here. He'd be taking a boring jobs he doesn't like and shifting it, in part, to one he likes better. As a side effect, his manager can see he has the skills required to actually do the job he wants, as he wouldn't be plucked to be a developer just because he shuffled the most logs around. If he does decide to leave after some time, instead of his resume saying he shuffled log files around, it can say he developed tools, improved processes, etc, which would likely lead to better job offers. Doing things that help the business are more interesting than random side projects done in a bubble and used by no one. He's getting paid the same either way, he might as well do some work that moves him in the direction he wants to go, and he finds interesting, rather than only doing the work that he knows will keep him in the same place.