[<<] Industrie Toulouse

February 22, 2005

Trying to re-use a message board is not a good example of component architecture. Being able to trust small, tough, and smart components is.
Linking to David Heinemeier's weblog and assorted thoughts about agile web development.

December 28, 2004

There are some places where traditional transactional systems have caused problems for some of our applications. I'm finally starting to come to grips with the world of asynchronous messaging, and how it might help us in the future.

November 30, 2004

This post on the wdf-dom mailing list, which covers both large projects and large issues with JavaScript/DOM development, is fascinating to me. Also a very very quick look at Nevow's LivePage technology.

June 16, 2004

Joel Spolsky has a very interesting article about How Microsoft Lost the API War

March 05, 2004

Python is an excellent "solution building" language, great for building applications out of various services and components. But it can ably produce those too.

December 29, 2003

Considering process heavy domain models versus process heavy service layers, I still don't know the best place for so-called "business logic."

December 22, 2003

Making a Page Messenger service to simplify sending and retrieving messages for web visitors opens up some interesting new possibilities.

November 25, 2003

A [seemingly] Struts influenced new Python web app server/framework, using mod_python and Zope's Page Templates.

November 12, 2003

Very quick thoughts about rule based rapid application development.

October 19, 2003

Review of a review of "Extreme Programming Refactored," which is primarily some personal thoughts about XP, its good and bad points, and why "throw-away prototyping" seldom works.

August 29, 2003

As storage interaction mechanisms are becoming more abstract in my projects, a Schema Validator pattern has started to emerge as a means of ensuring what I store is in the format desired.

July 08, 2003

A look at yet another "death of classes" post. I don't think classes are dying, but they have been terribly abused over the past decade. The tide is finally turning to smaller hierarchies and collaborating objects. I share some recent experiences with applying Zope 3 component style patterns to Zope 2 projects.

June 26, 2003

This week, I apply my RDBMS abstraction patterns to LDAP for delightfully rapid results.

May 14, 2003

A long post documenting a transition from chasing pure object-relational mapping to componentizing the data manipulation sequence and freeing myself of many headaches in the process.

May 06, 2003

Writing about ASP.NET, whyTHEluckySTIFF writes: Validation controls are way too simplistic. What if I want to validate a control...
Yes, it's been quiet lately. I'm buried deep in a project where I'm still (as always) wrestling with the...

April 22, 2003

Bill Bumgarner writes: While I have an active disinterest in Zope compatibility for various reasons, any well designed persistency...

April 18, 2003

APE is the rebranded (and apparently aggressively refactored) AdaptableStorage Zope product by Shane Hathaway. APE uses many of the...

April 14, 2003

I'm still slogging away on multiple projects, trying to bring a big mess of scripts under some more component-like control...

April 10, 2003

I started off the morning looking at Bill Bumgarner's post, "What do I need in a blogging tool?" Bill's...

April 01, 2003

A surprise series of events leads to a long-desired leap in architecture on a pair of Zope projects. One of the catalysts was a "From CMF to Zope 3" slide from Tres Seaver stating "Pluggable components are good; configurable components are better." The other catalyst was an application of a massive speedup to a critical piece of business logic in one application that had to be placed in another, only to realize how much the two code bases had forked - all in an area of customer-specific data requirements/configurations. In the course of a few hours, a configurable component solution steps into play to wean us off of the software configuration management difficulties presented by keeping important code in ZODB placed scripts. All this was done by using some common sense component design techniques, a bit of refactoring afforded by moving large scripts into classes, and use of Formulator to describe component configuration schemas. Read on for more details...

March 11, 2003

While walking home tonight, I was listening to Azure Ray on my iPod, right as I was passing Borders....