About Me

So I've never really figured out how to sum myself up on the internet without sounding like a LinkedIn profile or a dating app bio.

Here's the honest version. My name is William Karavites. My official title is Team Lead for Agentic/MCP Development AI Enablement at Lockheed Martin, which is a great sentence for a business card and a pretty incomplete description of what I actually do all day (that's its own post, honestly).

Short version: I design infrastructure and write code and spend an unreasonable amount of time trying to get a dozen different teams to build their MCP servers the same way instead of eleven slightly different ways. If you've ever debugged a distributed system at three in the morning you already know the exact blend of frustration and stubborn curiosity that got me here.

Before that I taught "Intro to Computer Concepts" at Rutgers. Teaching beginners is a great reality check. If you can't explain something simply you don't actually understand it, you've just memorized it well enough to bluff. That's also why I write like I talk, sometimes rambling all over, lots of ideas and excitement, random deep-dives (nope, I definitely don't have ADD...)

This isn't a resume though. Thank god! It'd be a boring read. This is more of a home base for whatever's actually taking up space in my head and that's a weirder list than the job title suggests.

It's also where the name of this place comes from. I've got a habit of working at both ends of the zoom lens at once. Some days it's macro: stepping back and looking at a garden or a piece of software architecture or (sure, fine) life itself as one whole system. Other days it's micro: one weed, one function, one bad assumption three layers down that's quietly ruining everything built on top of it.

I don't really separate "big thought" from "small task" the way most people seem to. Pull a weed long enough and you're thinking about soil biology. Fix one function long enough and you're rethinking the whole architecture. Same lens really, just pointed somewhere else that day.

The garden's a good example. First thing it taught me: you can't just throw seeds at the ground and hope for the best (learned that one the hard way, RIP to an entire flat of seedlings).

Soil isn't a surface, it's alive. Bacteria and fungus doing the actual work of getting nutrients to roots. It needs to breathe or none of it moves. It needs to be fed with anything from cover crops to straight up chicken-shit fertilizer (not a euphemism, an actual ingredient, deal with it). Depending on what you're starting with that's either a light top-up or a full year of conditioning before you plant a single thing. Get the foundation right before you build on it. It's basically software architecture, minus the git conflicts, plus actual bugs.

Outside of that I'm in a D&D campaign with a group of friends and it's been a lot of fun, once I finally figured out how to actually play my character. That took embarrassingly long and is honestly still ongoing.

I also volunteer at my local fire company, which on any given week is either the most useful or the most questionable thing I do with a weeknight.

This site's where all of it lives. I'm not building a portfolio or curating a highlight reel here. It's just somewhere to write about what I'm building and what's going wrong with it and whatever else is rattling around up there while I do.

Say hello if you want, I'm on GitHub or you can email [email protected].