Joe Freeman: Tech, Teams, Trade-offs

This is another example of the known/unknown vs knowns/unknowns  quadrant mapping.  The last example was muddled.  These simple medical and house-building examples should help make this mouthful more relatable. Watch the video down below that uses this content!  This page was created to support the video and will have text content at some time in the future. The 4 quadrants of knowing and unknowing Content to be added on the 4 quadrants. Driving our constraints into the Known/Knowns quadrant <to be edited> Video and other content Try at this  Surfacing things we know nothing about YouTube Video   Surfacing things we know nothing about... blog article Video for this  2nd attempt and the 4 quadrants of Knowing This blog article  4 quadrants of knowing blog article Medical Example <medical example to be written up> Home Building Example <text for later> Video Revision History Created: 2023 01

 Software developers think of the lifetime of data or objects within the confines of the language or frameworks they are using.  They need to think of data lifespan or scope as a first class component of design. Business and business process data is valid for some period of time.  It has a lifetime, scope, that may vary based on business rules, transaction time or some other function.  Technical or software transaction data is also scoped, valid for some period of time. This talk focuses on how these lifetimes can be more naturally integrated into a running software system. Lifespan Every business entity, attribute or property is valid for some period of time. It may be the lifespan of a project, a contract period , the length of time someone is a customer.   Transient copies of the data or newly created business entities may be valid for the life of some user session or only while some transaction operation is active.  This means...