|
| ||||||||
PyWeek - First screenshot
After a busy day at work yesterday, I couldn't think straight. I was trying to use turtle graphics to draw the paths that made up the level, but couldn't get it to work. Today I made an early (5am) start and broke the back of it before leaving for work.
Now it's a choice between collision detection and going back over my code to make it work "right". Which is going to slow me down more?
Right now I'm leaning towards doing the collision detection. If I need to refactor then I'll find out soon enough, and there's always darcs to fall back on.
— Marlow on 2006/09/05 19:46 of Sleight of Python
Comments: (log in to comment)
Last Challenge
September 2008
[entries, ratings]
Previous
March 2008
[entries, ratings]
September 2007
[entries, ratings]
April 2007
[entries, ratings]
> September 2006
[entries, ratings]
March 2006
[entries, ratings]
(June 2006)
August 2005
[entries, ratings]
Not logged in
Login
September 2008
[entries, ratings]
Previous
March 2008
[entries, ratings]
September 2007
[entries, ratings]
April 2007
[entries, ratings]
> September 2006
[entries, ratings]
March 2006
[entries, ratings]
(June 2006)
August 2005
[entries, ratings]
Not logged in
Login
By donal.h on 2006/09/05 20:01:
It is really annoying how work has to interupt PyWeek, which is so much more interesting a challenge. Though, I did secretly fix one thing... Oh, and now I'm posting this message. I'm such a bad employee...