Software engineering is gravely hampered today by immature practices. Specific problems include: – The prevalence of fads more typical of a fashion industry than of an engineering discipline – The lack of a sound, widely accepted theoretical basis – The huge number of methods and method variants, with differences little understood and artificially magnified – The lack of credible experimental evaluation and validation – The split between industry practice and academic research.

— Adam Barr, The Problem with Software

To him who seeks a reason but cannot abide any hypothesis of a design, whether in the form of Providence or of the Diabolical, there remains only the rationalist’s substitute for demonology—statistics.

— Stanislaw Lem, Seth Shostak and Michael Kandel, His Master’s Voice

The material which follows is food for thought, not a substitute for it.

— Gerald Weinberg, The Psychology of Computer Programming

“three pillars” of social skills. … Pillar 1: Humility You are not the center of the universe (nor is your code!). You’re neither omniscient nor infallible. You’re open to self-improvement. Pillar 2: Respect You genuinely care about others you work with. You treat them kindly and appreciate their abilities and accomplishments. Pillar 3: Trust You believe others are competent and will do the right thing, and you’re OK with letting them drive when appropriate.

— Titus Winters, Tom Manschreck and Hyrum Wright, Software Engineering at Google

It is interesting to note that the SEI Capability Maturity Model—the ultimate in process definition and focus—has its roots at IBM, where some of its key architects have a history dating back to OS/360.

— Robert L. Glass and Tom DeMarco, Software Creativity 2.0