tips needed; dealing with mental block while coding

[Christopher Friedt]

I think iterative approaches are good for getting out of slumps. When I 
find that I feel unmotivated, or at times overwhelmed, by a project, 
then I break it down into smaller problems. Smaller problems are always 
easier to solve.

You would be very surprised how quickly a lot of small parts add up to a 
big difference ;-)

~/Chris

Pavel Zaitsev wrote:
> As well you can help yourself to be producer of not brilliant, but reliably good code. You make a plan, and eek out a bit of code every hour. It is sort of difference between columnists and poets and novel writers, that may not sufficent code for the project.
> I guess thats where the boundary in writing, skews towards engineering. You get reliable patterns and understand of the target, backed by experience, you can proceed on even foot.
> 
> Cheers,
> Pavel
> 
>> While I haven't written a lot of code, I have experienced that too.
>> It's called "writer's block".  You have to be in a condition where the
>> ideas flow and that's not always on a fixed schedule.  I found I often
>> had good ideas, when I was doing something unrelated.  I found the same
>> thing happens when designing electronic circuits.
> 
> --
> Create Like a God, Command Like a King and Work Like a Slave
> 
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
> 
> 
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists