Invisibility can be dangerous. It's best to develop software with plenty of regular visible evidence. Visibility gives confidence that progress is genuine and not an illusion, deliberate and not unintentional, repeatable and not accidental.

Interfaces Easy to Use Correctly and Hard to Use Incorrectly A good way to design interfaces that are easy to use correctly is to exercise them before they exist Making interfaces hard to use incorrectly requires two things. First, you mus…

Typically, there is some immediate problem to solve. It might be internal to the development team, some tooling that fills a gap in the toolchain. It might be external, visible to end users, such as a workaround that addresses missing func…

A linker is a stupid, pedestrian, straightforward program. All it does is concatenate together the code and data sections of the object files, connect the references to symbols with their definitions, pull unresolved symbols out of the lib…

You need to give your project a voice. This can be done by email or instant messaging, informing the developers about the latest decline or improvement in numbers. But it's even more effective to embody the project in your office by using …