I think this makes sense especially for smaller companies, but it does put a extra emphasis on hiring well. Basically, I'm expected to code and helping my team is secondary to that. If I want the team to succeed I need to hire people who are self motivated and competent enough that they only require a little guidance here and there.
Turns out that's very difficult to hire consistently for. Finding self motivated and highly skilled developers just isn't all that easy in todays climate of boot campers.
There’s an article that was going around again about ‘glue work’ ([1]) that has a story where an engineer gets caught up doing all this kind of mentoring, coordination and other work like that and then is passed over for promotions because they don’t have technical achievements (though they claim to have become instrumental in enabling everyone else’s technical achievements).
The article never gets to quite the right conclusion - it’s actually massive management failure - what I was thinking the whole way through was “why hasn’t somebody sat them down and told them to do their actual job??”
Mentoring and code review are both super important, but if the organisation wants you to focus on getting tickets done then you basically just have to, unless you can convince them to actually add the additional work to your actual role description or get enough seniority to add it yourself.
But it’s good to have feedback on what kind of work you’re actually going to be measured on in performance reviews, promotions etc.
I also had a very good relationship with both the VP of engineering and the senior VP who oversaw the entire product and who I'd worked with before on other projects.
I did leave eventually, but it was for unrelated reasons.
I think the reaction to your story is so strong, because many can relate to having a good work situation which eventually turns sour through something like this. It is also good to hear that handling it can be done gracefully. Like many things, it is a two-way street.
I was hired at a company to help scale their development because their app was growing fast but they needed a leap forward in architecture and approach or they couldn’t keep up with growth.
I documented everything I did from day 1, from what I was doing as well as why.
When it came review time, everything ended up reflecting really well, for I may have closed less tickets than my peers, my peers where closing more tickets than ever, and there was a direct line from my work with them to that productivity increase.
Once upper management wrapped their heads around this they completely understood why I was effective at helping shift features: the A -> B wasn’t possible without me spending lots of time with others and helping with their projects, and we would have needed more headcount to achieve what we did by having me work with the org the way I was vs trying to juggle feature work with it
It’s all about the metrics at the end of the day, in some ways. If you can demonstrate your impact across the board it’s hard to dismiss
Luckily 2 years later I went a startup and similar great experience of team work and supporting each other continued. I worked at 2 more startups which grew a lot and were super successful and the culture continued.
Only in recent times, (post 2019) I have noticed that people are obsessed with performance rating systems and gaming them. I notice junior engineers are not as curious to learn or challenge-seeking as engineers a decade. And I notice recently promoted senior engineers are not as talented either. I used to think this had to correlate with dominant programming language – c/c++/go vs ruby/java etc. but I don't know if that fully explains it.
The problem is financials on both employee and employer side.
If you actually want to have a chance at a decent lifestyle without being born into existing wealth, there aren't that many options in the first place, and of these IT is the only sector that doesn't take care much about formal qualifications - although you're almost guaranteed to make money if you have a CS degree, you have a very high chance of doing so if all you have is a coding bootcamp and willingness to learn.
However, unless you land in a well funded startup that has money to burn and not much oversight / managers have actual freedom, the organizations capable of paying that kind of money tend to be very large, very bureaucratic, and pay rises are closely tied to some sort of "performance metric" - hence if you want to rise in level and pay, you gotta game the system because HR won't just give you a pay rise based on your manager's good word, they want something as evidence, even if only to insulate themselves against claims of discrimination or nepotism).
And to make it worse, even if you're in the first case of a well funded startup, if it succeeds and grows eventually "professionalism" will creep in sooner or later - either because the company hires enough experienced people (particularly in HR and finance) that bring it with them, because the company gets pressured to do so by investors/boards/unemployment insurance/legal requirements, or because inevitably complaints of discrimination crop up.
There most definitely is a correlation here. Language shapes Thought and the more complex/expressive a language is the more does that Programmer have opportunities to explore new paradigms/ideas that expand his mind. Your knowledge footprint increases and you do get better than somebody else who learns a "simpler" language and/or just stays at the surface level without any exploration (i.e. i will just use this API and not learn about anything else).
Each repair job had the same priority but some were much simpler than others - one month I thought I’d take the base station jobs to learn and because no one else was repairing them. They took longer to fix but obviously were more crucial to operations.
At the end of the month PHB held a team meeting where pie charts of utilisation were shown and I had performed terribly against the rest of the (senior and experienced) team. That was the moment I learned that the senior staff were picking off quick and easy jobs for a reason, and that office politics was a thing.
PHB couldn’t understand my reasoning of selecting those jobs and the outcome was his dislike of my performance… glad I learned about poor bosses that early in my career.
I was reading it to a close friend just now, and I have to confess that I choked up a couple of times reading it.
So again, thank you, my friend.
p.s. You don't happen to be anywhere near the SF Bay Area? If you are (or even if you're not), please drop me a note at the email address in my HN profile.
The result was that my annual review was meh. They recognized and appreciated my work helping the department as a whole, but my individual metrics were lacking.
As I had a family to feed, I just started keeping my door closed and cranking out my own work. My reviews then imporoved. I realized that the large law firm just didn't have a system in place to reward the work I was previously doing, so I adjusted to what they wanted. "There is no spoon." :-)
I’ve seen too many stories of people optimising for the “team”, but losing their job or being looked over for promotion due to negative perception from those higher up.
The opposite is also true, sometimes unfortunately. Once a good reputation has been established (whatever is currently valued in the company), any amount of misbehaviour will be tolerated for a long time.
It shouldn’t be this way, but that’s been my experience.
One important ingredient for this is to know many companies will actively lie about their values. Typical case is, everyone tells you they value quality and feedback, while in reality everything is rushed and actual suggestions are at best thrown away in the "later" bin.
> Once a reputation has been established, it’s then possible to go about changing things, but not before.
I've noticed 2 patterns in my various gigs in the past: The virtuous cycle where I'm trusted to build something with significant autonomy from the start, I end up being happy, motivated, productive; and the vicious cycle when I'm just a new untrusted cog in their machine, my motivation & productivity plummet.
As far as I can tell I have no control over the initial condition, and the only way I could break the cycle was to start fresh in a new assignment. Some would suggest I suck it up and work my way up, but to be honest I no longer have the energy to pay my dues over and over again.
Yeah, I feel your pain on the viscous cycle. For what it’s worth, I have managed to “hang in there” in such situations and the situation turned around. Normally it requires some change in the upper management or getting into a different team/role though (as you said, a “new assignment”).
> Some would suggest I suck it up and work my way up, but to be honest I no longer have the energy to pay my dues over and over again.
I hear this too! It’s a massive pain to have to go through the “we don’t trust you” phase at a new company. Hopefully as we become more senior, this is less of a thing, but for me there’s always been a period of pain when changing jobs.
There is something: as part of the hiring process, arrange with your boss to get a warm introduction to the team. Make sure that your boss describes the challenges that led to your hiring, your qualifications (and that they're excited to have you on the team!) and present the vision of the positive future impact that you are likely to have.
I've benefited from these kind of intros when I was a consultant. The senior consultant would hand off the engagement to (junior) me by making me look like a star. Also, meeting people in person as soon as possible after you're hired boosts trust.
> Which was exactly what I thought they had hired me for!
It's good to regularly update your manager with what you're doing and accomplishing, as they may not realize it at all.
Ah, the good ol early 2000s, where devs had "offices" or "cubicles" to themselves.
I have a distinct memory from not that long ago when I was unemployed and asking people for advice on what to put on LinkedIn and on my resume.
One consistent piece of advice was "Don't list anything more than five years ago. People will think you're old!"
I thought, "Screw that, everyone already knows I'm old."
So I decided to just tell my story, all the way back to the beginning in the days of punch cards and Teletypes.
I am grateful that you appreciated that.
As it is a holiday weekend, I may not be able to get back to every reply right away.
I am grateful that zdw's submission and my comment led to such an interesting discussion! Thank you all.
My new boss admitted at our first review that he had written up a performance plan, but threw it out not long before. What happened was we just transitioned to an open office, and he got to see the line of people who would come to me for help, and how I wouldn't turn anyone away.
I was a little salty about losing my cubicle, but that experience definitely made me appreciate being in an open office.
Of course, I haven't worked in an office of any kind for years and will never take a job that isnt WFH again, so take that last bit with a grain of salt ;)
Did the culture around questions change compared with working from a shared office?
That said, the challenge is getting over the hump of being proactive. I'm not sure if it was working in an office or the agency model of hourly billing plus time sheets, but I find people are far more likely to spin their tires and waste time until I finally convince them that they can ask me questions any time.
Perhaps there's something about working remotely that people feel the need to be more independent workers, I'm not sure. I'll initiate pair programming sessions and ad hoc design discussions to get the ball rolling, and encourage them to do the same. That tends to do the trick, though as I mentioned at the start, my day to day the past 6 years has had much less mentoring responsibilities and opportunities.
Well after a few weeks it turned out not so positive. They had quite a broad knowledge of things, but not in depth. They didn't think far enough (like for example, giving the tip to "use a FIFO SQS queue" despite not really understanding the fine-print, but still they persisted and it ended up in a prod rollback), they preferred educating about code style, didn't really listen to feedback (not in the sense of ignoring it, they didn't even realize that they weren't so senior compared to the rest of the team at all) and in general slowed everyone down without bringing much benefit to the table.
In the end they didn't get fired or something like this. They did another lateral move as the team explained why the team doesn't want to continue this. After their next team change, they talked about that this specific team didn't want to accept their help and that they had received bad feedback since they didn't produce code.
Obviously this is just an anecdotal counterexample, but still this can happen as well.
A director said to me: "I can't remember the last thing you worked on." In that moment I knew it was time to leave. I was gone a few weeks later.
At the time, I was known as a "Windows expert", so they hired me to help improve that version and help the team get more familiar with Windows programming.
I would often spend the first part of the day on what I called "house calls": visiting other developers' offices to either pair program or troubleshoot bugs or just talk about Windows API best practices and the like. (Yes, we all had private offices!)
After a while, one of my colleagues asked a question that stuck in my mind: "How can you afford to be so generous with your time?"
Sure enough, a few months later I got a review with a mediocre rating and a comment: "Your productivity hasn't been quite we hoped, especially considering that the rest of the team has gotten more productive lately."
Which was exactly what I thought they had hired me for!