Starters, Finishers, and Large Teams
blog.andyet.com
Starters, Finishers, and Large Teams
1–10 of 13 posts
Re: Starters, Finishers, and Large Teams
#2Can't stand those "starers". Always looking.
Re: Starters, Finishers, and Large Teams
#3starters - people you hire to act as programmers because you need headcount.
finishers - actual programmers.
guards - programmers that you should pay really well but you don't because you have a non-technical project manager and you think it's the same.
Re: Starters, Finishers, and Large Teams
#4starters - people you hire to act as programmers because you need headcount. finishers - actual programmers. guards - programmers that you should pay really well but you don't because you have a non-technical project manager and you think it's the same.
Guards sound like supervisors. Starters are juniors. Finishers are senior.
Re: Starters, Finishers, and Large Teams
#5Re: Starters, Finishers, and Large Teams
#6starters - people you hire to act as programmers because you need headcount. finishers - actual programmers. guards - programmers that you should pay really well but you don't because you have a non-technical project manager and you think it's the same.
This is very accurate. I was thinking I had value as a starter but you have put me in my place!
Re: Starters, Finishers, and Large Teams
#7starters - people you hire to act as programmers because you need headcount. finishers - actual programmers. guards - programmers that you should pay really well but you don't because you have a non-technical project manager and you think it's the same.
This is very accurate. I was thinking I had value as a starter but you have put me in my place!
I was referring to the definition given in the article just to be clear.
Re: Starters, Finishers, and Large Teams
#8I'm the guy who can't be bothered to understand complexity, because it doesn't interest me.
I could put my brain to work, figuring it out, but it's hard and not satisfying. I feel satisfied when I understand code right away because it's written by a clean code programmer.
So guess I'm lazy guard or something. I could also be incompetent though. :)
Re: Starters, Finishers, and Large Teams
#9So what happens when the starters design something that just doesn't work?
How are they getting feedback without finishing?
Finishers are actually the ones I want starting the project.
Re: Starters, Finishers, and Large Teams
#10starters - people you hire to act as programmers because you need headcount. finishers - actual programmers. guards - programmers that you should pay really well but you don't because you have a non-technical project manager and you think it's the same.
I, the OP, am a starter myself. I was focused on finishers because they're often undervalued.