The ebb and flow of personalized information whatever falls out of my brain on a given day.  
    Updated: 2/2/03; 1:58:39 AM.

 

Click here to send an email to the editor of this weblog.
Email

Click to see the XML version of this web page.

General Interest

Macintouch
MacOS X Hints
Scripting News
Doc Searls
Hack the Planet
bOing bOing
Jonathon Delacour
Mac Net Journal
mac.scripting.com
SATN.org
2020 Hindsight
Flangy News
My Apple Menu
Dan Bricklin
Inspirational Technology
Yourish
Kris Amico
Sam Ruby
USS Clueless
Josh Lucas
Mark Paschal

Geekware

Apache XML
XML Protocols
XML 1.0 Spec
WSDL
xmlrpc.com
soapware.org
opml.org

Radio

Radio Userland
Cheat Sheet
Andy's Radio Resources
Frontier Scripting Tutorial
Matt's Book
DocServer
Radio Stories
RSS 0.92
RSS 0.91

 
 

Sunday, January 5, 2003

ncurses on OsX

I've got my own screwy way of installing ncurses under MacOS X, but this article has me rethinking things. The hard part about being ahead of the game is undoing all that has already been done. The nice part about starting over using Fink is that it should just work out of the box and I won't have to do all the work everytime.

The bad part of this is that the server I needed to make the modification on first had never had Fink installed... so this is going to take a while.

Comments ()
6:53:48 PM    


Agile Database Refactoring

Scott Ambler has written several very good articles on database refactoring from an agile development perspective: The Process of Database Refactoring, Catalog of Database Refactorings and A UML Profile for Data Modeling. There are several more; see the section titled 'Agile Database Techniques' on the main page of agiledata.org.

Evolutionary Database Design by Martin Fowler and Pramod Sadalage covers things from a slightly different perspective, while keeping to the agile methodology.

Scott also wrote this Java coding standards document, which I found somewhat amazing, as I agree with it nearly completely. I believe that this is the first article outside of Stroustrup's "The Design and Evolution of C++" where I've seen someone recommend putting constants on the left side of evaluation (comparison) operations. Perhaps I haven't been paying very close attention.

For example:

if ( someVar == 0 ) {}
if ( someOtherVar = 0 ) {}
versus
if ( 0 == someVar ) {}
if ( 0 = someOtherVar ) {}

The second comparison (with someOtherVar) is obviously a bug, but won't be caught by normal means. The easy way to catch it is to have the constant on the left side where it can not be modified. I catch about six bugs per year with this and have been doing it since about 1995. You do the math.

Comments ()
9:31:32 AM    


© Copyright 2003 Dave Ely.



Click here to visit the Radio UserLand website.

 


January 2003
Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  
Dec   Feb