Worse is Better Design Rules

The Worse is Better design rules:

• Prefer Simplicity over everything else.
• Sacrifice Correctness for Simplicity.
• Sacrifice Completeness for Consistency.
• Sacrifice Completeness for Simplicity.
• Sacrifice Consistency for Completeness if Simplicity can be retained.

Invisible Design

Ironically, invisible design in UX requires adding constraints while in programming it requires removing them to find abstractions.

The problem with ugly, large and slow code

Bjarne Stroustrup in Masterminds of Programming:

"Ugly" leaves places for bugs to hide, "large" ensures incomplete testing, and "slow" encourages the use of shortcuts and dirty tricks...

Procedural Programming is NOT a Bad Thing!

For way too long now, I've heard proponents of object-oriented programming describe badly written programs as "procedural", as if to imply that procedural programming is a Bad Thing.

Good design is possible using any programming paradigm, just as bad design is. Stop using procedural programming as a derogatory term!

I personally prefer multi-paradigm programming, so that I can use the paradigm that feels right for the job at hand.