Monday, June 30, 2003
Friday, June 27, 2003
Monday, June 23, 2003
Wednesday, June 18, 2003
Tuesday, June 17, 2003
I received a weekly email from O'Reilly with short blurbs about new content on their site including a link to a story about an Old School unix adventure game... which reminded my of the Infocom "interactive fiction" games I used to play on my Commodore 64.
A quick google search later and I've found a site about interactive fiction games for the Palm platform, including winning entries from the annual interactive fiction competition. Another google search found a site for downloading actual Infocom game files, along with links to executables for playing these games on Win32, java, linux, and palm platforms. (Disclaimer: I'm not sure of the legal status of these games.)
This is certainly more than I needed to know. I don't have much free time as it is.
Sunday, June 15, 2003
Thursday, June 12, 2003
Tuesday, June 10, 2003
It seems that during last month's walkout by Democrats in the Texas legislature, the Republicans talked to some of their friends in Washington and got some help tracking down the Democrats from federal agencies including the Dept. of Homeland Security, the FAA, and the FBI. Didn't John Ashcroft assure us that the extended investigative powers would never be used against private citizens?
See this story and this story from the Washington Post.
Monday, June 09, 2003
Friday, June 06, 2003
Tuesday, May 27, 2003
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Scott Ambler's site agilemodeling.com has a few good introductory articles. The Agile Alliance site has links to many more articles from different sources.That is, while there is value in the items on the right, we value the items on the left more.
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
I seem to recall seeing an article when I found these pages in which the author promoted the idea of writing as few test cases as possible before writing code (contrary to standard extreme programming practice). Instead, he emphasized writing a test case for each debugging session/bug fix and saving each of those. Three weeks later, I can't find this reference. Please let me know if you see it.