My last post, Good code coverage: Necessity vs Sufficiency, about how you should maintain high code coverage with your automated tests, seems to have really struck a nerve in a small group of people -- I got some fantastic comments, with some great pointers. Michael Foord's comment, 'Too often "testing is …
read moreThere are comments.
I get really frustrated with posts that claim your unit tests lie to you or 100% code coverage is fallacious or there are flaws in coverage measurement. These are sensationalist headlines that encourage bad behavior, by confusing new or inexperienced or argumentative or lazy developers: "well, we all know test …
read moreThere are comments.
Over at OLPC News, Wayan Vota asks: "Do you get better FOSS code ... if the developers are paid or unpaid?"
Interesting question, especially as considered in light of the OLPC code base.
As of about a year ago, virtually everybody I talked to was shocked and stunned at the poor …
read moreThere are comments.
Infoworld did a brief writeup of Snakebite; my only quibble is that MSU comes off as a more of a passive partner in the article than we actually are ;).
--titus
Legacy Comments
Posted by titus brown on 2009-02-14 at 10:46.
foo
Posted by titus brown on 2009-02-14 at 10 …
read moreThere are comments.
I'm switching several projects from darcs to either git on github, or svn on Google Code.
twill, a simple Web testing tool/HTTP driver in Python, was switched over to Google Code several months ago: see http://code.google.com/p/twill. I'll post more on twill development soon, I …
read moreThere are comments.
As Jesse writes, Trent revealed the existence of Snakebite yesterday. Snakebite is an "open network" of various machines that Trent and others (myself included) are making available to the Python community for build and debug purposes. I'm coordinating the MSU component, which basically means that I run interference for Trent …
read moreThere are comments.
A fellow prof here at MSU, Rich Enbody, whipped up the following cheat-sheet for new programmers transitioning from Python (CSE 231) to C++ (CSE 232). He welcomes comments. Here's the link:
http://web.cse.msu.edu/~cse231/python2Cpp.html
Paranthetically, he and his cohort in crime, Bill Punch, will be …
read moreThere are comments.