Here's the full, minimally-edited question:

"We are having a debate about the basic way the UI, Business Logic, and Data Access layers communicate.

My experience has been that the UI talks to the BizLogic, and the BizLogic maps between itself and the Data Access layer.. like this:

::

UI -> BizLogic -> Data …

First, see "OSCON - Open Data " by Tim Bray, then see "Set My Data Free " in Kontrawize.

Here are some quotes "At the end of the day, information outlives software and transcends software and is more valuable than software." "Data matters. It shouldn't be an afterthought. It will outlive your applications …

I do a fair amount of manual refactoring. I've used WebSphere Studio (Eclipse) to do some automated refactoring, so I have some experience in using IDE's which exploit Java's static type-checking.

However, the question of type checking in a dynamic language is interesting. I don't use a sophisticated IDE for …

In one case, the prospect had 7 interlocked databases, and wanted to do a technology upgrade. In other cases, the numbers was larger (up to 30, I think) but the problem was the same.

Essentially they said "It's taking us forever to rework this design. What should we do that …

Binstock does a quick compare and contrast between Ruby and NetRexx, showing how an active community promoted Ruby, and NetRexx's lack of a community left it languishing. I think that this analysis is only partly true, and misses part of the value of open source.

Specifically, IBM's proprietary NetRexx can't …

See The hubris of calendrical calculations. And Calendrical Calculations, Part 2.

"Here are the exact words from the client when I suggested using the "official calendar": I’m aware of other systems having tables for Holidays but I don’t know that we can piggy back off any of them …

While "Browser as OS" is what appears to be happening. The browser is the front-end for many applications. Even in the Ajax case, however, the browser is only one piece of the application, and the browser isn't relevant on the server side.

The important point that is missed in the …

Here's the scenario I see:

1. The customer bought something, and then customized it. The customization -- by definition -- must have had significant strategic value.
2. The customer set it aside, making no more changes of any kind. Okay, there were bug fixes, but nothing significant. The developers were re-assigned to something new …

Here's another symptom of a Request for Faerie Dust™:

A proposal that includes (1) analysis, (2) proof-of-concept, and (3) a plan for a solution.

Sounds sensible, doesn't it? Study it, prove that you can solve it, and write the complete plan to solve it.

Sounded sensible to me, until I …

Here's a novel point of view on open source software.

'In fact, one of the things Google likes about open source software is that it facilitates secrecy. "If we had to go and buy software licenses, or code licenses, based on seats, people would absolutely know what the Google infrastructure …