Bells and Whistles

March 1996 / Letters / Bells and Whistles

In "How Software Doesn't Work" (December 1995), I believe you presented a balanced view of the problems and existing approaches to software develo pment. More important, I didn't see a bias for any technique or method.
Jim Cardow
Director of Software Development
Tybrin Corp., Shalimar, FL
jimc@hq.tybrin.com

While I never thought that developing software programs was easy, "How Software Doesn't Work" helped me to understand the complexity of the development process. On the one hand, consumers want reliable software with all the bells and whistles. On the other hand, they want that software to be affordable. The conflict between delivering a product on time--or ahead of a competitor--and developing a reliable product is usually resolved by compromise.
James Tyrone Cooper
jamesco@ix.netcom.com

Matthew Wilson
My approach to software engineering is far more pragmatic than it is theoretical--and no language better exemplifies this than C++.

more...

BYTE Digest editors every month analyze and evaluate the best articles from Information Week, EE Times, Dr. Dobb's Journal, Network Computing, Sys Admin, and dozens of other CMP publications—bringing you critical news and information about wireless communication, computer security, software development, embedded systems, and more!

Find out more

BYTE CD-ROM

NOW, on one CD-ROM, you can instantly access more than 8 years of BYTE.

The Best of BYTE
Volume 1: Programming Languages

In this issue of Best of BYTE, we bring together some of the leading programming language designers and implementors...

Copyright © 2005 CMP Media LLC, Privacy Policy, Your California Privacy rights, Terms of Service
Site comments: webmaster@byte.com
SDMG Web Sites: BYTE.com, C/C++ Users Journal, Dr. Dobb's Journal, MSDN Magazine, New Architect, SD Expo, SD Magazine, Sys Admin, The Perl Journal, UnixReview.com, Windows Developer Network