C Style: Standards and Guidelines

Its coverage of the topic of C style guildlines is better than anything else I've found.

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.

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 standard, with reasons and considerations. While these chapters are really a reference, I can see reading through them over time in order to become a better developer. To those who (rightly) are concerned about creativity, consider Straker's response: "The creative element in programming is more in the design, than in the coding. All but the most stringent standards and the most detailed designs leave plenty of creative scope for the coder. The only creativity that is to be frowned on is that which adds unnecessary complexity to the code." By the way, the author has recently put the entire text of the book online [...], but I'm still ordering print copies because I'd rather re-read under a tree than at a PC. Update: Now I've read the print copy -- there's a big difference reading from a book. Straker is thorough, and it's worth reading every word -- there's a temptation to skim and skip online. When you get tired, put the book down and come back to it later. Well worth it!

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, eye movement, looking ahead, looking back, subconscious, and natural ambition can affect both programmer productivity and program correctness. Comprehensively covers commenting, naming, layout, language usage, data usage, and programming usage. This material is also relevant for C++ programmers. Excellent source of ideas for developing an individual, group, or company coding policy.