Thread: Programming and State of mind.

It can be quite frustrating when things aren't working. You have to be very persistant and quite a pedant/detail oriented person to be a good programmer.

--
Mats

You also have to be good at ignoring the details that are just distractions in a given context, i.e., you need to be good at creating and using abstractions.

And if you're not careful, you begin speculating about the implementation of the real world just after waking up.


... yes, that has happened to me.

Originally Posted by sean

The other morning I woke up, said good morning to my wife, and thought, "wait... don't I need parentheses after saying hello?"

Depends whether it was a variable or a literal string, so you need to ask yourself - what did you actually mean when you said hello.

What I usually do is I plan out everything to a fine level of detail. I then go over my plans looking for potential problems and fixing them. Once done, I begin the programming, if relevant. I use a stage system, sort of like a video game, where I split functions into stages, describing the basic routine that should be followed, the write the function following this, starting with the basics then adding the extra complexity needed for the full effect one bit at a time. This way, I avoid the headaches though I still run into occasional problems.

When I started programming, I found myself starting to do the oddest things.

1. Thinking about a problem 16/7.

2. Trying to debug a program in my head while I am lying in bed, waiting to fall asleep. This does not help in trying to fall asleep.

3. Waking up at 2am or some other ungodly hour, turning on the computer, modifying some code, then trying to debug it. An hour or 2 later(time really flies when you're debugging), turn off the computer and getting back to bed.

4. Try to program 30 seconds after waking up. But my mind is still in bed, so everything is a challenge.

5. Trying to cram my head full of programming related stuff that are way beyond my current capabilities, and that I will probably never ever need to use.

I could go on and on, but you already get the point.

Originally Posted by happyclown

5. Trying to cram my head full of programming related stuff that are way beyond my current capabilities, and that I will probably never ever need to use.

Ah, the classic case of what I call "the law of rapid ability-learning". "One gains experience the fastest and easiest by doing things at their own level". It's a principal I've used for a while. My main weakness with programming right now is pointers. I also get a few of those items you've mentioned, but even if I haven't done any programming in a long while (mostly with planning, figuring out how to resolve an obstacle or trouble spot I encountered).

Originally Posted by jordanguyoflove

Is it only me or when writing programs you are highly susceptible of going absolutley nuts?

Because if it's only me then I must change how I program.

Thanks.

After awhile you stop going nuts and just stay that way, it's more efficient. Once i get 'in the zone' as they say, I'm a machine. I think like a machine, I work like a machine, 16, 24, 36, 48 and sometimes even 72 hours straight without drugs or sleep. I'm bipolar you see, so when these little brainstorms hit, I can get years of work done in a few days. The down side is when they end it can be weeks or months of soul crushing insanity with little or no productivity before another one hits. I once told my psychiatrist its a blessing and a curse. I wouldnt wish it on my worst enemy, but I wouldnt give it up for anything in the world. I find self-flagellation helps sometimes.