Tracy recently asked me if there were any good guidelines about how to write configuration files -- not coding-level guidelines, but guidelines on structure and content.
I was unable to come up with anything: my Google-fu failed me, and my DevonThink database was silent (although it did have some nice testing …
read moreThere are comments.
Via http://www.nodalpoint.org/2008/01/18/one_thousand_databases_high_and_rising, on the Nucleic Acids Res "database" issue:
As we pass the one thousand databases mark (1kDB) I wonder, what proportion of the data in these databases will never be used?
This is an unsettling thought for those (wonderful) people who spend …
read moreThere are comments.
I just finished a chapter for a book, Methods in Avian Embryology, being edited by my boss, Marianne Bronner-Fraser. This chapter is intended for developmental biologists who are interested in locating regulatory modules and analyzing them for binding sites. It ended up being my outlet for a compilation of problems …
read moreThere are comments.
As many people have doubtless read, PyCon '08 has announced the tutorial sessions. This year, Grig and I are doing a workshop-tutorial on testing rather than a teaching-tutorial; what this means is that our tutorial will focus on actually applying testing tools effectively to your source code.
We're billing this …
read moreThere are comments.
Steve Yegge recently wrote a long article, "Code's Worst Enemy", about how "many lines of code" causes problems in projects.
That's obviously pretty silly. To see why, let's examine a little project I've recently started; conservatively, I estimate that it incorporates well over a million lines of code:
print 'hello …read more
There are comments.
Brett Cannon notes that GHOP is working out well, and muses about the future of the CPython test infrastructure (among other things). This is something I'm interested in as well (guess where all those testing tasks in GHOP came from? ;) and I've been confused, if not frustrated, by the apparent …
read moreThere are comments.
Andrew Binstock hits the nail perfectly on the head with his post, Beautiful Code vs Readable Code.
--titus
read moreThere are comments.