Category: Software engineering

RISE: The Psychology of Computer Programming (Gerald M. Weinberg, 1971/1998) »

[The first of a planned series of posts on "Readings in Software Engineering"] The Psychology of Computer Programming, Gerald M. Weinberg, Van Nostrand Reinhold Company, New York, 1971. Hardbound, 288 pages. Personal acquisition date: 17 Oct 1978. Original edition out of print. The Psychology of Computer Programming (Silver Anniversary Edition), Gerald M. Weinberg, Dorset House [...]

Readings in Software Engineering (RISE): a new series of posts »

I have been collecting and reading books on software engineering since the 1970s, but I have found over the decades that the vast majority of programmers (and their managers) are unfamiliar with most of them. More’s the pity, for during the 38 years since I first started working in information technology (BYU Translation Sciences Institute, [...]

Five books every IT manager should read…right now »

My latest Baseline column  is up, and it talks about why you should read these five books now, if you haven’t already…and if you have read them, you should probably re-read them.  ..bruce..

Two new Baseline columns up »

The first column, “Second Class Software Quality for Major IT Projects”, talks about the curious fact that organizations are willing to spend millions, tens of millions, even hundred of millions of dollars on major IT project and yet still nickle-and-dime their software quality assurance (SQA) effort. It doesn’t help that SQA personnel are pretty much [...]

Pitfall: Allowing new features to creep (or pour) in »

[From Pitfalls of Modern Software Engineering by Bruce F. Webster (forthcoming)] Categories: managerial The impulse to constantly add new and incremental features to a software program certainly isn’t unique to modern software develoment, or to a particular technology or methodology. It derives largely from three sources. Upper management and marketing want, and sometimes need, those [...]