Programmers problems

The cover image of  "Physically Based
Rendering" by Matt Pharr/Greg
Humphrey.

Most of the time , me as a programmer/ a lot of other programmers i know are stuck between implementing a program completely ,discarding it , then moving on to another , maintaining stuff someone else wrote etc... There has never been a time where i have been in charge of implementing a project from scratch. After spending around 1.5 years at the University of Minnesota as a "Computer Science Masters Student" , i have dawned upon this realization that its never a bad time to write very good maintainable code.More importantly, the realization that reading some well designed code is a good place to start did not occur to me until just recently ( I had my lunch at the Bun Mi cafe here  while reading my favourite PBRT text book by Matt Pharr and Greg Humphrey and probably the wrap i was eating made it all click).

It should have been bloody obvious.. I was lazy. My instructor made me write code for assignments. I never looked forward since then. I know kids who sit and code for hours. I underestimated that planning that needs to go behind being able to code for hours. You cant just write code for hours.. You need a design. A design that can be extended.Something that makes sense and sticks to the behaviour of the system even when you want the system to do something completely crazy. Good code should be reassuring,ike a mother holding her child close to her bosom. Good code should make you want to code more. Good code should take care of you like you took care of it .

I dont care if i am going to copy the PBRT text cover to cover or NOT. I am going to learn to write good code. So i place my trust in you Matt/Greg. Here i come !