6 replies to this topic

[Gogeta70]

Hey guys, what's up. New member here, but not a new programmer ^_^

Anyway, i've been coding for years and have always had this problem. That is, often i will work on a project and usually get somewhere near completion of the project and then just lose the motivation to work on the project. Even if i force myself to open up the project files and try to work on it, i just kinda burn out and don't want to work on it at all... it's kinda weird.

Does anyone else have a problem like this? Any tips on getting over this lack of motivation?

[zoranh]

That behavior is typical for kids and programmers. You solve mind problems but then you have no motivation to align text boxes, to look for broken links or to complete documentation and testing.

I suppose that every programmer had to solve that problem in his head. Just try to understand that end user doesn't want to know how beautiful your class library is, how extendible class hierarchy is, etc. End user wants end product. Concentrate on that, and leave epic programming behind - you're not a kid anymore.

[Gogeta70]

Eh, that doesn't really work for me. I don't have a job as a programmer, i do it as a hobby. But you are right, i lose the motivation when it's no longer a challenge to code what i'm making. And... what's with the whole kid thing man? O_o

[zoranh]

Kids behave like that - they solve the challening part and then stop. They play with toys but give up when they have to collect the toys into the box. That's exactly what programmers do - solve challening part and then leave the rest unfinished. Grand total is unfinished product. Not even ready to give it for free download on the Internet.

I had that problem in studying years and I've (hopefully) solved it in my case. I consider that period of my life growing up as a programmer. Just keep focused on the fact that goal of programming is end product, rather than nice solution to a difficult problem. Try to understand that programming means also writing comments, writing development documentation, performing different kinds of testing, collaborating with a graphics designer, etc. Of course, there will be occurrences where programming skills are required, but that doesn't occupy more than 5% of time in practice.

[Gogeta70]

I suppose you do have a point. I guess something like this is only solved by putting forth a conscious effort.

[wim DC]

You're not alone :) >http://forum.codecal...-breakdown.html

[WingedPanther]

I face that, but the biggest thing that stops me from "stopping" is knowing that if I DON'T finish it, I'll have to come back to it later. I like to get things done right, and never have to come back to them. Not finishing isn't really an option, anyway, as not finishing stuff = fired.