I always wonder what is the best way to remember key things points when I’m design complex systems. I have done mnemonics, mind castles, templates, checklists, flowcharts, you name it. I have found that the best way to remember things is to really understand them and incorporate them into the natural flow of things.
If they are only reference items, then they become things that can be forgotten or excluded. If they become habit, then it is impossible for them to be forgotten even if you tried.
Herein lies the issue, not every fact, interaction and association can be remembered when it comes to design. Many undercurrents can be part of planning, implementation, documentation, training, etc, but not 100% adopted.
Some examples are architectural frameworks or taxonomies, such as TOGAF or the Zachman framework, or ITIL for service management.
These can be very cumbersome to completely use from beginning to end, and many components are not entirely relevant to all environments. So what do you do to ensure that some core tenet are remembered if they are not used all the time?
Well this brings us back to memory and learning. No two people learn in 100% the same fashion, so long term retention of information is a very different beast for each of us.
This fascinates me as I am learning to optimize my own process. People with eidetic memory have the ability to recall images in great detail after only a few minutes of exposure. This is very rare, but some do it by the process of synesthesia, which allows for sounds to be tasted and colours to be associated with numbers, etc.
For those that are not in the 1%, we need to look at other methods of transferring information to long term memory. My current method involves the concept of learning modalities and multiple intelligences. If you understand how you learn, then you can work with your specific intelligence area.
These are the reasons I teach, blog, draw and design. They are not just things I end up doing, but rather they are things I need to do to understand and retain subject material.
So in the spirit of retaining core design tenets, I have decided to create a series of short videos that highlight these in a memorable manner.
By using short dramatic video clips from popular culture, movies and television, I will try to convey these in a way that is relative and fun. They are in no particular order, other than what I am thinking or applying at the time.
I call these “Dramatic Design Quotes”, and I will attempt to make a series of these to help myself and others. Below are the first two I have created.
Dramatic Design Quote #1 – Redundancy.
Here are some redundancy related quotes from the vSphere Design PocketBook
“When working with blades don’t put all you hosts of a single vSphere cluster in one enclosure. You can avoid creating a SPOF and increase redundancy by placing your blades in multiple enclosures.”
– Eelco Kos, @eelcokos VCP
“When using 1Gb Ethernet you should have at least one addition network card to complement the onboard NICs for redundancy and spread teams across them”
– Simon Eady, @simoneady Bristol VMUG Leader
“Model your design after Noah’s Ark, 2 of everything! Redundancy.”
– Bobby Stampfle, @bobbyfantast1c vExpert
Dramatic Design Quote #2 – IT Governance
Here are some governance related quotes from the vSphere Design PocketBook 2.0
“Security & regulations investigations; Depending on the business it is useful investigate security and regulations requirements. This makes sure that the IT infrastructure meets the standards defined by security or regulations defined by local law. “
– Martijn Baecke, VCDX #103 @baecke
“Guests in general should be configured to get their time from AD domain controllers. If not possible then the guests should be configured to use an external NTP source. If this is not practical from a security perspective (exp: you cannot open firewall ports to an external source), then synchronization with host can be an alternative”
– Aylin Sali, vExpert @V4Virtual
For more information on the vSphere Design Pocket Guides from PernixData, click on the links below: