|
|
|
|
|
by cletus
5192 days ago
|
|
> What I learned when I came of age was that I am a Starter. The more accurate way to put this is "I am not a Finisher". The argument here is that starting and finishing are two equally valuable skills that are somehow equivalent. A "Starter" is a fairweather friend. It's easy to start things. Most people like starting things. Note this is different from networking and so forth, which is really a separate skill altogether. Employers, business partners and investors will look at what you've finished and don't care what you've started. When something is 80% done or when times are tough or it's time to soldier on and run the last mile of the marathon, nobody wants the guy around who says "well, I started, that's my skill but I'm done now, I suggest you find a Finisher". Not being a Finisher isn't a different skill--it's a character flaw. |
|
The ability to look at a vaguely specified problem and say "Okay, here's how we're going to attack it, and here's what we need to build to have something that works" is a very valuable skillset, and not everyone has it.
Now, remember that "finished" is not the same as "launched". Usually, my responsibilities continue up to the point where we can get a product into the hands of users and train the people who'll be maintaining it after me. But there's a fairly large role for maintenance programmers, people who are responsible for little tweaks even though the system is mostly working as desired, and if you're a Starter, there's no reason for you to do that work yourself.