Skip to content
View waghmaredb's full-sized avatar

Block or report waghmaredb

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
waghmaredb/README.md

Deepak Waghmare

CTO, Asia Pacific Japan & Greater China — Dell Technologies
Singapore · I write about where enterprise technology meets its consequences — and I build to test the argument.

Writing · LinkedIn · X · vExpose Blog


Most technology strategy is written for the moment it's adopted. I'm more interested in the moment it's tested — when the pilot has to reach production, when the architecture has to survive the outage, when the compute bill lands on the board's desk. That's where technology stops being a roadmap and becomes a consequence.

That's what I write about at deepakwaghmare.com: organizational resilience and what a company discovers is actually load-bearing only in a crisis; the economics of compute, where efficiency is quietly overtaking raw capability as the real constraint; and technology sovereignty as a category rather than a slogan. Across the whole enterprise stack — infrastructure, data, and AI — not one fashionable layer of it. Two books are in progress along those lines: The Token Trap and The Load-Bearing Core.

This GitHub is the workbench behind the writing — benchmarks, reference builds, and the code I use to check an argument before I make it in public. I've never trusted a claim I couldn't run.

What lives here

  • vexpose-labs — the working code behind vExpose: benchmarks, reference architectures, and the scripts I use to check my own numbers before publishing.
  • Infrastructure-as-code reference builds — Kubernetes, OpenShift on bare metal, and storage automation from years spent closer to the metal. Kept public because someone always needs a working example.

What I work across

Enterprise infrastructure & storage · Data platforms · The economics of compute · Cyber-resilience · Technology sovereignty · AI in production · Kubernetes / OpenShift

Beyond the code

Most of my public energy goes to the ideas, not the repos — keynotes and panels across the region, a newsletter for CIOs and boards, and the two books above. The best of it lives at deepakwaghmare.com.

If you're working where technology meets the business — the economics, the resilience, the part that has to hold when everything runs on it — that's the conversation I'm always up for.

Pinned Loading

  1. ansible-k8s ansible-k8s Public

    Automated Kubernetes cluster deployment on CentOS with Ansible, targeting vSphere/VMware environments.

    3 3

  2. Dellemc-storage-RESTAPI Dellemc-storage-RESTAPI Public

    Postman collections for automating Dell EMC storage REST APIs — PowerMax, Unity, XtremIO, and VxFlex.

    1

  3. redhat-ocp-dell-baremetal redhat-ocp-dell-baremetal Public

    Reference configuration for deploying Red Hat OpenShift on Dell PowerEdge bare metal with PowerStore storage (UPI).

  4. vexpose-labs vexpose-labs Public

    Benchmarks, reference architectures, and runnable code behind my writing — the "prove it in code" half of vExpose.blog.

    Python

  5. inference-economics inference-economics Public

    Transparent calculator for the real cost of serving LLM tokens — tokens per watt, $ per million, cloud price vs energy floor.

    Python