Seeing the Build

by irms

bugEntreprenuerial programmers can see the end product in their heads before they get started writing the spec.   That vision of the end prodcut is the reason for starting to develop in the first place.  But seeing the end product is a long way from what it takes to make a good programmer.  Really all that means is that they are good dreamers, and has nothing at all to do with writing code.

Good programmers follow specs (you do have a spec, don’t you?) and cover all the edge cases as they write code, test  and fix (write code test, and fix,  write code, test and…) But it’s the entreprenuerial programmers that muscle through that, from the very beginning, and do something mediocre programmers will never do:

See the Build

When a programmer begins to visualize how each module of his masterpiece will be built, there’s a massivley nerdy transformation that happens.  Where once we had a fairly-timid, under-tanned, smarty-pants software developer, we now have an outspoken, program-holding, pitch-talking, entreprenuer.  He gets excited about what he’s about to work on, he thinks in terms of classes and functionality, and he has an advantage on his side that few people seem to use.

Excite Someone Else

When you are able to see the build, when you see the pieces in your head, and you’re able to imagine how each piece gets built, you are in the unique position of exciting someone else.  Oftentimes, when a person likes an idea, but doesn’t jump onboard, it’s because they can’t see how it will come to be.  This is your job.  Take your excitement and paint a picture.  Walk them through the bits they can’t see, and you will create an evangelist for your masterpiece.

[ Update ]

Just as I was posting this, a nerd friend of mine sent out the following Tweet, which really does embody everything I just said above:

gregs-tweet

@ggoforth recently launched a pet project of his own, Pencil’Em, which debuted in Las Vegas. Congrats, GG!