[rsisk]

I design software for a living. Part of that design process is to run multiple design reviews where I bring in my peers, representatives from each dept. in the company, as well as customer/partners. In other words people who have a stake in the software being developed.

There is nothing like sitting in front of a group of people ripping apart your design. Or having to explain over and over again why you design things the way you did. It can be frustrating and humiliating.

Kind of like posting a design on CD.

But in the end somethings happen:

First, the other stakeholders learn from the discussion and have a good appreciation for what is being developed. Education has occurred.

Second, my design gets a thorough analysis by people that use the software and may see things differently than I did, probably pointing out legit flaws or short comings. Designs are improved.

Third, I get better at defending my design decisions. Definitely a valuable skill, especially when you are trying to convince the engineers they need to write the software in a particular way. More education has occurred.

And ultimately, I am the designer, so I get to decide what I do with the feedback. Some makes it into the software, and some gets ignored. But in the end the world is a better place for having done the design review.

So keep posting your ideas to the CD thrashing machine and make use of the positives and learn from the negatives.