On building companies, engineering, and what the work looks like now that code is cheap. I write a lot. Here's some of it, in case it helps you find solid ground. Some of these were written for a brand I was building or working for. Those are tagged, and open on that site in a new tab.
WVU Online's story about my master's and where it went. Chad Mezera and Derek Brewer wrote it. I'm in it, and so is Cash, on the PRT.
Your aura isn't inside you. It's the light you hand other people to read you by.
I embraced it, built my half (the data) and got out of the way. Two planes, two authors, and the labor in between.
We batched software into releases because shipping was expensive. It isn't anymore. Now batching is the risk.
If you can write a memo to a new hire, you can write software. Most teams still can't write the memo.
For decades we priced software by the engineering. The expensive part was always the explaining.
The first build turned nearly everyone red. Chasing the bug, we rediscovered color constancy.
We published the math behind the aura read (white balance, chromatic adaptation, a continuous hue read) running live, sliders and all. The edge was never the algorithm.
If you refract twice and get two different bands, congrats, you're alive. On why the read changes, and why that's the point.
A short, honest piece about what aura.refract is and what it isn't. Because someone always asks.
I've never actually had my aura read. I only ever saw the pictures, in cities I wasn't in. That gap is the whole reason aura.refract exists.
Forty people a night, 250 nights a year, and a browser has no cap. Why the next two years of aura photography won't look like the last two.
On July 1 I move from full-time CTO of Ledger Collective into a board and advisory seat. Not a goodbye, just me going back to what I'm built for.
My sleep schedule got wrecked. Not because anything was wrong, because everything was right. On building systems that run while you rest.
Before this site I wrote for Flatfile (2021 to 2023, as Engineer and Head of Product Marketing) and on LinkedIn (2024, as Ashley Mulligan). Articles, launches, and the films I'm in, with their original dates, linked where they live. Flatfile is now Obvious.
Pair programming with Nate in the first year of building with AI. The headaches, and the line he kept saying: "Ash, time is no longer linear."
The years I softened my southern accent and left the small-town work off my résumé. Now it's the part I'm proudest of.
After we relaunched the developer APIs, I rebuilt the docs on Mintlify. Their write-up of the project, and a walkthrough.
A short film on what it costs a business to keep onboarding customer data by hand. That's me on camera.
The film that introduced the category. Written and presented by me.
You land the huge customer. Then their data shows up, and it is filthy. The stretch between the handshake and the go-live.
Federated data sounds great until you ask who gets access, and how. On security and shared data.
Data sitting in a database earns nothing. It has to move. Retail, healthcare, and the case for exchange.
Written in the 2022 downturn. What slow data onboarding costs in delayed go-lives and lost clients.
The $50M announcement, the film that went with it, and my own post from that morning. I wrote the copy for all three.
The platform launch I wrote and ran as Head of Developer Experience.
The rebrand and the new site, done in house. This is the launch film.
Every company's database has its own structure. What that costs the moment two of them have to share.
The story of one of the first Flatfile Impact grantees, a nonprofit tracking wildlife with data from the public.
The webinar I co-hosted with Eric Crane on scaling data onboarding for dev teams. On YouTube.
A free version of the product I relaunched. Paste a CSV, get JSON. It's still running.