MNEILSWORLD.COM

MNEILSWORLD.COM · HANGING Nº 001 · HTML & CSS ON A CANVAS

MICHAEL NEIL

Software engineer for twenty years. Currently an SVP in Security Engineering at Citi, building the guardrails for agentic AI.

  • Agentic security
  • 20 years, many industries
  • Node · Python · Go
  • Father of two

About the maker

I'm Michael. I've been building software for twenty years across many different industries, which is a polite way of saying I have opinions about everything and scars from most of it.

These days I'm an SVP in Security Engineering at Citi, working on agentic security — the discipline of keeping AI systems that act on our behalf from acting badly. Before that: full-stack web applications, where Node.js, Python and Go are daily drivers; then infrastructure and DevOps on AWS, where automation became both a job and a personality trait.

I care about building things that run themselves, but what I actually enjoy is watching teams level up while they do it. My goal is the moment someone stops asking "how?" and starts teaching their teammates instead.

The world so far

Two decades, five terrains. No résumé-style bullets. Just elevation.

  1. The Flash Plains

    Interactive landscapes in ActionScript on this very domain. A world you could walk through and the reason "the world" is still what this site is about.

  2. The Full-Stack Ranges

    Web applications across many industries. Node.js and Python grew into daily drivers; Go arrived later, on purpose.

  3. The Infrastructure Peaks

    DevOps and AWS at scale. The work shifted from writing features to writing the systems that carry them: pipelines, automation, infrastructure that runs itself.

  4. The Security Highlands

    Infrastructure security in the enterprise. Now as SVP, Security Engineering at Citi.

  5. The Frontier: Agentic Security

    When software starts acting on its own, somebody has to teach it restraint. That's where I spend the days.

Craft

What I reach for, and why it sticks.

The studio

A double major in art and communication left a mark. Three styles I keep returning to — each one maps onto how I build software.

Surrealism — if it can't be built, sketch it anyway. Requirements are dreams first; physics is a later draft.
Impressionism — systems are mostly motion. Capture the mood of change, not every pixel at rest.
B·7
Brutalism — show the structure. If the concrete is load-bearing, let people see it.

Say hello

The fastest way to reach me is LinkedIn. If you're building with agents and want another set of eyes on your blast radius, that's the inbox for it.

Open my LinkedIn ↗

No JavaScript runs on this site. No trackers. Just HTML, CSS, and one very large sun.