I'm Graeme. I build infrastructure at scale. I've been doing it my entire career. I spent a good part of my early thirties working for a major retailer in the north of England, doing my best to help St Nick as the resource they flew onsite for 3 months to make sure the supply chain wasn't disrupted for Christmas. Along the way I helped that same retailer skip the line for their internal online platform for their entire entertainment product range, with a custom Order Management Solution providing data-driven workflows for pricing, supply and order cascades. That project earned our little company an apartment in Westminster, an office in SW1 on the south bank, and the entire front-end development team that built the site. I've always felt it best to over deliver.
Then I spent a while applying what I'd learned on that job - how to get down on the floor and listen to the people using your tools, how to watch how they're used, how to make them better - and started to build my own platforms. First, still with a supply chain focus, I built a data-driven platform and the components of the standard Order to Cash and Purchase to Payment cycles on top of it. This was part of a used-media buyback venture that grew to around 100 employees on two continents.
Since then it's been software. I spent a decade at one of the world's largest information-content and technology providers building out their development platform one Jira ticket at a time. What started over a decade ago as a chain of 5 Jenkins jobs that built a JAR and deployed it as an AMI through CloudFormation became a platform that deployed nearly everything the company produced.
When the company using that platform was swallowed in a $5bn acquisition, our products remained on our platform. When I was invited to be the representative of our business unit on a corporate-wide project to standardize pipelines, we were excluded from the proceedings after they compared the scope of their goals to what our platform already provided.
Since that opportunity concluded, I've been building. What else are you going to do? It's a system based on the idea that if we can compress the surface of an idea and its execution to the minimal form, the chance for either to drift is minimized. In practice, this means executable markdown where presentation, data, and the code to generate both can live in the same document. Data as streams, a causally organized datastore to hold it, and a simple JSON-RPC based bridge to the outside world combine to create Wanderland - a simple to use, lightweight to run surface for creation. What it becomes is whatever you can think of. The portfolio is just a few of my whatevers.
Enjoy.
e: i.am[at]graemefawcett.ca
b: https://bsky.app/profile/graeme.fawcett.social
l: https://www.linkedin.com/in/graeme-fawcett-5b183119
p: dig +short AAAA tao.loss.dev
Be in touch