Tuesday, September 10, 2013

Code Complete Chapter 34 and 35.


Notes from reading:
Code Complete: A Practical Handbook of Software Construction, Second Edition by Steve McConnell Link: Amazon 
I have been reading this try to improve my skills I figured I could jot down some notes which might help it sink in my brain and who know you might find it interesting.

McConnell makes a great point here: 
"The point of having coding conventions is also mainly to reduce complexity. When
you can standardize decisions about formatting, loops, variable names, modeling
notations, and so on, you release mental resources that you need to focus on more
challenging aspects of the programming problem. One reason coding conventions are
so controversial is that choices among the options have some limited aesthetic base
but are essentially arbitrary. People have the most heated arguments over their small-
est differences. Conventions are the most useful when they spare you the trouble of
making and defending arbitrary decisions. They’re less valuable when they impose
restrictions in more meaningful areas."
I wish everyone would just listen to conventions it would free up a lot of everyone's day.  Maybe always defining strings as constants isn't the best way but if everyone just did it we could get to real programming.  

" A professional programmer writes readable code, period." Awesome quote.

Wow there is a list of books at the end to help one go from begginer to pro at Steve's company  Construx Software.

submit to reddit

No comments:

Post a Comment