The "programming" in Psychology of Programming seems to have gotten associated with behavior having to do with the syntax/semantics of programming languages and the coding activity.
A few of the open questions that I'd include in PoSE that fall outside the programming language issues are:
Testing - How do people decide what to test? How do people construct tests? How do people actually use test tools (as versus the way the authors of those tools envisioned their use)?
There are also some issue here that are on the PoP/PoSe border. How do novice programmers learn to do testing? How does programming language syntax/semantics affect test strategy and behavior?
Requirements and specifications. This is a huge area. Is there a psychological separation between a requirement and a specification or is it all context dependent? What sorts of requirement representations are hard/easy to code from? Why? How do requirements errors happen? Can we come up with a taxonomy of requirements errors? What does it take to teach novice software developers to write requirements?
There are also some areas that I have more trouble translating directly to psychological issues. Whether a product installs successfully is actually far more important than whether it has bugs after
it is installed. Why do installs fail? What kinds of human errors lead to install failures? What are the psychological characteristics of systems for creating install scripts? Are they just like conventional programming languages or are they fundamentally different in some way?
Ruven
| "Sebastian Jekutsch" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 03/10/2005 08:36 AM
|
To: [email protected] cc: Subject: Re: PPIG discuss: Commercial reality (was: Competence (was: About natural naming)) |
Ruven,
thanks for your valuable mediation. I studied computer science and therefore learned about software engineering (SE) as a technical matter: using and transforming languages, following a defined and pre-planned process, or reusing successfully applied software architectures. These are the few success stories of SE but what strikes everybodies mind is that the unresolved issues are often human ones, individual (inabilities, errors, working environment, etc) and social (communication, natural language, politics, etc).
Psychology of Programming (PoP) caught my interest because as a Ph.D. I'd like to study human error in programming. (You can read about it in the next PPIG newsletter.) The first impression was that PoP has only been studying "toy" problems often using an unknown setting. That's no criticism; I believe it a prerequisite to get any useful result at all. Especially - and that's quite different to computer science - because PoP always seem to try to build a detailed model of why humans do it the way they do. For professional software engineering it would be sufficient to observe behavior (with significance to some degree, but with high external validity), not to explain it. That's for my first impression, in case you were interested in. :-)
Could you please explain the difference between PoP and PoSE? What are the open questions which are (usually) not tackled by PoP, and why? Is there some relation to the difference in studying novices and experts, or to the difference in studying coding/code comprehension and requirements elicitation?
Sebastian
-----Urspr�ngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Ruven E Brooks
Gesendet: Donnerstag, 10. M�rz 2005 14:50
An: [email protected]; [EMAIL PROTECTED]
Betreff: RE: PPIG discuss: Commercial reality (was: Competence (was: About natural naming))
The discussion of commercial issues arise because some of us have a great deal of trouble understanding the
relevance of some of the research being discussed. A large part of the postings seem to be about teaching introductory
programming; others appear directed at minor coding issues that are unlikely to have significant impact.
To the extent that psychology of programming is APPLIED psychology, relevance to real world situations is what's important.
Furthermore, many of the important areas, writing/interpreting requirements, testing, etc. appear wide open in terms of
opportunities for research.
Perhaps, we ought to start a second discussion group, psychology of software development, that focuses on psychological issues
and research that arise in professional and commercial software development.
Ruven Brooks
| Derek M Jones <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 03/09/2005 05:29 PM | To: [email protected] cc: Subject: RE: PPIG discuss: Commercial reality (was: Competence (was: About natural naming)) |
Walter,
>Isn't the first P in PPIG for Psychology?
Indeed it is. Not wishing to tread on any more nerves
than I might already have trodden on, but the interests
behind the current thread (i.e., the realities of commercial
software development) are driven by a different set
of priorities than the interests of many of those on this list.
I don't see the psychology aspect of some of the threads I
see on the list and the only explanation I have for them is
"oh, that's an academic thing".
derek
--
Derek M Jones tel: +44 (0) 1252 520 667
Knowledge Software Ltd mailto:[EMAIL PROTECTED]
Applications Standards Conformance Testing http://www.knosof.co.uk
----------------------------------------------------------------------
PPIG Discuss List ([email protected])
Discuss admin: http://limitlessmail.net/mailman/listinfo/discuss
Announce admin: http://limitlessmail.net/mailman/listinfo/announce
PPIG Discuss archive: http://www.mail-archive.com/discuss%40ppig.org/
