Software Design

On Thresholds

I had a production system go down this week - one minute no problem, the next, critical functionality stopped working.  Worse, it didn't die because something broke - it went down by design. And did so without warning.

Fail Loudly

The premise that systems should "fail fast" is pretty well established - the idea has it's own wikipedia page, and any number of books talk about it as a fundamental premise.

For example, Release It! from the Pragmatic Bookshelf makes several references to Fail Fast in Chapter 5: Stability patterns.

Working with WPF

Recently, on one of the mailing lists I read, someone wrote:

With WPF, I see development and training time being bumped up (at least) a notch or two for no reason other than having a flasher UI.

I thought it worth sharing my response ...

Syndicate content