The Rules of Three

Hardly anything is unique. A few things are, but most are not. When you know which parts you’ve seen before, you can spend your time where it will make the most difference.

Any component can be broken down into three parts – know them and cut your workload in half. Using the Rules of Three will help you recognize patterns, recognize uniqueness, and work on what matters.

1) Systems - the base level

Interacting with external entities - Your native API or your site-wide EMR.

The thing you always need to talk to.

2) Processes - the middle level

Functions that do things - Logic, mappings, networking, and rules used in many places. When you see yourself creating rules or logic thats used multiple times - create a library. Copying and pasting is natures way of telling you to create a library.

3) The Snowflake - the top level

These are the specific mappings and transformations - The “snowflake.” The tiny part of an interface that is like no other. Learn to spot the “snowflake”: this is the reason you’re building a new interface.

Keeping the snowflake as small as possible is the key.

Now how do you organically write code so that it follows this three part pyramid structure? Follow our three interface development best practices.