Recently I've had two prompts to look at some form of monetization. I've had multiple colleagues say I should charge for small pieces of work way outside of my normal wheelhouse, and some discussion about how to support old products that are out of maintenance by their original Organizations.

Excluding VIC, all my truly valuable work has been closed source. This has been a useful prompt to look at changing that for projects where I have the agency to do so.

Vague future goals

My interests, hopefully guiding future project work, relate to expression, capture and use of distilled intent in code, orchestration, etc, to enable much more flexibility in how the intent is realized than with our current expressions, which tend to "how" or at best a low level "what".

I've hopes to take some of the concepts from intent expression to translate into interesting project planning tools.

Background

I moved from IBM in the UK, to VMware in San Francisco back in 2012, with a brief stint of self-funded R&D in the middle focusing on AR and subliminal information processing.

In VMware I've been worked on integrating introspection and management of workloads into vSphere since 2012, from exposing JVM heaps to VM balloon pressure, to elastic scaling of BigData workloads, with a truly alarming number of years getting containers to be 1st party vSphere workloads: Bonneville → VIC → WCP → Keswick/VECO and some related availability logic down at the ESXi level.

Why Sponsorship

It's of interest to me for a couple of reasons:

1. allows indication of serious interest from, and utility to, the sponsor (focus)
2. compensation for time sunk in projects that have broad utility to a wider audience, where small individual amounts can add up to a useful amount (monetization)