-
Julython (in January) - a python codemonth with infrastructure, not just culture
http://www.julython.org/ is taking the approach of "gamifying" day-to-day python hacking; you just add a commit-hook that pokes their site, and they assign you "points"... reminds me of http://twistedmatrix.com/highscores/ and ( Read more... ) -
Day 30 - Final Wrapup
November is over - were you able to focus some attention on a project of your own? Where are you taking it next?
See you next year... -
Day 27 - wrapping up...
The month is coasting to a halt, thanksgiving vacation time is either a complete disruption or a good time to get some hacking done, depending :-)
This is a good time to start thinking about what you've got to show for the effort, and what you're going to do with it next. -
Day 16
We're halfway through the month; over at that other project they're hitting the 25,000 word mark. Hopefully you're plinking away at something at this point; how's it going? -
Day 13
Ok, I'm slacking almost as much on announcements/probes as I am on my own project. So at this point, I'm asking for either updates on what you've done so far, or something interesting that you've done instead. -
Day 7
We're already a week in to codemonth - you should have at least some momentum at this point, but if not, perhaps describing what you're stuck on here would help? -
Day four.
SInce we've only had local signups, I'd just say "spend that extra hour voting instead" except that the polls are already closed...
So we have two android projects and one unspecified one signed up. I'll ask for progress reports tomorrow... -
Day "one"
Starting on a holiday/party weekend might not have been the most clever choice... but start we shall. Time to start your projects! Reply here with what you're working on, what your first milestone (inchstone? remember, we're going for steady pressure, a little work each day, not marathons) is, and what you're aiming for this month... -
Codemonth 5.0!
It's Codemonth again.
As in previous years, this works like NaNoWriMo but for code, instead of stories. It's not as specific - we're not aiming for SLoC targets, as much as projects that would benefit from 30 days of attention. Every day, do something for your project:- write a test
- comment or document something
- add a feature
-
The end of a month, the start of a maintenance cycle
November is over, but rather than treating this as "pencils down, papers to the front", think of it as having built some momentum to sustain your project into the new year. Remember that codecon is back (April 2008, San Francisco, "new and improved") if you're looking for more external inspiration ( Read more... )