small medium large xlarge

IEEE Articles

Back in 2003/4, Andy and Dave were the editors for a series of articles in IEEE Software magazine. We have those articles here in PDF form.

Practice (pdf) (Nov, 2004)

Source: IEEE Software (1)

What looked neat and tidy turns out to be not quite as structured
when the real world intervenes. Why you have to practice the practice
of programming.

Imaginate (pdf) (Sep, 2004)

Source: IEEE Software (1)

imaginate: (v) to instantiate into reality
by pure will of imagination.

Open Source Ecosystems (pdf) (Jul, 2004)

Source: IEEE Software (1)

Does corporate development
have communist roots, with its strong belief
in central planning and the interchangeability
of production programming staff units? Open source may provide a
better way.

OO in One Sentence (pdf) (May, 2004)

Source: IEEE Software (1)

Many of the cornerstones of
OO programming benefit other programming
paradigms as well. Even if you’re writing shell
scripts or batch files, you can use these techniques
to great advantage.

Nurturing Requirements (pdf) (March, 2004)

Source: IEEE Software (1)

A kind of mass
delusion seems to persist in the development
community. Many people think that there are
such things as requirements.

Three Legs, No Wobble (pdf) (January, 2004)

Source: IEEE Software (1)

Pipelines (pdf) (November, 2003)

Source: IEEE Software (1)

By stringing components or programs together, rich behavior can emerge.

Preparing the Raw Material (pdf) (September, 2003)

Source: IEEE Software (1)

We don’t write
software in programming languages, integrated
development environments or case tools, whiteboards,
or 3 × 5 cards. We write software in our heads.

Verbing the Noun (pdf) (May, 2003)

Source: IEEE Software (1)

The value of spending three months doing a
requirements analysis is not the 150-page document
produced; it’s the learning and the experience gained in the process.

The Trip-Packing Dilemma (pdf) (March, 2003)

Source: IEEE Software (1)

Why do we always oversimplify something that really is
complex, and overcomplicate something that should be easy? And
how do we stop?

The Art of Enbugging (pdf) (January, 2003)

Source: IEEE Software (1)

On a bad day you
might feel that you aren’t programming at
all, but rather enbugging the code—putting the bugs in.

State Machines (pdf) (November, 2002)

Source: IEEE Software (1)

Zero Tolerance Construction (pdf) (September, 2002)

Source: IEEE Software (1)

Mock Objects (pdf) (May, 2002)

Source: IEEE Software (1)

Software Archaeology (pdf) (March, 2002)

Source: IEEE Software (1)

Ubiquitous Automation (January, 2002)

Source: IEEE Software (1)


Copyright © 2002,2003,2004,2005 IEEE. Reprinted from IEEE Software, issue
dated as per article.

This material is posted here with permission of the IEEE. Such
permission of the IEEE does not in any way imply IEEE endorsement of
any of The Pragmatic Programmer’s Products or services. Internal or
personal use of this material is permitted. However, permission to
reprint/publish this material for advertising or promotional purposes
or for creating new collective works for resale or redistribution must
be obtained from the IEEE by sending a blank email message to
pubs-permissions@ieee.org.