Heard this from a drama just now and it makes a lot of sense to me. Architecture is an art, thus as an artist you should have your own stance. Put aside your boss' and customers' opinions.
Likewise, software architecture is an art, your software is an artifact – a piece of art. Therefore, you design it and you justify each part of it.
- yc
Likewise, software architecture is an art, your software is an artifact – a piece of art. Therefore, you design it and you justify each part of it.
- yc
3 comments:
While I do agree that software design is art, I can't say every input other than self-inspiration is entirely worthless.
I'm not an artist. To me, art is a form of expression. It needs no audience. If you like it, appreciate it. If you don't look at others.
You can't do that with software. Software has to have a purpose. It has to solve specific problems. Neglecting customer's opinions (usually in the form of feature request/improvements) is one fast ticket down to doomed software.
Likewise, a building has its purpose, the components and compartments too, the doors, the windows, the corridors, etc.
And no, I'm not saying that we should neglect boss' and customers' opinions, I shall rephrase it. I wanted to say we should not merely following what they suggest without having our own stance or understanding the pros and cons of the decision.
Hope that makes more sense. :-)
- yc
Understand your customer's need, understand the current trend, and stipulate them into your design or outcome with more creavity sense of attractive solutions would definitely bring a perfect "art-of-work".
No matter how good a designer in his art or design, if he/she neglect the client's expectation and demands, I would say this designer is hardly achive his/her successment in his field.
Good luck dude~~
-kathy
Post a Comment