Professional Integrity: The Invisible Metric of Software Engineering Excellence
16504_Of Health, Trust, Money ... and Integrity.
In this IEEE Software editorial, Robert L. Glass explores the concept of professional integrity within the software engineering industry, defining it as the alignment between one's actions (or writing) and their personal beliefs. The piece illustrates how surrendering one's judgment to others leads to psychological dissatisfaction and professional "toadyism."
TL;DR
Renowned software veteran Robert L. Glass argues that integrity—the commitment to doing a task as you believe it should be done rather than merely as others wish—is the most vital yet most easily lost professional asset. Through personal anecdotes, he reveals how "parrotting" experts or managers leads to psychological dissatisfaction and a fundamental loss of self.
Background: Beyond the Code
In the software coordinate system, we often focus on metrics like KLOC, cyclomatic complexity, or sprint velocity. However, Glass argues that the "Ethical Coordinate" is just as critical. While this piece is more philosophical than mathematical, it serves as a "theory of the practitioner," positioning the software engineer as a moral agent rather than just a technical executor.
The "Ghostwriting" Trap: When Expertise Collides
Glass describes a common industry scenario: being asked to synthesize another person's expertise into a foundational document (in this case, a software cost estimation primer).
The author identifies two catastrophic failure points when one tries to write without believing:
- Experiential Mismatch: The expert's theories often conflict with the writer's own historical data and intuition (Inductive Bias).
- Communication Noise: Attempting to articulate thoughts that are not your own leads to a "quagmire" of constant rewriting and wasted effort.
The "Casper Milquetoast" Phenomenon
One of the most profound insights in the article is the relationship between scarcity and value. Glass observes that people talk most about what they lack:
- The ill talk of health.
- The betrayed talk of trust.
- The poor talk of money.
- The "toady" (the submissive executive) talks of integrity.
Glass’s boss, "Casper," lacked the very integrity he admired in Glass. Casper had become a "toady" to his own superior, "Rumly Dogged," constantly trying to anticipate commands. This behavior isn't just a personality trait; it's a structural failure in professional communication where the "Individual Perspective" is sacrificed for "Corporate Alignment."
Methodology of the Self
The "Method" proposed here is one of Active Resistance. Glass suggests that being perceived as "disagreeable" or a "stubborn cuss" is often the external manifestation of internal integrity. In software engineering, where "Trial and Error" is the best way to develop useful ideas, suppressing one's own experience for the sake of harmony is a technical sin.
Critical Insight: The Cost of Conformity
The "Results" of ignoring your integrity are:
- For the Work: Produces a product that might satisfy stakeholders but lacks truth.
- For the Self: Results in "psychologically painful" diminishment.
Summary & Future Outlook
Robert L. Glass’s work reminds us that as software systems become more integrated into the fabric of life, the integrity of the people building them becomes the final fail-safe.
Future Implications: As we move toward AI-assisted development and automated decision-making, the risk of "parrotting" an LLM or an algorithm without personal belief is the new frontier of the integrity crisis Glass identified in 2006.
Key Takeaway: Don't put your name on something you don't believe in.