I write software, and I'm a licensed cosmetologist in Georgia. I'm still behind the chair every week — the license was meant to be a career change, but after working a salon floor I got obsessed with fixing the software I was fighting there every day. So I'm building it.
Seven years professional, most of them inside a mortgage lender's legacy codebase: the kind of system where an outage costs real money and a compliance mistake costs more. I came up on C# and .NET; these days I prefer Node and React.
That's the thread through the four packages pinned below. Each one guards a failure that is silent and expensive — a marketing text that goes out an hour too early in the recipient's timezone, a webhook that rejects real traffic because a proxy rewrote the URL Twilio signed, a cron job that fires in all three replicas and charges the card three times, a ZIP parser confident enough to turn a date into coordinates in Washington DC. They came out of a production system and were general enough to release on their own.
The other two pins are a debugging tool and my personal site. vscode-memory-watch came from
answering "which of these 38 processes is eating 20 GB?" with a measurement instead of a guess.
Under 1% of my commits are public, and that isn't going to change — so the contribution graph is a poor proxy for the work. Those four packages are a better one: all on npm, three with no dependencies at all, each with a real test suite and CI across Node 18 through 24.
Building with — Node · React · TypeScript · PostgreSQL · Docker · AWS · PWAs Kept alive — iSeries/AS400 · ColdFusion · SQL Credentials — Licensed cosmetologist (GA) · AWS Certified Developer · AI/ML, UT Austin · BS MIS, Alabama '19
More at drewthomasbuilds.com, and the salon platform I'm building is elovarra.com.
Off the clock: a homelab of ARM and x86 boxes running containers, a NAS, and a long habit of putting custom ROMs on phones that didn't ask for them.