Coding Slump
-
Codemonger
- Enthusiast

- Posts: 384
- Joined: Sat May 24, 2003 8:02 pm
- Location: Canada
- Contact:
Coding Slump
I'm in a coding slump right now ... you know personal problems and such effecting my programming time. I just can't focus this month until at least after 22nd. Does anybody have some solutions for me 
<br>"I deliver Justice, not Mercy"
    - Codemonger, 2004 A.D.
    - Codemonger, 2004 A.D.
-
dontmailme
- Enthusiast

- Posts: 537
- Joined: Wed Oct 29, 2003 10:35 am
-
Codemonger
- Enthusiast

- Posts: 384
- Joined: Sat May 24, 2003 8:02 pm
- Location: Canada
- Contact:
Re: Coding Slump
> I'm in a coding slump right now [...] Does anybody have some solutions
Read this interesting Usenet thread: http://tinyurl.com/6369a
Read this interesting Usenet thread: http://tinyurl.com/6369a
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.
"PureBasic won't be object oriented, period" - Fred.
on a sloping scale of disaster i'd say women barely reach above zero, one should try kids
( PB6.00 LTS Win11 x64 Asrock AB350 Pro4 Ryzen 5 3600 32GB GTX1060 6GB - upgrade incoming...)
( The path to enlightenment and the PureBasic Survival Guide right here... )
( The path to enlightenment and the PureBasic Survival Guide right here... )
Use a reward system (small managable rewards) and have the discipline to stick to it.
The reward need not be (should not be) huge, you don't want to worry yourself about how you can afford it, etc.
The reward should be something you really like/want.
The reward should NOT be taken until you have done the deed.
Eg:
When I have written the XYZ() procedure I will have a cup of coffee.
When I have written the WXY() procedure I will watch a video.
When I have written the ABC portion I will go fishing.
When I have completed the app I will have a mad, passionate love fest with my partner/myself/{insert other choice}
Whatever.
The discipline is to NOT have the reward until the task is done. The trick is to keep thinking about and building desire for the reward. "When I have done this, I get that! Oh Boy."
Sounds trite. Works great.
- When I have done this I will {insert reward}
The reward need not be (should not be) huge, you don't want to worry yourself about how you can afford it, etc.
The reward should be something you really like/want.
The reward should NOT be taken until you have done the deed.
Eg:
When I have written the XYZ() procedure I will have a cup of coffee.
When I have written the WXY() procedure I will watch a video.
When I have written the ABC portion I will go fishing.
When I have completed the app I will have a mad, passionate love fest with my partner/myself/{insert other choice}
Whatever.
The discipline is to NOT have the reward until the task is done. The trick is to keep thinking about and building desire for the reward. "When I have done this, I get that! Oh Boy."
Sounds trite. Works great.
@}--`--,-- A rose by any other name ..
-
Codemonger
- Enthusiast

- Posts: 384
- Joined: Sat May 24, 2003 8:02 pm
- Location: Canada
- Contact:
repeat it enough times and pavlov strikes again 
( PB6.00 LTS Win11 x64 Asrock AB350 Pro4 Ryzen 5 3600 32GB GTX1060 6GB - upgrade incoming...)
( The path to enlightenment and the PureBasic Survival Guide right here... )
( The path to enlightenment and the PureBasic Survival Guide right here... )
-
Codemonger
- Enthusiast

- Posts: 384
- Joined: Sat May 24, 2003 8:02 pm
- Location: Canada
- Contact:
Yup, it's a good plan ... I feel like a dog now that needs to be retrained. What I did was wrote each function and between functions had a game of starwars online. It worked pretty good. I think I will change my reward for when I code next. Pizza sounds good, need more rewards ideas though.
<br>"I deliver Justice, not Mercy"
    - Codemonger, 2004 A.D.
    - Codemonger, 2004 A.D.

