This article makes a great suggestion in the section about staying motivated and that is to be working on a project you are excited about.

As for my own advice, uninstall games, put away your console, and do anything else to cut yourself off from video games for a while. Playing games is much easier then making them. Achieving goals in games is easy. They have been designed to minimize frustration and maximize reward. So naturally you will turn to games to fulfill a sense of accomplishment because it is the quick and easy way to do that. I have found that making my own games is much more satisfying but it does take more take and work to get there. I still do enjoy playing games but I would prefer to see my own creation come to life then play somebody else's game. I am not saying you need abandon games for the rest of your life, just put them away until you finish your game.

I also think it is important to break your game up into important milestones and set goals to reach them. The milestones should be something that let you see your progress. It gets tiresome to keep working in source code where the only feedback is passing test cases. For me interactive visual feedback is the most satisfying.

I don't know what you really expect to get out of this: there's no magic solution to procrastination. It stops when you get to work. Which means that all you have to do is start.

If you're looking for some commiseration, most active posters are probably slacking in some regard to be posting here, so...there you go

In all honesty, that first step is often psychologically difficult, but it's a fake-out: once you get past the start you realize it was easy. I've experienced the same in both art projects and code projects: the almost intimidating nature of a blank page or document. I think starting requires practice just like anything else: the more times you buckle down and just START ALREADY, the easier it becomes and the more familiar you become with the mental reward of feeling accomplished.

HappyCoder makes an excellent point that games are designed to make accomplishment easy and fast: that's why our brains like games. The rules are simple, the challenge is straightforward, and the feedback is instantaneous. Life sucks, rewarding experiences in life are harder to come by, and take more time to achieve. Hence why so many people dive into games to feel those quick shots of reward.

Real accomplishment lasts longer and feels better though, keep that in mind. Those games you're comparing your own project to weren't made by you. The one you'll hopefully finish (by starting now) will have been made by you, even if it doesn't measure up it's a creation from your own hands. That makes it immensely more meaningful.

TL:DR; - get to work.

Edit: I will add one thing: if you're working through code that doesn't give you enough rewarding feedback at its own small milestones, look into using something like Trello. I use it in all my projects, and it really does give you more of a positive feedback system when you complete a piece of the coding task and can either (physically) check off an element on a card's checklist, or move a card to the "done" stack. I highly recommend it as both an organizational tool and brain candy.

I blame my procrastination on my first year computer science course. On the first assignment they showed us this basic mouse that had to find its way out of an arbitrary maze by only knowing what's in front, left or right of it. I could not solve the problem for every maze. I still cannot to this day, and it haunts me. Yes, that's right - I fail at programming.

But otherwise, I feel the most important thing is to actually work on what you enjoy doing. If you don't enjoy doing something, you might as well stop right now, because if you're like me, it's realistically never going to get finished unless it's homework. I am also a fan of prototyping new ideas as much as possible. If you find something cool that looks doable, and if you've got time, try and implement it. Regardless of whether you succeed or not, it'll give you some motivation to do some other work done.

Also, I've experimented with multiple design techniques to create applications. The obvious one is the top-down approach: implement the high-level code first, writing stubs for lower-level functions and classes, and recurse until the thing works. This doesn't work, because it takes forever to get something that compiles and see a result, real bad for motivation. Another one is the bottom-up method, where you implement the independent, low-level part of the code first, in nice, reusable modules, and then glue them all together to create something useful. This is better, but doesn't work great either, because you will probably get sidetracked and waste a lot of time, and there may be unforeseen design issues with how different parts of the program interact. It also takes a long time to get some feedback on the code.

What I found works for me is a mix of those two approaches, trying to implement the bare minimum (I don't write games, so your mileage may vary, but for instance I'll try and get basic input/output working before thinking out anything else) and design my different classes to require as little interaction as possible, and to make them as simple as possible, so that they may be tested independently. Always try and keep a single variable changing with all others constant if you want to fix issues, otherwise you will get frustrated.

Also, stop worrying about how much better other games are. I like to go with the mindset that there is always someone better than me at X, for any X. Get comfortable with this, because you will never be the best. And even if you are, you'll have no way of knowing. So just go with this, improve yourself and your games/programs, perhaps later join a team to code with, and so on... one day you'll be able to implement the effects you see in current games, but by that time you'll see even better effects, and the cycle will continue. You will always want more, all human beings do, and you can't let your motivation be eaten away by that.

@BCullis I think by now you should know exactly what i want to get from this, a good discussion. Its not often talked about.

Because there's nothing to really gain from talking about it.

The point of my "I don't know what you expect to get" starter was that procrastination as a stumbling block is only ever solved by finally getting to work, no matter how much discussing you do about it. No one has ever stopped procrastinating on a task by talking to other people about how they're putting off getting started. And it sounds like you have quite the task on your hands and an approaching deadline.

i just so happened to make the worst decision ever by getting a graphics card for xmas! I gave in, my stupid brain just wants games XD

This is why I can't take it seriously as a "lets ponder the origins and solutions to procrastination" discussion. It's an issue of discipline, and comments like this say "I don't have any". There's your answer. It's like eating junk food instead of making yourself a healthy dinner: games are immediate gratification, hard work takes time and isn't fun. Until it is, which happens pretty much once you start.

Since this is a college assignment, it's not optional (unless you're deciding passing your course is optional, in which case, game away!), otherwise I'd second someone's comment earlier that you should instead pick something you're more interested in working on. As for your theory, it reads more like denial or an excuse: "obviously it's the games' fault that I'm not motivated!" Please. You don't want to work on the project because it's work. I'm just going to say it's due to burnout from being in school for a while, I too had trouble being as motivated in the last semesters of my undergrad. But I still worked on some pretty awesome projects that got me fired up once I got started.

As stated in the article, breaking down the program in hilariously small chucks and always making a small but playable thing is the most important thing. I say always make something playable, like a prototype. You can't make a game, no matter how small pieces you have broken it down, if build it from "left to right". You have to work more or less on all part of the program a bit. You can't fully implement the graphics for zero to full if you can't interact with the game. You can't fully implement the internal workings if you can't interact with it and don't see a thing. You can't fully implement input/interaction from zero when things doesn't do anything and you can't see anything.

I think you get the idea. Today, I have no feelings when I see a blank page, even if I'm learning a new thing. I just get started with it, make many prototypes as I learn and make some prototypes for the actual project I'm working on.

For my current job I have to make a automatic data acquisition and instrument controller program in Labview for an endurance test. I started Labview about 2-3 weeks ago and I already have about 10-12 prototypes of random learning stuff, and 3 prototypes of the actual project for testing different things. Labview is a graphical dataflow language, as I saw, many programmers utterly hate it, because it's so different than most text languages.

That all folks, blah blah