Wardley Maps

Somewhere in 2016 I stumbled upon a conference video presented by a person named Simon Wardley ( @swardley ) hence the name Wardley mapping. He was telling the story of “crossing the river by feeling the stones” and it was fascinating to witness how this method of creating maps communicated so much understanding. That is even without fully understanding the capabilities you unlock with them.

Origins

The reason I bumped into the video is because I’ve been looking into the “OODA loop” famously formulated by John Boyd. In the world of DevOps this is also one of the ways we can iterate, learn and take deliberate action. Wardley mapping includes this concept but mixes it with a few other things, among which Sun Tzu “The art of War” in what I can only describe as great insight by Simon who fused this coherently together.

My lungs hurt so frkn! bad!

Over the past two years I’ve been struggling to regain strength in my lungs due to the long term effects of a possible COVID infection somewhere early 2020. I say possible, because back then you couldn’t get tested yet, so I don’t know for sure. Symptoms have been acute shortness of breath, increased allergy sensitivity, enduring inflammation of the bronchi and a strongly reduced VO2 Max. So for example, whenever I tried to pick up the pace during training it would hurt or I just couldn’t get the necessary amount of oxygen into my body. When the seasons changed to Winter-ish this got progressively worse. That sucked!

What led to this

Over the past year or so I’ve been working in an environment where an instance of API Management in an internal network configuration was about to run into scalability issue. This is with regards to the number of workloads connecting to it using VNET-peering. Peering is the preferred method to reduce latency between workloads in different networks in the same region, but has a maximum of 500 peering’s. This is one of the hard limits in Azure see networking limits.