Where can find the "common error pattern" or "frenquently difficult
concept" in first programming language for novice programmer?

Hello Dinos,

In some ways, the answer to your question depends on the language used
by the beginning programmer. A few references to illustrate:

C and C++ examples:
  http://www.cprogramming.com/tutorial/common.html
 
Java
  http://www-106.ibm.com/developerworks/java/library/j-diag1.html

PHP
  http://www.zend.com/zend/art/mistake1.php
(and see links to other PHP problems)

Tcl/Tk
  http://mini.net/tcl/2968
(a set of links to common problems)

There are certainly recurring themes. Wrong variables. Lack of
initialization (where needed). Perhaps more mistakes from omission
than comission. If you need some more examples, search with phrases
such as
  beginner mistakes programming
or add common, frequent or similar words. I can provide more detail -
please use the clarification request if needed.

  --Maniac

---

Request for Answer Clarification by dinos-ga on 01 Oct 2002 20:41 PDT

Yes,I think I already got some information on it.
But I prefer get more information about "general issue"
(not specific programming language) or "academic resources" about it.
Can I get it?

---

Clarification of Answer by maniac-ga on 02 Oct 2002 20:58 PDT

Hello Dinos,

I don't know if I can find "academic resources" (or research) for
mistakes made by people learning how to program.

Most of the research on programming mistakes (or defects) is focused
on professional developers, not students or new developers. For
example, the "Personal Software Process" described at sites like
  http://interactive.sei.cmu.edu/news@sei/columns/watts_new/1999/March/watts-mar99.pdf
  http://www2.umassd.edu/swpi/xp/papers/IEEESWNov2001/s6056.pdf
and focus on software process improvement (in this case at a personal
level). There are a number of other methods such as "cleanroom", "pair
programming", and "inspections" and so on to improve software quality
for teams. There are a number of good text books and web sites
describing these methods - I can refer you if you are interested.

Let me also note that much of the data collected for the PSP is from
experienced people because the intent is to separate the problems of
learning a new language from the problems of software development in
general. The general categories used to categorize defects in the PSP
are pretty much language independent (spelling or syntax errors,
something missing, incorrect implementation) as well as an assessment
of when the defect was introduced. A defect found by a test could be a
design or coding problem.

I did broaden the search somewhat and found some related material that
may be helpful.

An effort to develop an "intelligent tutor" for new programmers. This
tends to be focused on specific programming problems.
  http://wwwbruegge.in.tum.de/projects/intusys/intusys_eng.html

Tips on conducting a computer research project (the programming tips
are near the end).
  http://www.virtosphere.de/schillo/research/tips.html

  --Maniac