Live data from Hacker News

We fired our top talent. Best decision we ever made

medium.freecodecamp.org

121–130 of 137 posts

Re: We fired our top talent. Best decision we ever made

#121
This pretty much happened to me at a project. Coworker was positioned as leader of our project and thought I was a genius and could make her look really good. Starts pushing me really hard to do stuff I had no experience doing really quickly.

Another MBA-type coworker starts drafting me into his own initiatives. They actually were essential to the stuff we did running at all, but apparently no one actually knew that.

I overwork for a while. Eventually I get pretty burnt out and I stop being able to work at a supranormal pace. Coworker/pseudo-PM gets mad and starts badmouthing me to my actual manager. I get butthutt since I'm working 10x harder than anyone else on my project yet I'm being harassed constantly.

Eventually I have enough savings that I stop caring about getting fire. In my mind, management had unreasonable deadlines, so I began to rely on myself to decide what a reasonable level of output was. I start doing about 4 hours of work a day and stop caring about anything beyond my "daily minimum".

I started to get in really good shape, since I'd constantly sneak to the parking lot and do laps or run to the gym when no one was looking. I started returning to my religion and started reflecting a lot, and really meditating on the situation. I realized that I was being punished for my pride and arrogance and became a much more humble person.

Instead of working hard on my own work to glorify myself, I would focus on making my team members as helpful as possible. Since I was fine losing my job, I was also fine jumping on basically any metaphorical grenade for any reason and absorbing political fallout.

Eventually my entire team was absolutely in love with me, except my pseudo-PM, the MBA coworker, and my actual manager. I realize they are all just stressed out folks trying to make a living. The Pseudo-PM seems mad at me for some reason, and constantly complains about me while the rest of my team talks about me as if I am a saint. Soon pseudo-PM is let go from the company.

Eventually the whole project just gets transfered to another manager, who has reasonable expectations and seems to look out for his employees. Now life is pretty good. It was just a really surreal experience.

Re: We fired our top talent. Best decision we ever made

#122

This pretty much happened to me at a project. Coworker was positioned as leader of our project and thought I was a genius and could make her look really good. Starts pushing me really hard to do stuff I had no experience doing really quickly. Another MBA-type coworker starts drafting me into his own initiatives. They actually were essential to the stuff we did running at all, but apparently no one actually knew that.…

I'm trying to edit this but failing. Psuedo-PM leaves the company, MBA coworker is let go, project is transferred from my manager to someone reasonable.

Re: We fired our top talent. Best decision we ever made

#123
post #35

Earlier quoted context omitted.

Eh, I've joined 3 or 4 projects where there was a "genius" behind it. They liked being in control, and to a one they all talked about being irreplaceable. I don't know Rick, of course, and can't speculate on what's going on in his head, but he certainly seems like the geniuses on the projects I and others ended up rescuing from their own respective geniuses. I think everyone's quick to pile on the author, for some re…

Please don't take my analysis as a way to absolve Rick. He's the worst type.

Ok, fair, that's good, I think we probably agree more than disagree then.

I guess my take on it is that the handful of Ricks I've seen, they all wanted to position themselves as irreplaceable, as kings of the project. For them it was intentional.

Maybe not the case with the Rick in this story. Without knowing the person (or even if the person is real, or if this is a composite character from multiple situations, etc), we're all just guessing.

I'm just more inclined to sympathize with the author, because of my own experiences with Ricks. :)

Re: We fired our top talent. Best decision we ever made

#124
While a lot of the blame falls on management for, well, completely failing to manage anything or establishing a proper feedback loop where the developer(s) could contribute to management and deal with clients in a more organic way (to prevent the requirements creep, mostly), there's still a lot to blame on the developer. He evidently wasn't the genius he (and the company) thought he were and, in the eagerness to prove that he was, he made a mess.

For my part, I'm glad I'm way too lazy to be a Rick; I would never want to grab all that responsibility and, as such, I hopefully won't ever make a mess of that proportion.

Re: We fired our top talent. Best decision we ever made

#125
Rick seems to have a typical behavior reflecting a “fixed mindset”. This concept is described on the famous book from the psychologist Carol Dweck. He seemed to search for validation all that time. Since the failure would be an atemporal sign that he was not good, he denied the errors. Thankfully, according to the research, eveybody can change from a fixed mindset to a growth mindset. We all have some quantum of Rick inside us. I am reading this on a Monday. This is a good text to start the week and reflect about my behavior at my workplace.

Re: We fired our top talent. Best decision we ever made

#126
The author needs a lesson on management. Going from college, straight to a bullshit management position doesn’t give him enough experience. He needs to be managed by all types of different managers before becoming one. He is just a phony.

Sitting here, telling people that it's hard to fire. Please. Want to know what's harder? Properly managing your resources is harder. This what separates boys from men.

A lot of smart people are 'Ricks', and you will need to learn how to manage them properly. The Ricks will be on the A team while you can still collaborate C level ideas with your B level team.

Trash article.

Re: We fired our top talent. Best decision we ever made

#127
post #73
post #38

Earlier quoted context omitted.

If he had the respect of his coworkers, I'm guessing "Rick" was really a 10x programmer, BADLY MANAGED. You need somebody else who understand the project objectives and can put a limit to the development of "configurable" options. >Rick’s product supported a dynamic workflow with over fifteen thousand permutations. In reality 99% of our use cases followed one of three paths. The team hard-coded the workflow. This rem…

I think you misunderstand what "10x programmer" is intended to mean (even though I hate this term and think it is mostly rubbish). A 10x wouldn't make some ungoldly amount of complexity "just because", they would implement the simplest solution that meets the given requirements - hence they're "10x more productive" than other developers; this doesn't mean 10x LOC, just being pragmatic. The ones you describe are the n…

Also a 10x Dev would usually go back to the product manager/client and say that feature X looks kind of redundant or a really edge case, but would take a significant chunk of time to code. Is it really needed for v1.0 considering it will cost 2 weeks of Dev Time?

You obviously need to have a good understanding of your clients and their needs and the way they use your product to e able to do that, but many shops simply ignore introducing their developers to the actual users of the product.

Re: We fired our top talent. Best decision we ever made

#128
post #51

Earlier quoted context omitted.

The author is not to blame for the problem of course - since the problem existed before his arrival. The author made the problem worse by implementing the wrong solution. The company was lucky to survive this misstep, and poor Rick was forced to work insane hours just to end up being fired anyway. Not a good outcome for anyone. The company looks bad for mistreating a seriously committed employee. Rick looks bad becau…

>The author made the problem worse by implementing the wrong solution From what I can tell, the author thoroughly investigated the situation, then made the (correct) decision to rewrite the entire thing from scratch. It does seem as if Rick was severely burned out from the long hours, which probably made things a lot worse. I think he shares equal blame along with the company...nobody asked him to do that, and it see…

This should certainly have been an anonymous post at the very least.

Re: We fired our top talent. Best decision we ever made

#129

Earlier quoted context omitted.

I never said I didn't have version control. To assume "at the code level it should be largely self-documenting" is to be a Rick. Comments are there to help everyone, including non-programmers understand what is going on.

I have been coding for almost 40 years and always been big on documenting code, but the problem is that code changes and documentation doesn’t always keep up. Given modern tools I’ve come to the conclusion that documenting overall purpose and specific edge cases is more than enough. For example, the file header should describe its purpose, and anything in the actual code that’s not obvious should be commented. No mor…

> I have been coding for almost 40 years and always been big on documenting code, but the problem is that code changes and documentation doesn’t always keep up.

This has always been a sign for me to tread very, very carefully. People who change code without changing the comments probably didn't read the comments, didn't read the code or didn't understand it - either way, if comment and code disagree both are probably wrong.

Re: We fired our top talent. Best decision we ever made

#130
post #3

Earlier quoted context omitted.

Also, I'm not sure I'd apply the label "genius" with someone who has copious amounts of "copy pasta" in his solely crafted code base.

Makes you wonder why the company would consider him their "top talent".

I imagine that it's because he delivered, rather than taking the time to abstract away stuff which might not need to be abstracted away.

Remember that very, very few organisations (companies or in academia) have 'quality code' as an overarching goal: rather, they want good enough code, soon. Time after time I've seen developers fall into one of two traps: abstracting too soon or too late. It's very, very difficult to avoid.

My preferred method is to just hack together something that works over a couple of iterations, then spend an iteration refactoring. It's hard to convince a business that this refactoring time isn't wasted, but it is in fact extremely valuable to the code base. 'I need to do this now so that I can satisfy your change requests later' sometimes works.

Post reply on HN