On the structure of software systems. Not artsy-fartsy UI design, but software structure and system structure design.
I had thought I would do my first Lesson Learned about my control for the upcoming Silverlight Contest, but recent events changed my mind. A phrase has been bandied about alot at work lately, a phrase we've all heard and uttered in one form or another at least once in our software careers. It exists in numerous variations, but essentially boils down to this: "The software is bad because the requirements were bad." I've seen it happen far too often: somebody complains that "<x> is broken" and...