If Debugging Is The Process Of Removing

Some Consider The Puzzles That Are Created By Their Omissions As Spicy Challenges, Without Which Their Texts Would Be Boring; Others Shun Clarity Lest Their Work Is Considered Trivial.

In The Software Business There Are Many Enterprises For Which It Is Not Clear That Science Can Help Them; That Science Should Try Is Not Clear Either.

The Required Techniques Of Effective Reasoning Are Pretty Formal, But As Long As Programming Is Done By People That Don't Master Them, The Software Crisis Will Remain With Us And Will Be Considered An Incurable Disease. And You Know What Incurable Diseases Do: They Invite The Quacks And Charlatans In, Who In This Case Take The Form Of Software Engineering Gurus.

Our Intellectual Powers Are Rather Geared To Master Static Relations And That Our Powers To Visualize Processes Evolving In Time Are Relatively Poorly Developed. For That Reason We Should Do (as Wise Programmers Aware Of Our Limitations) Our Utmost To Shorten The Conceptual Gap Between The Static Program And The Dynamic Process, To Make The Correspondence Between The Program (spread Out In Text Space) And The Process (spread Out In Time) As Trivial As Possible.

In The Wake Of The Cultural Revolution And Now Of The Recession I Observe A Mounting Pressure To Co-operate And To Promote "teamwork." For Its Anti-individualistic Streak, Such A Drive Is Of Course Highly Suspect; Some People May Not Be So Sensitive To It, But Having Seen The Hitlerjugend In Action Suffices For The Rest Of Your Life To Be Very Wary Of "team Spirit." Very.