Comments for Blue Cog Blog

Comment on PyOhio Attendee Wannabe by Catherine Devlin

Catherine Devlin — Sun, 18 Jul 2010 11:01:20 +0000

Thanks for the shout-out, and sorry we’ll miss you… just until next year, though!

Comment on COhPy Meeting – December 2009 by Brian Costlow

Brian Costlow — Sat, 20 Feb 2010 03:28:46 +0000

Just ran across this. You’ll be happy to know I quit that job in January.

Doing the talk in March…

Comment on Google Docs Backup with GDocBackup by Bill Melvin

Bill Melvin — Thu, 07 Jan 2010 23:35:48 +0000

fabrizio,

I tried both the command line version and using -autostart with the GUI and both options work well. I’ll probably end up using the command line version with Mono and Cron on Ubuntu to automate it. For now I’m still running it manually after I’ve made changes to documents. Thanks for the information, and thanks for a nice and easy way to backup Google Docs.

Comment on Google Docs Backup with GDocBackup by fabrizio

fabrizio — Fri, 01 Jan 2010 15:00:33 +0000

If you want to automate the backup process you have 2 choice:
– use the command line version and run it through ScheduledTask (win) or Cron (linux)
– use the normal (GUI) version and add the -autostart option. Plus, run it by ScheduledTask or Cron.

fabrizio (gdocbackup author)

Comment on Thoughts on TDD by Bill Melvin

Bill Melvin — Wed, 11 Nov 2009 20:52:07 +0000

Craig,

The lexer/parser sounds like a very good fit for using TDD. It’s the sort of component with sophisticated behaviors that would be easy to break when changing.

Comment on Thoughts on TDD by Craig Stuntz

Craig Stuntz — Wed, 11 Nov 2009 16:15:37 +0000

1. Actual metrics on TDD: http://research.microsoft.com/en-us/projects/esm/nagappan_tdd.pdf
2. Some specific cases work so well with TDD that it seems to me they’d be orders of magnitude harder without it. E.g., I’m writing a lexer/parser now. With a suite of tests for bugs I’ve fixed previously, I can fix new bugs without fearing reintroducing old ones. Lexers and parsers are built to handle wildly varying and frequently invalid input, so there are *lots* of cases. With TDD I can fix bugs safely.

Comment on PyOhio 2009 by D'gou

D'gou — Wed, 29 Jul 2009 00:44:18 +0000

Nice writeup!
I hope you can make it next year (and me too!).

OpenSpaces aren’t as scary as they might sound, and the convener of one doesn’t have the be one running it, just the one willing to express interest in a topic.

Comment on PyOhio 2009 by William McVey

William McVey — Tue, 28 Jul 2009 20:41:34 +0000

I believe the lightening talk you’re referring to with pygame introspection was still Gloria W. Jacobs talking about Kamaelia’s Über-cool introspection of it’s messaging mailboxes rendered with a pygame generated data flow diagram. I’m disappointed you didn’t remember my PyCon in your Living Room lightening talk. It had ponies and everything.

It’s a shame you were only able to make the first day. Second day had lots of other good talks as well.

Comment on COLARC Meeting – April 2009 by Craig Stuntz

Craig Stuntz — Wed, 08 Apr 2009 13:13:04 +0000

Thanks for writing this. I’ve passed it along to Mike and linked it in my plug for the meeting.