We're happy with portion of our work we've selected for presentation at Explore DDD. Now we plot the narrative of the keynote before assembling a final set of slides.
We begin the keynote with this observation of a denver street shot the morning of the talk. Viewed first in still and then in motion, this metaphorically stood for our ability to observe more than first meets the eye.
YOUTUBE heYz8VhnJGA Published on Sep 23, 2017.
About Transformations of our industry, what we carry forward and what we must learn anew.
Roots of Wiki and Patterns in observations of technological and organizational evolution.
Ubiquity and its Bounds as recognized by DDD in section IV's Context Map. Know this to understand the problem. Page 28. pdf
Reorganizing for Autonomy, self-selection and self-service. What could possibly go wrong?
Consistent Metadata as stand-in for Bounded Context. Capturing partially consistent data in a graph database.
Resolving Misalignments by applying and tabulating heuristics. Address mistakes and confusions. QA?
Large, Small and Tiny graphs. Aggregate to large and then query to small. Repeat for tiny. Query as inference.
Secondary Source good for design, incidents, on boarding but not operations. Not a new steward of data.
The Federation Connection as inspiration where decisions are not agreed. A force for good not a wall against bad.
Spawn Queries like wiki pages. Anyone can edit. Slack good queries and renderings.
Hold Queries for downstream applications. Smoketest with each build. Similar approach to upstreams.
Graph to Table to Graph. We add something with each step. Alignment, focus, interpretation.
Search for docs or datatypes. Get pages, answers or application links. A Tertiary application.
Managing Vulnerabilities quietly and privately between teams and security services. Octets to Architects.
Modeling with Complex Types and transformers. Either named as metadata or held on wiki pages.
Bayesian Inquiry where one builds or weakens beliefs through repeated operation of an open-ended interface.