Half-finished projects a bad thing for prospective employers?

Question

I'm currently 19 and studying Bachelor of IT. Like any programmer I spend a lot of time pursuing pet projects. Some of them are based around promising ideas, some are just because I want to try them.

Many projects end up on hold as more important things come up, or I come up with a better idea, and I feel a little guilty for pursuing it in the first place. I hope I will end up finishing more eventually.

I read somewhere (can't remember where) that recruiters actively avoid developers that are of the "half baked" nature. I haven't had programming job of any kind, so am hoping this isn't adversely affecting my chances.

So do employers find this a turn off? Would you rather a programmer who sees projects out to the end?

Answer 1

I would say a half-finished project still gives you experience and also can demonstrate your skills and knowledge.

It also prepares you for the "real world" of work where it isn't rare for projects to be canned part way through! :-)

Answer 2

First I wouldn't call them all projects, as you write, you just try things out.

Regarding the projects themselves, yes, I believe you need to be dedicated to finish what you start. If you're not sure you need or want it, don't start. Pick up something you would want to see finished and go with it.

That may be just me. I don't like that much a process as I anticipate the final result. To see a project finished and running, that's a thrill. Not coding and hacking things together as the purpose, but hacking them to build something is.

Answer 3

Two things are most important to me in this context:

• Quality of work
• Having something demonstrable

I'd rather see a half-finished project of excellent quality than a complete but low-quality project.

And unless there's something I can actually run, it's hard to gauge the quality.

Getting as far as proof-of-concept and then moving on to something else isn't necessarily a bad thing for a hobby project.

Answer 4

You could re-frame the purpose of the project: that it wasn't to finish/implement some functionality, it was for you to learn some technology, and that by that measure you did finish project, it was a success (i.e. that you did learn whatever it was you set out to).

Answer 5

Nice question and awesome answers. Thanks.