Programmer's Block

ffaristocrat

I have a personal programming project (a web-based game) I've been trying to get started for weeks.

I. keep. putting. it. off.

It's possibly too a bit too much to chew but it's intended to be a learning exercise. I've been reading up on web tech, learning Python, researching websockets, thinking about game design, subscribing to mailing lists and lots of other things that aren't actually writing some damn code.

I feel like if I could actually get started, I'd get on a roll and be able to pound out stuff. Instead, I just jump on ultimak's Minecraft server.

What do you do when you just get stuck on really starting something?

see317

I stop posting on forums, turn off any outside distractions, turn on some instrumental music in the background and start working.

Unfortunately, if there is some magic motivation button, I haven't found it. You just need to start working.

Demerdar

Well... you just have to start. You need to exercise a little bit of self discipline.

zilo

Start smaller. Like, calculator or text-based blackjack or something.

By far the most common cause of failed programming projects is poor scoping. If you can't get yourself to get started on that project, start a different one that you know is not "too much to chew".

Satsumomo

My sister does freelance work, and the way she gets stuff done is by having "office hours".

She basically sets herself to work Mon-Thurs from 9:00 am to something like probably 6:00 pm, not sure. But this way she really gets herself working hard, and she doesn't feel bad about not working on her non-work days.

Dehumanized

if at all possible, disconnect from the internet

if required for online documentation or whatever, set time limits. 15 minutes offline, 5 minutes on.

course, that will not help you at all if you can't find the willpower to stick to it

DrProfessor

I'm an artist so maybe it's not the same... but sometimes when I'm feeling unable to continue or like I just can't draw something I just need to stop, relax for a while, stop trying to force it. It's not like this is a job, it's just a little something on the side right?

However, programming is more technical. When it comes to learning something like programming, I find I need to stop asking questions and researching solutions. I just need to grab a book and get started, or get experimenting.

Though, I would reccomend starting small too. I can barely move a box in programming. But mess with it in a way you find interesting. Just start with trying to get yourself situated.

Sometimes music helps, sometimes silence helps more, sometimes you actually need a change of environment, and sometimes you just have to start throwing sticks into your fire and get yourself excited to do this thing...

Entriech

I find when it comes to programming, I need to start small and build momentum. Choose a very small piece of what you want to make. For example, you could get your menu system up and running. With a single concrete problem to solve that takes minimal time, it might be easier to buckle down and start. Once you've knocked that one out, you may find that you're hungry for more, at which point pick another small piece and do that.

Don't worry about the pretty right now, worry about the functional. You can go back afterwards and make nicer graphics/fonts/colours. Right now just get it to work.

Ethea

I like the writers quote:

"You can't edit a blank page"

Which I always think about when I have to write the boring sections of code. Start writing code, no matter how shitty it looks. Once the code is on the page you can always go back and make it less shitty.

Seol

Have you tried TDD? One of the good things about that is how it breaks big problems down into small, manageable ones: one of its main motivations, in fact, is getting past programmer's block situations.

oldsak

Have you planned everything out? If you actually have a hard design to work off (instead of everything being in your head) and a list of things to do, it becomes easier to tackle the project piece by piece.

Valaena

When I set projects for myself I like to map out different steps on a sheet of paper. Like, literally draw a map of what I'm doing. Kind of like a flow chart.

It helps me separate different parts of a project so that if I get burnt out on one thing, I can somewhat easily switch to something different without being lost when I go back.

Tejs

zilo wrote: »

Start smaller. Like, calculator or text-based blackjack or something.

By far the most common cause of failed programming projects is poor scoping. If you can't get yourself to get started on that project, start a different one that you know is not "too much to chew".

Oh man, THIS so hard. Trying for the space shuttle right out the gate is always doomed for failure.

The other part is the actual discipline to follow through. The most 'fun' part of software development is the design phase; figuring out how you want to architect your solution and put things together. The not so fun part is actually implementing all those things you planned.

Turkey

Even if you don't have a clear idea of how to begin, just get a piece of paper and start vomiting pseudo-code on it. Even better if you do it as a followup to Valaena's advice.

When it's time to sit down to work, try dressing up even if you're at home. I've always found myself being more disciplined when I'm wearing a shirt and pants instead of, say, pajamas.