Hmmm

The worst thing about doing things as design somehow drives me crazy. I saw a page that is hideous and so I chop chop and done. Not until I saw the next page, I felt like grabbing the designers and throw them out of planet earth. I have to repeat the same information over and over again for the convenience of the user but why need so when it has been done before. It is not an editor and it is not a newspaper or notebook… The information is emailed and printed. At the end of the flow, I have a dozen of objects and a dozen of table processing all the information. I chopped a dozen of trees and the last page, I have to repeat again. Having a big data structure was crazy enough. The UI…. crazy enough too. I have to redo the struct or edit the struct to meet what was needed on that last page… Sigh… The requirement is getting larger so is the data. Sometimes, I guess we need to reject to keep the data healthy. Else, it is going to accumulate more and more to compensate for the none linear requirements. When it is none linear, the complexity increased. The more the trouble. Bound to have small errors here and there if there is no bridge in between. Good insight. Now I understand if previous developer wants to kill me for my design. When u r the one doing the program, u design in its simplicity. Else, design as in nobody needed to develop. Of course, anything can be developed, but is it ugly from the inside out or outside in, that’s something to be pondered.