Important
If you’re looking for the professional version, check out my LinkedIn. This? This is my fun space. 🫶
Backend engineer by trade. AI Champion 🦾 and Occasional Doctor 🩺 — I’ll patch Copilot up just so I can break it again two minutes later.
There was madness in any direction… A fantastic universal sense that whatever we were doing was right… Our energy would simply prevail… We had all the momentum… We were riding the crest of a high and beautiful wave… And in a very real sense, the tendency is to push it as far as you can.
— Hunter S. Thompson
The people who push boundaries, set examples, break systems and rebuild them better — those are the ones who make a real difference. That’s the lane I choose to live in.
Not just to be "good", but to make everyone around me an expert in the process. And if that means I have to break it a million times before I figure it out, then so be it. There’s a method to my madness — and in the chaos, there’s always something beautiful waiting to emerge. 🌪️🦄
Senior Software Developer @ The Home Depot. I sit happily at “the second seat” — someone else shoulders the heavy work and nonstop meetings (well… more than mine anyway) while I get to make the fun calls:
- Starting conventional commits ✅
- Wiring repos with linters that break builds ✅
- Updating Slack workflows so PRs without CODEOWNERS get auto-rejected ✅
- 🤫 that's a surprise. But in my defense, I did say it was going to happen about 10 times already.
It’s not about being mean (well… not just that, but after ~10 years in the industry, we deserve a little 🤏 leeway for scaring best practices out of people. In all the best ways, of course!) — it’s about excellence.
Do I honestly care if you put commas at the end of every single line in Node files? Nope. Sprinkle them in like confetti if it makes you happy. 🎉 What I don’t want is a pull request diff filled with meaningless noise because somebody stripped them out — only for the next person to add them back in with no rhyme or reason besides “that’s how I like it.”
AI tracking every commit. No more format wars. No more diff fights. Linters to the rescue. 🌪️🔥
These are the projects that escaped work — half-banned experiments, dev rants turned into code, and the occasional side quest that somehow worked:
- CheckMarK ⚡ – hack-time junk drawer: Copilot mischief, repo workflows, anything and everything else that didn’t fit elsewhere.
- Underfoot Underground Travel Planner — This started as a hackathon project, but it's evolving into a full-fledged tool. Read all about its origin in my submission post on Dev.
- RAI-Lint 🤖⚖️ – Because AI should follow the rules too. Linting for Responsible AI practices: bias detection, fairness checks, and ethical guardrails baked right into your CI/CD pipeline. If your model can't pass the vibe check, it doesn't ship. I started a Dev blog on this topic and then quickly got sidetracked with implementation.
- My Hermetic Agent 🔮⚡ – A small but dangerous playground for Hermes-4-14B: hybrid reasoning, tool use, dual memory, and zero guardrails. It’s just me seeing what happens when you give a capable model too much freedom and a TimescaleDB to remember its crimes.
- NPM JS Template (aka Lint Lockdown) – the “friendly” tool that makes sure you can’t escape conventional commits or proper formatting.
- Awesome GitHub Copilot – custom instructions, prompts and chat modes for GitHub Copilot, each with its own personality.
If it didn’t make it through the front door 🚪 at work, it probably landed here.
I blog weekly on DevTO ☕ — equal parts chaos, caffeine, and “didn’t think that through, but it worked anyway.”
🦄 I know this complains because everything that would count as a contribution is locked away in a different user. I'm going to work on that, but in the meantime it's not a terrible score, considering the zereos. Although, I am not happy it gave me a junior score. Gonna fix that, too! 🤪