best practices

warning: Creating default object from empty value in /hermes/walnaweb12a/b57/moo.greydragoncom/nodsw/modules/taxonomy/ on line 33.
Leeland's picture

Agile Modile-Driven Development

A rather interesting message set went by today on model driven development. The article referenced is worth a read.

From Scott W. Ambler (Tuesday, June 3, 2008, at 6:35:39 AM):

In the current issue of Better Software Celso Gonzalez and I have an article entitled "Agile Model-Driven Development: Scaling Agile to Meet the Needs of Real-World Projects". The URL is

Leeland's picture

First Sleep - Intermission - Second Sleep

I found this New York Times article ( so interesting as I myself tend to wake up at about midnight or 1 AM to lay and stare at the ceiling for about an hour 3 or 4 nights a week. Which I have notice my new 15 month old son is doing too...

Leeland's picture

Behavior-Driven Development

I started poking at TDD (Test-Driven Development) a few years ago. I get really good at it, then I stop, then I get into again, then I stop and round and round I go.

Leeland's picture

A few books that really helped me out

I like reading. Sometimes the book turns on the proverbial light bulb. These are a few of the professional development books that did this for me: Peopleware : Productive Projects and Teams, 2nd Ed. by Tom Demarco & Timothy Lister (at Amazon)
Leeland's picture

Project Management leads to fun games

Well this was unexpected. I was researching the Project Management Process. Which was going great, I have been reading a lot of papers and books on the subject and getting much more comfortable with some of the more common TLAs. Problem is that it seems that every single author decided to come up with her or his own set of TLAs which makes the whole area of process and more specifically project management very fuzzy.

Ran into some very nice items though:

Leeland's picture

Version Control Repository Layouts

== Generic Expected Layout ==
Many shops adopt a source layout similar to this layout.

The root level is used as a dumping ground for all the code in the organization usually with the names broken into modules (if necessary) and each module has directories for build, distribution, source and test artifacts. The source and test directories are further subdivided by artifact type, in this case config, java, resources and sql.

* Module
*; src : Source artifacts related to the module
*; test : Test artifacts for the module
*; config : Module configuration

Thread Slivers eBook at Amazon

Syndicate content