Code tends to outlive jobs. When we create code, we are not writing for ourselves, but for an audience of peers and progeny that will look upon it and have to maintain it. Do we want them to do so with awe and respect, or with fear and disgust? Writing maintainable code not only makes our life easier, but the lives of those around us, and garners admiration, praise, and rewards - if not always financial, at the very least karmic.You can ignore the rest, the other rules make the same basic point: Write for an audience. Though, I do have a few to add: #0 understand the problem before you work on the solution and #6 never ever commit a line of code you don't understand.
So many questions: Why has she got a pink Kalashnikov? Why are they all in the bath? Why does she have a peace sign on her pants? And what is, or was, that animal?
The conclusions have often been backed up by careful scientific exploration. For example, confit, the French technique of cooking slowly in fat, is supposed to impart a unique taste and texture as the fat penetrates the meat. But Dr. Myhrvold said: “There’s no way it could penetrate. The molecules are too big.” He said double-blind taste tests proved that the same tasty results could be achieved by steaming and then rubbing some of the fat on the outside.I'm adding The Fat Duck to my list of restaurants to visit.
Programmers don't have the same need for wood-paneled expensive plushness that, say, corporate lawyers or investment bankers might. However, the office has to be aesthetically satisfying or it will be tough for anyone to take seriously the idea that the company values aesthetic internal design of computer programs. Similarly, the office has to be finished and well-executed or nobody will believe that the organization is committed to finishing products. In the long run it is impossible for an organization to be excellent in one area and mediocre in all others.
About Austin Marshall and Something More
Blog | Archives | Projects | Contact Me