The role of a Senior Developer
mattbriggs.net
The role of a Senior Developer
1–10 of 22 posts
Re: The role of a Senior Developer
#2(make that 3 so far...browser closed)
Re: The role of a Senior Developer
#3I overlooked the first "then/than", but a few sentences later you had another. (make that 3 so far...browser closed)
Re: The role of a Senior Developer
#4I overlooked the first "then/than", but a few sentences later you had another. (make that 3 so far...browser closed)
Re: The role of a Senior Developer
#5I overlooked the first "then/than", but a few sentences later you had another. (make that 3 so far...browser closed)
One of my weaknesses is being terrible at writing :-) I am trying to get passed it. Thanks for the feedback, I think I fixed them all.
Re: The role of a Senior Developer
#6Re: The role of a Senior Developer
#7I overlooked the first "then/than", but a few sentences later you had another. (make that 3 so far...browser closed)
One of my weaknesses is being terrible at writing :-) I am trying to get passed it. Thanks for the feedback, I think I fixed them all.
I have trouble with that one myself. :-)
http://www.grammar-monster.com/easily_confused/past_passed.h...
Re: The role of a Senior Developer
#8Re: The role of a Senior Developer
#9I think the same goes here. There's not some magic thing that a senior developer has that a junior developer is missing. They are simply, overall, better.
Re: The role of a Senior Developer
#10I know you admit that it's a gross oversimplification but this kind of talk still bothers me a lot. It's a lot like when, to use a (honestly shoddy) metaphor, people talk about rankings in a video game like League of Legends. Some times you'll hear talk like "the difference between a bronze and silver player is game sense!" or "objectives control!" or "mechanics!". The truth is it's all of these things and none of th…
> There's not some magic thing that a senior developer has that a junior developer is missing.
"They're just better" is a way of saying "this is magic and not quantifiable". If you cannot quantify what factors allow one developer to consistently deliver quality software on schedule, then you cannot grow your team in that direction, and are essentially rolling the dice.