6 ms·
First real job I had there was this guy who had one specialization. He was in charge of some software that drove tape drives. Every outside new manager would
by duxup 6y ago
First real job I had there was this guy who had one specialization. He was in charge of some software that drove tape drives.
Every outside new manager would come in and in some form or another look down on this guy in some form due to his age and generally not doing "a lot" of tasks and new products.
It took the local VP to come down and regularly high five him after his product git rave reviews from customers (regularly) and make the point every time some manager didn't get it.
That guy's code, documentation, everything was rock solid, and the number of support cases for everything he did was so low that the dude was without a doubt the most productive person as far as income goes. You could sell the product that he worked on and just rake in money with almost no costs after that. Almost everything else had a lot of support costs and etc.
Meanwhile the guys who were doing all the new stuff, sucked at trying to juggle 12 things because it looked good on a resume.
- riku_iki 6y agoThat guy could perfectly be some tech lead, establishing his rock solid approaches on team of junior 4-10 engineers and delivering rock solid new products.
- jdbernard 6y agoNot everyone has the disposition to teach and lead.
- sli 6y agoBefore we even get to disposition, some folks simply do not want to do those things.
- duxup 6y agoI didn't say it outright but I picked this guy as an example as ... hey ABSOLUTELY did not want to lead anyone / should not lead anyone. Very much the high performer type who SHOULD NOT 'progress' to management or supervisor or ... reviewer of any sort. He was professional, but "prickly". I found the keys to get along with him but a lot of folks didn't have the patience.
- riku_iki 6y agoIf he doesn't want, it is one story. Another story may be because he may not be promotable to such position because of mentioned "prickly" behavior, which may or may be not just engineering honesty and straightforward approach in contrast to bs(sugarcoating, ass kissing, exaggregating, sweeping dirt under carpet, etc) culture established in many companies.
- noir_lord 6y agoIt's similar to the systems administrator dilemma. Do your job well, it looks you are not doing very much, why are we paying you? Everything is on fire, it looks you are not doing your job properly, why are we paying you? I've worked with a few engineers over my career like the person you described and frankly they are worth their weight in gold, been able to bank on their output working reliably and consistently over time is hugely valuable, doubly so when what they do is the bedrock of many other things. Of course the unhurried, thoughtful person looks like they are slacking and the hurried, frantically working person looks like they are a hard worker. Fundamentally it's because impact is harder to measure than perception.
- Buttons840 6y ago> Do your job well, it looks you are not doing very much, why are we paying you? > Everything is on fire, it looks you are not doing your job properly, why are we paying you? Option 3: Everything is on fire, be really quick to respond to your manager and then poke and prod at things in production until it kinda works, repeat daily. This guys a hard worker! I'll have to keep him in mind for a promotion.
- high_5 6y agoAnd in the process burnout yourself. Quit the job or exit game of life.
- freedomben 6y ago> Fundamentally it's because impact is harder to measure than perception. Absolutely. Another nontrivial variable is the tendency for managers/team leads to get the "credit" for successful work, even if they aren't trying to. I've had managers before that did nothing but impede a high performing team. Luckily we delivered despite this. But it never failed, the manager would get accolades (often very public) for successfully releases, customer feedback, etc, and would end up promoted up. Meanwhile the team kept doing our thing, getting barely-matches-inflation annual increases and more and more micromanagement from the scrum diehards. Didn't take too long for the team to move on to better things. I have a dream of someday reuniting the super team for a sweet startup idea. Not likely to happen but I can dream :-)
- sli 6y ago> Meanwhile the guys who were doing all the new stuff, sucked at trying to juggle 12 things because it looked good on a resume. This isn't helped by the current trend of trying to hire mostly fullstack developers, also known as hiring one person to do the job of three people. It does almost nothing but incentivize packing resumes to hopefully make the cut and burn people out from switching modes.
- watwut 6y agoFullstack does not mean that you will burn out. Fullstack can mean 40 hours a week, never overtime. Also, for smaller apps, after you had at least few months of experience with all technologies, it is not difficult to switch modes. People who specialize will be better at their specialization, but you will be good enough for majority of apps.
- lolive 6y agoThe JavaScript fatigue is NOT a myth. [and CSS/layout is really tough, too]
- marcosdumay 6y agoAll of that applies to frontend development too. At the end of the day, some people like Javascrip and CSS. And "full stack" only means that they will work with those, SQL, and some backend language (that may be Javascript too). It doesn't imply anything on the workload, all it does imply is that the place is hiring a generalist instead of specialists.
- lolive 6y agoThe last job offer that made me smile was for an AI / fullstack developper. Aka the platypus of software dev. The problem is pretty simple. Let's say you are cutting-edge in all the technologies that make you very adaptable at time T. You get hired. You decide a stack A/B/C/... for your next project. You get stuck in that project for ... let's say 3 years. (a reasonable time for a project to reach production and have a few real-life iterations). If you are not an assh... who leaves after 2 years (leaving the production/maintenance to others, i.e never having lived the "hell" of maintaining things for real), then you are 3 years-behind in all the technologies that are not in the A/B/C/... stack. Now, at time T+3, you are ... the obsolete man [for TTZ fans only :)]
- aidenn0 6y agoThat VP is my hero. I've seen that story play out too often, but without the VP.