Rules of Abstraction

Martin Thompson on Designing for Performance, presented at a talk two months ago in Stockholm. Martin made the case for having a representative model, a domain model that is fit with the purpose in mind.

On the topic, Martin presented the Rules of Abstrations:

  1. Don’t use Abstraction

2. Don’t use Abstraction.

3. Only consider abstraction when you see at least 3 things that ARE the abstraction.

4. Abstractions must pay for themselves.

5. Beware DRY, the evil siren that tricks you into abstraction => Coupling.

 

Rickard Schoultz
I work at Digital River World Payments at the Principal Architect, but all views are my own. I write about technologies related to payments, security, network infrastructure and information management.