Communications of the ACM
From Communications of the ACM
When Should a Black Box Be Transparent?
When is a replacement not a replacement?
From Communications of the ACM
In Praise of the Disassembler
There is much to be learned from the lower-level details of hardware.
From Communications of the ACM
Aversion to Versions
Code needs to run anywhere as long as the necessary dependencies can be resolved.
From Communications of the ACM
The Non-Psychopath's Guide to Managing an Open Source Project
Respect your staff, learn from others, and know when to let go.
From Communications of the ACM
Kode Vicious Plays in Traffic
With increasing complexity comes increasing risk.
From Communications of the ACM
Numbers Are for Computers, Strings Are for Humans
How and where software should translate data into a human-readable form.
From Communications of the ACM
Writing a Test Plan
Establish your hypotheses, methodologies, and expected results.
From Communications of the ACM
A Chance Gardener
Harvesting open source products and planting the next crop.
From Communications of the ACM
The Obscene Coupling Known as Spaghetti Code
Teach your junior programmers how to read code.
From Communications of the ACM
