Devoting More Weekend Time to Projects

12/14/14

So, I aimed for a small goal this weekend: make my own timer site to use for AgileGame sessions. A small step to making it an actual game to play online, I guess. Interacting with the clock in javascript is going to be important, too, I'm sure.

Anyways, enough rambling: small goal failed.

It seems like my weekend efforts often come to be wasted. Maybe I'm picking goals that only seem small. I mean, the timer itself is a number of little things I don't really know how to do. And not dividing those little things into their own AgileGame sessions might be a mistake in of itself. Especially since I'm now going for 10-minute sessions.

Though, this is all implying I set aside a considerable amount of time to AgileGame sessions. I did not. I got in like three legitimate sessions.

I spent much too much time sitting in front of my chromebook vaguely attacking the timer project. The few sessions I attempted were the only properly productive times, but I still allowed myself to get stuck in things I know are time sinks.

It's strange, falling into habits I know don't work.

I think my weekend strategy should just be multiple iterations of my daily strategy: short sessions with well-defined goals. Aka, AgileGame. Some part of me thinks I can do a more complicated task over the weekend, and tackle it using different tactics than the explicitly planned means of getting things done that I've been carefully crafting and practicing.

I suppose this is how I tried to tackle weekends before I attempted to make tools or strategies to be more effective. Old habits die hard?

I'll focus on smarter weekend time-management in the future. I'm doing weekdays better. Strong weekends, however, would be incredibly powerful.