Information Technology Reference
In-Depth Information
Altogether, although some types of problems can be found eas
ily during testing, others slip through, and some arise only with cer
tain sequences of events. Extensive testing can help check scenarios
that might arise when a single user runs the software. However, in
teractions of multiple users create additional problems that may or
may not become apparent through normal testing.
What is a programmer? Do they work in isolation?
The term programmer sometimes is used in a narrow context,
and sometimes the context is much broader. In the narrow sense, a
programmer is a person who translates algorithms into computer
programs. That is, the programmer takes the design developed by
others and writes it in a careful and precise format that can be inter
preted by a computer. In this work, the programmer must be fluent
in a specific language available to the computer's environment, and
the programmer must be able to write detailed instructions in that
language.
Although this term sometimes has this restricted meaning, the
term programmer also is used at times to refer to someone engaged
in the general algorithm development and coding endeavor. In this
broader context, part of the programmer's task likely involves some
coding of detailed instructions in a specific language. However,
other parts of the programmer's job may involve the development
of specifications, designs, algorithms, and testing. In this sense,
“programmer” may mean any problem solver who does coding—at
least from time to time.
A popular myth about software developers is that they work by
themselves, often in windowless cubicles, interacting only with the
computer in front of them. Although such a viewpoint may cor
rectly describe some programmers (especially in the early days of
computer development), this perspective largely is not true today.
Rather, because software is successful only when it meets customer
needs, today's programmers must be able to interact effectively with
clients. Programmers must be able to listen effectively as customers
talk about an application, and programmers must be able to ask in
sightful questions to clarify needs.
 
Search WWH ::




Custom Search