We’ve talked about it more often: everything is perception. But, sometimes, assumptions can create a self containing environment where perception doesn’t get measured. Every point of view is, for instance, just one of many points of views. Therefore, decide who the target audience is for your designs.
Perception is one silly thing. It means that everyone has their own view on reality. In Software Design this isn’t any different than in the rest of our lives. The thing is, we rarely check if the perception one has is the same from others and our own.
Software Development isn’t easy, that much is clear to us now. But, like I state in my previous post, software design is. At least, when we know who we are writing it for. In my opinion we still write too much for the technical department. Even too much for people who have nothing to do with software development or the project in the first place. Departments like Quality Assurance make sure we write the things down they tell us that must be part of the design, even if an end user or project owner doesn’t understand any of it. Even if it doesn’t make sense to the development department.
Is there a way in which we can satisfy both the audience that needs our designs and the people who govern the quality of our designs? Aren’t the readers and accepters of our designs the guardian of quality? Isn’t quality measured in the amount of value for it’s peers?
Do you guys have any thought on this? Please post below.
