Taking your name off of a project

You cannot often choose the projects that you work on.  However, the ones you work on should reflect your principles, your asthetic sensibilities, even with all the compromises that necessarily have to take place between conception and production.

But when does it get to the point where, like Daniel Libeskind (who removed his name from the Freedom Tower project), you are prepared to take your name off of a project whose demands and compromises alter the design so substantially that it is not your creation any more?

This is certainly not new.  In the film industry, for many years, when a director wanted to take his name off of a film, it was credited to the psuedonum "Alan Smithee."  That name has racked up quite a career! (see Wikipedia article on Alan Smithee).

So, what is the line that you won't cross? 

Perhaps we don't have enough software projects where the architect is well known.  Does anyone care who the architect is?  Honestly, who remembers the name of the architect of the colosseum in Rome?  What about the architect for your home... do you know his name? 

On the other hand, I can easily imagine a day where software architects compete as individuals, just as building architects and movie directors do, for the right to work on a project of high visibility and importance.

And I can easily imagine a day when a software architect will want to take his name off of the system.