Its coverage of the topic of C style guildlines is better than anything else I've found.
0Report
I use this standards and guidelines with misra-C, C coding standards. This include followings; Psychological factor general principle commenting naming code layout file layout language usage data usage programming usage implementing standards MISRA-C do not include naming and layout. But there are very important for productivity on team development.
0Report
Here's a readable reference on a subject many people love to avoid: coding standards. Why have them? How to choose? How do they help developers? In-depth chapters on the psychology of how people understand code (when they have to read it in order to change it), and on how to deploy a coding standard successfully. Of course, the bulk of the book is a detailed explanation of almost any kind of item you could put in a coding...
0Report
Distinguishes between commonly accepted practices and areas with several feasible alternatives. The author reserves his example of the ideal standard to the appendix. The chapter on "Psychological factors" provides many insights into how standards can improve the programming process. Elements such as pattern recognition, filtering, habit, redundancy, cues, context, chunking, the rule of seven, context switching, eye focus,...
0Report