Coding for a living

Jonathan Ellis jonathan at
Thu Dec 22 21:54:25 MST 2005

On Thu, 22 Dec 2005 21:34:48 -0700, "Steve" <smorrey at> said:
> You mean like this?

That example has several drawbacks as a "portfolio piece."

First, it's game-oriented.  If you want to write games, fine, that's a
good thing.  If you want to write anything else, it's probably less good
than something more... practical.  Fairly or not, you'll get lumped in
with all the neophytes who want to write a game but have absolutely not
even the foggiest idea of how much effort it takes to make one.

Second, if an employer actually visited this particular site, it's not
immediately clear what the project is about.  This is a death sentance
for his interest level.

Third, and worst, it appears to be long on handwavy "planning" and short
on anything concrete.  Start small.  Build something that works, even if
it's simple.  Don't waste a lot of time planning something you have
insufficient resources (time, money, skill...) to build.  This is good
advice for most projects anyway, but it's critical if you want to show
your project off as evidence that you know what you're doing.

C++ is history repeated as tragedy. Java is history repeated as farce.  --Scott McKay

More information about the PLUG mailing list