What could one do every day to get him motivated to code ?

[Primoz128]

Well im asking for myself, cause i just can't do it, but i want to, only 2 times i did on large scale were 2 different summer holidays for a long time every day, and it was pain the second time forcing myself, while the first time it was funer than playing gamer...

Any ideas ? I been looking at many stuff for ages, thinking of solutions... but i can't find one.

[jesperbrannmark]

Get friends to work with. Don't sit by yourself!

[Primoz128]

Got absolutely noone who would do this.

[djes]

Listen oldschool chiptunes !

[Shield]

It's because many hobby programmers don't see any immediate results when they start coding,
so they lose interest after a couple of days. As with all the programs the beginning is a difficult but important
part because the foundation has to be made to create a solid project.

Some people set their goals too high (including myself, sometimes). It's good to take on a challenge
and to do something you didn't do before, however doing it like this has devastating effects on the mood
and will result in abandonment of the project.

It's more important for an individual to see results to keep yourself motivated.
Maybe the SCRUM process could be something interesting for you to check out (just the idea, not necessarily the process).
Basically, you decide what application to build and you create a catalog of a couple of features you'd like to implement.
You sort them after importance / priority and then you start coding and implement feature after feature.

For example if you want to create a game, a feature list might be this:

• Write basic initialization code (inits, open screen, main loop, ...).
• Create structures to keep track of game characters.
• Display the player's character and implement basic movement using the keyboard.
• Create a tile map system.
• Add first weapon for the player and implement shots.
• Create enemies and implement a way for the player to kill them.
• Implement collisions.
• Implement player animation.
• Implement enemy animation.
• Play sounds when the player attacks or gets hit.
• ...

You see, all of these features are very simple and straight forward and they can be implemented
one by one. Keep it simple! Of course this idea requires the developer to re-write certain code parts,
but that's not really a problem. A software project can't be planned out in the very beginning, things
are always going to change as problems and difficulties cannot be foreseen.

The whole idea of this approach is to be able to "show something", even if it only is to yourself.
This motivates a lot, believe me. As a hobby developer you don't really have time pressure anyway,
so take your time and keep working.

Of course you can (and should) release your software early, for example here on the forums.
It doesn't matter if it's far from finished. You only implemented a couple of features and the game
isn't really playable yet? Whatever, release it anyway. People will test it and give feedback and
you might as well raise some interest. This also gives you additional motivation if you see that people
are interested in your project.

[BorisTheOld]

Build and debug the application in your head before you start coding. This process can take several months.

Only write code when you have everything figured out, and play really loud music while you code. Steppenwolf, Santana, and AC/DC work for me.

[IdeasVacuum]

It will only come to you when you have a project that you are really enthusiastic about - when you have that, you'll have the opposite problem - not being able to leave your PC for more than 5 minutes and working through the night without even noticing that you have.

[Shield]

This process can take several months.

This is clearly the wrong approach for both hobby programmers and professionals.

[skywalk]

Good question and equally fine answers.
I would add that I see this problem of motivation in all forms of occupation.
So many people have trouble because they fail to start.
They look at the enormity of a problem and become depressed or overwhelmed.
Instead they talk about how they will do this or that INSTEAD of actually doing something.
So, my suggestion is to break down your problem to small parts that can or will be used in your larger solution.
It matters not how small the task is as long as you are able to complete the task in short order.
If you stumble, put it in a "HARD" folder and move on.
Eventually, you will see lots of "DONE" work, and you may revisit the "HARD" problems with more understanding and experience. Remember, this forum loves challenging questions.

[BorisTheOld]

This process can take several months.

This is clearly the wrong approach for both hobby programmers and professionals.

Not so! Each person finds his own way of working.

As I've mentioned once before, I have an Eidetic memory and Spatial Sequence Synesthesia. This means that everything I read, hear, see, or think about, is converted into images that occupy a time/space continuum that exists all around me. Essentially, I see all of space and time existing as a single moment. I also have no sense of the passage of time.

When developing an application I first visualize it - creating shapes in my continuum that represent all aspects of it. This allows me to navigate through the application, testing it and modifying it as necessary. Once I'm satisfied that everything is working correctly I then write the code.

My comment above was meant to be somewhat humourous, but the technique is perfectly valid.

[Zach]

Where do I sign up to have this brain defect inflicted upon me?

[deeproot]

It will only come to you when you have a project that you are really enthusiastic about - when you have that, you'll have the opposite problem

Hit the the nail on the head there ....... I badly need advice on motivation to walk away from my PC !!!

Not so! Each person finds his own way of working.

Wise words from BorisTheOld as usual!

Seriously, find a project that you really believe in and the code will flow. It certainly helps to picture the whole thing in your mind, and if some of the details are a bit fuzzy and the success of the final outcome is less certain - don't worry, just enjoy getting each bit to work! (and a bit of Santana playing loud while you do it is good too )

[Nituvious]

When I lose ambition I always talk to a friend of mine and he sometimes challenges me to program something within a short amount of time. That usually gets me motivated!

[edit]
Speaking of playlists. Guns n Roses, specifically Don't Cry always motivates me. Maybe for the nostalgic value, though.

[BorisTheOld]

Where do I sign up to have this brain defect inflicted upon me?

Sadly, it's not possible, since such a brain defect is a gift of the gods. However, DeepRoot's sage advice is a worthy substitute.

For those of you who work better with some light background music, you might want to try the following link:

http://www.youtube.com/watch?v=is14oiI9Juo

And remember to play it really loud.

[Warmonger]

Where do I sign up to have this brain defect inflicted upon me?

Sadly, it's not possible, since such a brain defect is a gift of the gods. However, DeepRoot's sage advice is a worthy substitute.

For those of you who work better with some light background music, you might want to try the following link:

http://www.youtube.com/watch?v=is14oiI9Juo

And remember to play it really loud.

That's better...

http://www.youtube.com/watch?v=HnRc46xWSfI

But really, you should just jump into a project knee deep even if you don't have it planned out completely. Ones motivation to complete a existing project is stronger then a project that hasn't seen life yet. Without any work committed its easier to throw your hands in they air and say screw it! I for one like seeing visual progress, seeing a project of mine coming together little by little is enough to keep me working on it.