Earlier quoted context omitted.
I'd say it applies even more to great developers. Good programming greatly multiplies a single person's work. When great developers get together and all understand a set of best practices along with bringing in unique individual talents, then their creative output will be exponentially better than a group of lesser programmers.
wouldn't that be the case with any sort of group project? i.e. hard sciences
Steve Jobs on Average vs Best Software Developers
11–20 of 130 posts
Re: Steve Jobs on Average vs Best Software Developers
#12Re: Steve Jobs on Average vs Best Software Developers
#13Even though I know I'm still a junior developer (~1 yr exp), I feel hopeless at times that I'll never approach being 'A' status especially knowing that I have many peers my age that are already far and away better than me. How would I overcome that?
Re: Steve Jobs on Average vs Best Software Developers
#14IMO truly great developers are not just developers. They are also software architects, UX and UI designers, network engineers, etc. "A" developers knock down learning curves and assimilate everything about software creation innately .
That way they can put what they are doing in the greater context of the organisation. As well as add a lot more weighting to maintainability and future flexibility over the "latest cool thing".
Re: Steve Jobs on Average vs Best Software Developers
#15We hear this a lot and somehow feel it's true but there are no reliable metrics and little verifiable data so ultimately it's just talk.
Maybe I'm out of step with the recruiting community but are there people who are sitting around going "let's round up some really mediocre candidates?"
Re: Steve Jobs on Average vs Best Software Developers
#16Re: Steve Jobs on Average vs Best Software Developers
#17A bit of a meta question: As someone who feels like a 'B' or even 'C' at times, what would it take to become an 'A' player? Is it predicated on pure talent alone, hard work, or experience? Even though I know I'm still a junior developer (~1 yr exp), I feel hopeless at times that I'll never approach being 'A' status especially knowing that I have many peers my age that are already far and away better than me. How woul…
Re: Steve Jobs on Average vs Best Software Developers
#18Re: Steve Jobs on Average vs Best Software Developers
#19I think there is a lot of talk about hiring an "A" developer, but almost nothing on what makes an A developer an A developer. More likely than not, it a continuum, and that a lot of engineers have the potential to be an A, but don't end up getting there due to one reason or another. It would be great to see some discussion on what environment could one provide that would enable A players to thrive and reach their pot…
Pay them enough, give them an interesting problem, and lock them in a room with a bunch of other A players
Re: Steve Jobs on Average vs Best Software Developers
#20A bit of a meta question: As someone who feels like a 'B' or even 'C' at times, what would it take to become an 'A' player? Is it predicated on pure talent alone, hard work, or experience? Even though I know I'm still a junior developer (~1 yr exp), I feel hopeless at times that I'll never approach being 'A' status especially knowing that I have many peers my age that are already far and away better than me. How woul…
Early on when I was learning to program, I had a very strong curiosity that made me want to understand how everything works. I think if you have that natural curiosity, it is the easiest way to become a better programmer. As I've gotten older, though, that has waned. In response, I've tried to build habits of investigating things and trying to learn about them when I don't understand them. It is tempting to just use google to find the answer, or "shotgun" it by trying all kinds of random things before you get it to work, but learning how it works is always the best, and it will pay off later.
So, I guess my main point here is to just keep tinkering and reading and getting your head wrapped around all these things so that you understand them well. Then things will eventually become "easy" and intuitive.