'Code Complete' Previewed
When I start reading a classic, I feel so good inside. "I'm going to be a genius when I'm done with this book!"......Thoughts like that.
This monday, I bought a second-hand copy of 'Code Complete' (The First Edition). Figured that if everybody thinks it's a great book ("Best Book I've Read!", " Greatest Programming Book!"), then it must be true. And that when I finish those 896 pages, I'd be a lot wiser than I am now.
Later, checking out the back cover, I discover that it's a book dealing with procedural programming!! Procedural programming?!?! What the heck?! Not even Program Design is within the scope of the book. It's just a book about coding using procedural langauges.
I haven't yet looked at the contents of the book. The book lies with the ten or so other books I am simultaneosuly reading. But I can't help wondering what the book is all about. Maybe the first four hundred pages deal with the Art of avoiding the One-Off Error. And the next four hundred are about strategies to pick suitable variable names.....
When I buy a book on programming, I expect Design Patterns Damn It!! And it's got to have "object" mentioned atleast ten times on the back cover!! And if the foreword isn't by Grady Booch, Martin Fowler, Kent Beck or one of their buddies I'd be pretty disappointed.
Anyway, this Steve McConnell must be pretty lame to be dealing with "Procedural Programming". What does he build? Mission Critical Tetris Software?
P.S: I kid! I kid!! The book is probably going to teach me stuff I Didn't Know I Didn't Know. And I'm going to go "Whoa!" And then I'll probably go "Whoa!" some more!
P.P.S: Are there catalogued procedural design patterns? A quick google search gave me nothing. I've never been involved in the creation of large-or-medium scale software using the procedural paradigm, so I really don't know, but if the field is sufficiently mature, shouldn't there be a bunch of commonly used design patterns?
Technorati Tags: code, oop, patterns
This monday, I bought a second-hand copy of 'Code Complete' (The First Edition). Figured that if everybody thinks it's a great book ("Best Book I've Read!", " Greatest Programming Book!"), then it must be true. And that when I finish those 896 pages, I'd be a lot wiser than I am now.
Later, checking out the back cover, I discover that it's a book dealing with procedural programming!! Procedural programming?!?! What the heck?! Not even Program Design is within the scope of the book. It's just a book about coding using procedural langauges.
I haven't yet looked at the contents of the book. The book lies with the ten or so other books I am simultaneosuly reading. But I can't help wondering what the book is all about. Maybe the first four hundred pages deal with the Art of avoiding the One-Off Error. And the next four hundred are about strategies to pick suitable variable names.....
When I buy a book on programming, I expect Design Patterns Damn It!! And it's got to have "object" mentioned atleast ten times on the back cover!! And if the foreword isn't by Grady Booch, Martin Fowler, Kent Beck or one of their buddies I'd be pretty disappointed.
Anyway, this Steve McConnell must be pretty lame to be dealing with "Procedural Programming". What does he build? Mission Critical Tetris Software?
P.S: I kid! I kid!! The book is probably going to teach me stuff I Didn't Know I Didn't Know. And I'm going to go "Whoa!" And then I'll probably go "Whoa!" some more!
P.P.S: Are there catalogued procedural design patterns? A quick google search gave me nothing. I've never been involved in the creation of large-or-medium scale software using the procedural paradigm, so I really don't know, but if the field is sufficiently mature, shouldn't there be a bunch of commonly used design patterns?
Technorati Tags: code, oop, patterns
posted by gavri at 8:41 PM
0 Comments:
Post a Comment
<< Home