Sign in

What this course is

Suggest an edit

This course teaches design principles with plain examples from software, databases, networks, operating systems, and everyday physical systems. There is nothing to install, and you need no blockchain background.

What each module teaches

  • Design tradeoffs. An option is better only for a goal, so name the goal before you compare options.
  • Constraint bypass. Check whether a constraint belongs to the result you need or only to one way of reaching it.
  • Relevance and genericity. Constrain only the properties the result depends on.
  • Core and periphery. Keep the valuable state in a small part that rarely changes, and keep the code that changes often away from it.
  • Singleton and factory. Put a critical function in one shared component, so the review effort concentrates on it. Derive the identifier of each created instance from its content, so anyone can check it.
  • Atomicity as guarantor. Steps that complete as one unit or leave no trace can replace trust between two parties.
  • Standardization patterns. One shared interface replaces a private agreement between every pair of participants.
  • Stateless design. A component that keeps nothing between calls holds nothing an attacker can reach.
  • Goal hierarchy. Trace each design choice up to the goal it serves, and drop it when it stops serving that goal.
  • Adversarial thinking. Design as if one user is fully informed and looking for a way to take value they are not owed.

None of this depends on a particular language or platform. Some lessons close with an optional section headed Blockchain application, which shows how the principle appears in a blockchain system. Those sections are there for readers heading into the security-focused courses.