Communications of the ACM
Improving Section 230, Preserving Democracy, and Protecting Free Speech
Proposing a framework for a decentralized market where no one party controls the flow of information.
From Communications of the ACM
This Is the Foo Field
The meaning of bits and avoiding upgrade bogdowns.
From Communications of the ACM
A Lesson in Resource Management
Waste not memory, want not memory — unless it doesn't matter.
From Communications of the ACM
Cherry-Picking and the Scientific Method
Software is supposed be a part of computer science, and science demands proof.
From Communications of the ACM
Swamped By Automation
Whenever someone asks you to trust them, don't.
From Communications of the ACM
Can More Code Mean Fewer Bugs?
The bytes you save today may bite you tomorrow.
From Communications of the ACM
A Nice Piece of Code
Colorful metaphors and properly reusing functions.
From Communications of the ACM
A System Is Not a Product
Stopping to smell the code before wasting time reentering configuration data.
From Communications of the ACM
Scale Failure
Using a tool for the wrong job is OK until the day when it isn't.
From Communications of the ACM
Wanton Acts of Debuggery
Keep your debug messages clear, useful, and not annoying.
From Communications of the ACM
Debugging on Live Systems
It is more of a social than a technical problem.
From Communications of the ACM
File-System Litter
Cleaning up your storage space quickly and efficiently.
From Communications of the ACM
Think Before You Fork
Kode Vicious's thoughts on forking, config files, and using internal wikis.
From Communications of the ACM
Coder's Block
Programming is a creative endeavor, and therefore there is such a thing as coder's block. What does it take to clear the blockage?
From Communications of the ACM