Why not become a lifetime supporting member of the site with a one-time donation of any amount? Your donation entitles you to a ton of additional benefits, including access to exclusive discounts and downloads, the ability to enter monthly free software drawings, and a single non-expiring license key for all of our programs.

You must sign up here before you can post and access some areas of the site. Registration is totally free and confidential.

Although I am not completely certain, the title of this book sounds more nightmarish than transcendent.

Quote

Stamping [a feature in Chandler that would allow users to transform one kind of data into another, like making an e-mail message into a calendar event] aimed to introduce a kind of productive ambiguity to the computer desktop that more closely mirrored the way people think. It was not a simple concept, even for the designers who'd invented it; for the developers who had to make it work, it was even trickier. Computer programs used silos and trees and similar unambiguous structures because they helped keep data organized and limited confusion. If an item belonged to one group, it did not belong to another; if it lived on one branch of a tree, it did not live on another...

During a particularly horrific uni assignment, I had one nightmare that was completely in assembler.

I'm not entirely sure about Rosenberg's book. Is following the progress of an as-yet unsuccessful application that hasn't delivered on any of its promises really going to teach anyone anything about software development other than "Don't crow about your product until it's launched?" Or, given Rosenberg's last comment in the interview, do you really want your friends and family to think that _all_ developers are a bunch of isolated egotists?