On a side note: Why do I care who you are or what you wrote? I use lots of software everyday, some I wrote, some others have written, and maybe even some you wrote. Just because I may use your code, does make you experienced. But then again when I think of experienced programmers I think of people who can write "good" code.
BTW: Does benefit mean pisses me off once everyday?? Then I guess I do benefit from your code.
Obviously, You missed the point of the chapter on style. In the book they very clearly point out, its not which style you choose(ie variable naming, etc) but the fact that you choose one and stick with it.
I would suggest you stop pretending to be an "experienced" programmer and go back and read the book. Everyone, *Everyone* has something to learn from this book. For the "experienced" programmers its a good refresher, because everyone strays from the path.
Slashdot Mirror
You still don't get it. Too bad.
On a side note:
Why do I care who you are or what you wrote?
I use lots of software everyday, some I wrote, some others have written, and maybe even some you wrote. Just because I may use your code, does make you experienced.
But then again when I think of experienced programmers I think of people who can write "good" code.
BTW: Does benefit mean pisses me off once everyday?? Then I guess I do benefit from your code.
Obviously, You missed the point of the chapter on style.
In the book they very clearly point out, its not which style you choose(ie variable naming, etc)
but the fact that you choose one and stick with it.
I would suggest you stop pretending to be an "experienced" programmer and go back and read the book. Everyone, *Everyone* has something to learn from this book. For the "experienced" programmers its a good refresher, because everyone strays from the path.