They’re out there and that’s where the legend comes from but they’re rare. And increasingly becoming rarer.
I’ve been in a team that was assigned a list of bugs to work through. I had my Silicon Valley mentality, I wanted to prove in worth having there, and I just like getting things done.
So after a week I had fixed 35 bugs. Analyzed each issue, found core cause, developed correct fix and regression tested each one. Fun!
The other two team members had fixed .... 1.
This was bad for team dynamics obviously.
Other teams I’ve been in I was always the fastest blasting through bugs and having reputation with the QA team. But for Dev speed I was certainly not getting 10x more features done than other good engineers. It’s hard to compare features - each are different and they’re not all same sized. So who knows. But feeling wise I was just on par with other good engineers I knew, faster than poor engineers.
But I know some hardcore geeks who always did stuff I couldn’t do like program 3D fractal generators in assembler. Or the legend at apple who I once had to visit with a problem nobody could figure out - he didn’t know anything about our team or the project but he provided a solution inside 5 minutes and half coded it in that time too. That’s a legend. PhDs and scientists I worked with the advanced technology group at apppe spoke about him in hushed voices. He was the guy to go to when nobody knew what to do. Won’t mention his name but it was a memorable experience. How could he even understand what we were doing so fast let alone come up with a solution nobody had thought of .... myths!!
But in practical situations I am 100% with the top comment here - team matters way more than individuals. It’s like any team sports. The team that plays together the best wins, not the team with the most talented individuals.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
They’re out there and that’s where the legend comes from but they’re rare. And increasingly becoming rarer.
I’ve been in a team that was assigned a list of bugs to work through. I had my Silicon Valley mentality, I wanted to prove in worth having there, and I just like getting things done.
So after a week I had fixed 35 bugs. Analyzed each issue, found core cause, developed correct fix and regression tested each one. Fun!
The other two team members had fixed .... 1.
This was bad for team dynamics obviously.
Other teams I’ve been in I was always the fastest blasting through bugs and having reputation with the QA team. But for Dev speed I was certainly not getting 10x more features done than other good engineers. It’s hard to compare features - each are different and they’re not all same sized. So who knows. But feeling wise I was just on par with other good engineers I knew, faster than poor engineers.
But I know some hardcore geeks who always did stuff I couldn’t do like program 3D fractal generators in assembler. Or the legend at apple who I once had to visit with a problem nobody could figure out - he didn’t know anything about our team or the project but he provided a solution inside 5 minutes and half coded it in that time too. That’s a legend. PhDs and scientists I worked with the advanced technology group at apppe spoke about him in hushed voices. He was the guy to go to when nobody knew what to do. Won’t mention his name but it was a memorable experience. How could he even understand what we were doing so fast let alone come up with a solution nobody had thought of .... myths!!
But in practical situations I am 100% with the top comment here - team matters way more than individuals. It’s like any team sports. The team that plays together the best wins, not the team with the most talented individuals.