Background to coding guidelines; Culture, knowlege, and behavior
-
Derek M. Jones, "The New C Standard" Introduction, p.53 "Every language has a culture associated with its use. A culture entails thinking about and doing certain things in a certain way. How and why these choices originally came about may provide some interesting historical context and might be discussed in other sections of this book, but they are generally not relevant to Coding guideline sections." "Culture is perhaps too grand a word for the common existing practices of C developers. Developers are overconfident and insular enough already without providing additional blankets to wrap themselves in. The term existing practice is both functional and reduces the possibility of aggrandizement." "Existing practices could be thought of as a set of assumptions and expectations about how things are done (in C). The term C style is sometimes used to describe these assumptions and expectations. However, this term has so many different meanings, for different developers, in different contexts, that its use is very prone to misunderstanding and argument. Therefore every effort will be made to stay away from the concept of style in this book." "In many ways existing practice is a meme machine. Developers read existing code, learn about the ideas it contains, and potentially use those ideas to write new code. Particular ways of writing code need not be useful to the program that contains them. They only need to appear to be useful to the developer who writes the code, or fit in with a developers preferred way of doing things. In some cases developers do not thoroughly analyze what code to write, they follow the lead of others. Software development has its fads and fashions, just like any other information-driven endeavor."
-
Derek M. Jones, "The New C Standard" Introduction, p.53 "Every language has a culture associated with its use. A culture entails thinking about and doing certain things in a certain way. How and why these choices originally came about may provide some interesting historical context and might be discussed in other sections of this book, but they are generally not relevant to Coding guideline sections." "Culture is perhaps too grand a word for the common existing practices of C developers. Developers are overconfident and insular enough already without providing additional blankets to wrap themselves in. The term existing practice is both functional and reduces the possibility of aggrandizement." "Existing practices could be thought of as a set of assumptions and expectations about how things are done (in C). The term C style is sometimes used to describe these assumptions and expectations. However, this term has so many different meanings, for different developers, in different contexts, that its use is very prone to misunderstanding and argument. Therefore every effort will be made to stay away from the concept of style in this book." "In many ways existing practice is a meme machine. Developers read existing code, learn about the ideas it contains, and potentially use those ideas to write new code. Particular ways of writing code need not be useful to the program that contains them. They only need to appear to be useful to the developer who writes the code, or fit in with a developers preferred way of doing things. In some cases developers do not thoroughly analyze what code to write, they follow the lead of others. Software development has its fads and fashions, just like any other information-driven endeavor."
-
Derek M. Jones, "The New C Standard" Introduction, p.53 "Every language has a culture associated with its use. A culture entails thinking about and doing certain things in a certain way. How and why these choices originally came about may provide some interesting historical context and might be discussed in other sections of this book, but they are generally not relevant to Coding guideline sections." "Culture is perhaps too grand a word for the common existing practices of C developers. Developers are overconfident and insular enough already without providing additional blankets to wrap themselves in. The term existing practice is both functional and reduces the possibility of aggrandizement." "Existing practices could be thought of as a set of assumptions and expectations about how things are done (in C). The term C style is sometimes used to describe these assumptions and expectations. However, this term has so many different meanings, for different developers, in different contexts, that its use is very prone to misunderstanding and argument. Therefore every effort will be made to stay away from the concept of style in this book." "In many ways existing practice is a meme machine. Developers read existing code, learn about the ideas it contains, and potentially use those ideas to write new code. Particular ways of writing code need not be useful to the program that contains them. They only need to appear to be useful to the developer who writes the code, or fit in with a developers preferred way of doing things. In some cases developers do not thoroughly analyze what code to write, they follow the lead of others. Software development has its fads and fashions, just like any other information-driven endeavor."
Utterly pretentious bullshit: write code, make money. That's it. :)
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
Derek M. Jones, "The New C Standard" Introduction, p.53 "Every language has a culture associated with its use. A culture entails thinking about and doing certain things in a certain way. How and why these choices originally came about may provide some interesting historical context and might be discussed in other sections of this book, but they are generally not relevant to Coding guideline sections." "Culture is perhaps too grand a word for the common existing practices of C developers. Developers are overconfident and insular enough already without providing additional blankets to wrap themselves in. The term existing practice is both functional and reduces the possibility of aggrandizement." "Existing practices could be thought of as a set of assumptions and expectations about how things are done (in C). The term C style is sometimes used to describe these assumptions and expectations. However, this term has so many different meanings, for different developers, in different contexts, that its use is very prone to misunderstanding and argument. Therefore every effort will be made to stay away from the concept of style in this book." "In many ways existing practice is a meme machine. Developers read existing code, learn about the ideas it contains, and potentially use those ideas to write new code. Particular ways of writing code need not be useful to the program that contains them. They only need to appear to be useful to the developer who writes the code, or fit in with a developers preferred way of doing things. In some cases developers do not thoroughly analyze what code to write, they follow the lead of others. Software development has its fads and fashions, just like any other information-driven endeavor."
GAMerritt wrote:
In some cases developers do not thoroughly analyze what code to write, they follow the lead of others.
Some? I'd say this was a gross underestimation of the perserverance of potentially poor practices. This sounds like just a grand way of saying that certain practices and thought processes become the accepted norm, and contemplating other choices or the reasons for the initial decisions is beyond the wit of the jobbing coder. It is a fact that styles arise out of the architectures of the time, and these styles achieve a certain sense of immortality, long after the point at which the architecture serves to act as a valid constraint. Patches get applied to the underlying languages with varying levels of success. I have a question though. You've quoted, to a great extent, somebody else's thoughts on this matter; what are your thoughts? Where is your voice on this - you've not been shy with it before?
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
Derek M. Jones, "The New C Standard" Introduction, p.53 "Every language has a culture associated with its use. A culture entails thinking about and doing certain things in a certain way. How and why these choices originally came about may provide some interesting historical context and might be discussed in other sections of this book, but they are generally not relevant to Coding guideline sections." "Culture is perhaps too grand a word for the common existing practices of C developers. Developers are overconfident and insular enough already without providing additional blankets to wrap themselves in. The term existing practice is both functional and reduces the possibility of aggrandizement." "Existing practices could be thought of as a set of assumptions and expectations about how things are done (in C). The term C style is sometimes used to describe these assumptions and expectations. However, this term has so many different meanings, for different developers, in different contexts, that its use is very prone to misunderstanding and argument. Therefore every effort will be made to stay away from the concept of style in this book." "In many ways existing practice is a meme machine. Developers read existing code, learn about the ideas it contains, and potentially use those ideas to write new code. Particular ways of writing code need not be useful to the program that contains them. They only need to appear to be useful to the developer who writes the code, or fit in with a developers preferred way of doing things. In some cases developers do not thoroughly analyze what code to write, they follow the lead of others. Software development has its fads and fashions, just like any other information-driven endeavor."
Thank you for bringing this to our attention. I have reported the author as a sesquepedalian logophiliac.
In real engineering, you do what works in practice, even if the theory says it fails. In social engineering, you do what theory says works, even if it fails in practice.
-
Thank you for bringing this to our attention. I have reported the author as a sesquepedalian logophiliac.
In real engineering, you do what works in practice, even if the theory says it fails. In social engineering, you do what theory says works, even if it fails in practice.
Oakman wrote:
sesquepedalian logophiliac.
You can get a cream for that nowadays, if you go to your doctor.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Manfred R. Bihy: "Looks as if OP is learning resistant."
-
Utterly pretentious bullshit: write code, make money. That's it. :)
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
Hey. This guy likes utterly pretentious bullsh*t. He spouts a lot of it.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
Oakman wrote:
sesquepedalian logophiliac.
You can get a cream for that nowadays, if you go to your doctor.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Manfred R. Bihy: "Looks as if OP is learning resistant."
OriginalGriff wrote:
You can get a cream for that nowadays, if you go to your doctor.
I thought the cream was for logorrhea.
In real engineering, you do what works in practice, even if the theory says it fails. In social engineering, you do what theory says works, even if it fails in practice.
