Talk:Coding best practices

The article is full of sweeping generalizations, non-sequturs, and contaversial advice presented as fact. It is amusing that it is accidentally correct in saying that the practices described have "incredible" (i.e not credible) value.

This page gets into lifecycle, requirements, etc. best practices. But the title is *Coding* best practices.

Also, many of the best practices listed for requirements, architecture, etc. aren't necessarily best practices. For example, Extreme Programming disagrees with them, yet is a very valid methodology. DRogers 17:11, 12 September 2006 (UTC)[reply]

Criticism of Article content and tone.

As an informative article, I feel the article's casual and possibly lecturing tone detriments from the value or emphasis of the article. In certain places, (e.g a quick Google search will turn up...) the information source is vaguely hinted at.

As such, the article fails to

1. give a reasonably complete overall picture of coding conventions, 
2. link users to related topics, 
3. introduce them to related keywords and categories for the people looking for more in-depth information.

I feel that the format given below is more suited for

The format: Meaning of 'Best coding Practices', what do they refer to, not refer to.

What are the categories/conventions which are generally accepted as BCP?

No one set of practises. Situation specific.
Brief discussion of possible aims - ease and speed of development, less bugs, speed, stability, portability etc,
and how compromises are made on the priority of aims.
 Based on Language - General and specific coding conventions e.g. hungarian notation, 
 Based on desired results, who the end-user is, what his requirements are.

How does this translate into an approach at each level, e.g.

pre- and post- contracts for writing a procedural function, 
OOP based class-design, 
Design Patterns for local class-interactions, 
Modular approaches (Test driven development)
Implementational approaches (extreme programming)

Discussion of studies/recommendations/preferences of eminent figures in the industry.

Peer Review

Article seems to suggest that Peer Review means looking at other people's code to see what's the best way to do things. That's not what peer review means at all. Rather it means having other people look at your work, to identify any problems in your own code. --duncan (talk) 09:48, 10 February 2009 (UTC)[reply]

Unclear article

This article is in serious need of a cleanup. As it stands, it is incomplete, suggestive and even misleading. I'd almost prefer it to be deleted as it requires complete rewrite anyway. -- mafutrct (talk) 13:57, 11 November 2009 (UTC)[reply]

Rewrite

This article is badly written and off topic. I was looking for a conclustion to coding dilema myself but will have a go at rewriting this article instead.

The title "Coding Practices" would be more appropriate with a section on "Best coding practices".

This article currently seems to be a vague, inaccurate, inexperienced and personal view on project development.

This article should really be covering the use of comments and layouts in code, naming convention of variables, methods etc, use of switches/ifs, the differences these changes have in a range of languages and the choices to be made based on the situation in hand. SkeaterMedia (talk) 07:16, 22 April 2010 (UTC)[reply]