This project is read-only.

Motivational strategies to keep programming


This is a light issue although could get more serious if not addressed.

Does anyone find it hard to get going with c# again after a weekend, holiday or after being to a party for example? I do!!

I just had to force myself to pick up my c# programming book after being to a party last night which turned out to be a late night.

This a topic that is seldom talked about in the programming world so its a good issue to start off with.

Has anyone any motivational tips on how to keep going with c# especially after something upsets your stride? or you can't bear to even think about unravelling some bad code that you wrote a little while ago.

Also feel free to add any issues you have into this Project and we'll see what happens.

Kind Regards


maverick9 wrote Feb 19, 2013 at 5:34 PM

Hi Matt, I'm glad you bought up this issue! I feel the same most times on weekends. I'm afraid I'll burn-out because my day-time job is also programming.
Also, I need a good project/idea to keep me motivated for C#. Currently I don't have a clear idea what I will do after reading the C# book.
I'm thinking of creating a personal finance software project or contributing to an existing open-source C# project.
The above 2 ideas are keeping me motivated for now.

However, I feel there are existing personal finance software out already ( ) etc... So, I'm not sure I want to reinvent the wheel.. ( demotivating factor )...

MichaelOverhorst wrote Feb 24, 2013 at 11:08 PM

Hi both,

Same as maverick9, i also have a full time job which involves software development, ofcourse you cannot pick your projects in real life, sometimes there is just something that needs to be done. In the weekends i don't have much time to program but i do read alot to keep my self up to date. When i do program, it will always be something that has not been done yet, i would never ever be motivated to reinvent the wheel and ofcourse this is quite pointless anyway. But if you're still learning the language, every practise you can get will help you to get somewhere. After (like in my case) 8/9 years or so, projects on the side are not that important anymore or so it feels, it's just like speaking your native language and as long you keep yourself informed about new features, you're set.

Anyway, i came across this codeplex and i think this may help many people to keep motivated as they can compare the final product with each other. I might toss something in when there is a fun goal though, who knows it might help. :)

Kind regards,

siddharths067 wrote Mar 3, 2013 at 8:06 AM

Well Matt,
I Agree With you , I am in 9th Grade and here i am in middle of my board exams and so i have to manage my life between the sides of a Student and a Linux Kernel Developer but the fact that C# will help me in development of Windows Forms and Windows Platform which will help me reach a large market which would get me Recognition is what that keeps my C# Blood Pumping , You know its all about the Thirst of Knowledge and Recognition is what that keeps me driving!!!

siddharths067 wrote Mar 4, 2013 at 3:46 AM

Matt The Group Seems TO Be a Little But Dull Lately We Really Need Something..

siddharths067 wrote Mar 4, 2013 at 3:50 AM

How to Motivate Programmers
May 22, 2009
There's an inherent paradox in motivating programmers. I think this Geek Hero Comic illustrates it perfectly:


It's a phenomenon I've noticed even in myself. Nothing motivates like having another programmer tell you they're rewriting your code because it sucks. Dave Thomas has talked about this for years in his classic Developing Expertise presentation, supported by the following quote:

Interestingly enough, a friend of mine (who is a quality control manager in a hospital) often makes identical statements in reference to doctors: Polite requests, coercion, etc. are useless at best and often detrimental. Peer pressure and competition are the key.
Don't try to race sheep,
Don't try to herd race horses

Yes, the use of the term sheep is mildly derogatory, but the general principle is sound: use motivational techniques that are appropriate to the level of developers you're working with. If you have neophyte developers, herd them with maxims, guidelines and static rules. If you have experienced developers, rules are less useful. Instead, encourage them to race: engage in a little friendly competition and show off how good they are to their peers.

Posted by Jeff Atwood

I Got This Thing From a Website

wrote Mar 4, 2013 at 4:05 AM