Productive Programming

I've had a few questions about the Productive Programming Book, here are a few of the pearls I got from it:

SLAP

all code in a method live at the same level of abstraction. Nice acronym.

Aristotles Essential and Accidental Properties

Notions of Accidental Complexity have been around for a lot longer than I thought.

Dietzlers Law - 80-10-10 (classic)

you can do 80 percent of what the customer wants in a remarkably short time. The next 10 percent is possible, but takes a lot of effort. The last 10 percent is flat out impossible because you can't get "underneath" all the tooling and frameworks. And users want 100 percent of what they want, so 4GLs gave way to general-purpose languages (Visual BASIC, Java, Delphi, and eventually C#). Java and C# in particular were designed to make C++ easier and less error prone, so the developers built-in some fairly serious restrictions in the interest of keeping average developers out of trouble. They created their own versions of the "80-10-10 Rule," only this time the stuff you couldn't do was much more subtle.

• Productive Programmer

Tweet This Post