Living where design and code meet, since the very beginning.
From the very start, I've always had an interest in making the things I design work. I began in Flash and taught myself how to make websites from there. The feeling of being able to design anything I wanted and bring it to life was the fuel that kept me going. And still is! The number of side projects I have is mind-boggling. Ask me about my family dashboard to help manage my family schedules and chores.
Eventually, after working for a small startup out of college, I learned how to create custom WordPress themes and ended up with my own small design/dev studio, which I've run since 2013. I had one employee for six of those years. We made many, many custom WordPress websites for all kinds of industries, for everyone from Fortune 200 companies like Union Pacific to a local landscaping mom-and-pop shop. I led teams of various sizes and capabilities to create all kinds of websites, often on WordPress.
As time went on, my role and company transitioned to just me, working more closely and integrated with various teams. My best work has come from long relationships, not one-off projects. Lately, I've worked closely with teams ranging from large international non-profits to fintech startups.
I enjoy solving problems and creating systems that can support teams in the long run. With AI, that work has sped up exponentially.
I also spent about five years mentoring hundreds of career-changers learning front-end development. It taught me the job was never really teaching code. It was teaching people to problem-solve, and to believe they could. Bringing along less-experienced people is something I do on purpose, and it shapes how I build things other people have to run.
Who I work best with
What matters most to me is the kind of problem. The work I do best tends to be:
-
Teams establishing design for the first time, still figuring out what good looks like.
-
Teams modernizing a product that's outgrown its original design.
-
Teams with a stalled or half-built project that needs someone to take it over and ship it.
-
Teams who want a system they can actually own and run after I've handed it off.
What I work with
The tools and practices I reach for most, across design and build.
-
Design
Figma, design systems and component libraries, UX research and usability testing.
-
Build
HTML, CSS, and some React, Tailwind, Storybook, and Git.
-
Systems & AI
Design-to-code workflows and AI-assisted build pipelines (Claude Code, the Figma MCP).
Things that interest me
I'm a tinkerer. If I'm not building something for work, I'm usually building something at home. There's always a side project going.
-
My Raspberry Pi home hub
In progress, but a little local network where my husband and I can pull up info, run our home automation, and maybe someday a family memory box.
-
A family dashboard
I'm designing and coding it with my 8-year-old, who runs product and has very strong opinions.
Read about it -
Cooking
With a little Instagram account I update for fun when the mood strikes.
Check it out -
Reading
A borderline unreasonable amount of romantasy. My TBR list is ever growing.
Work Notes
Occasional write-ups on what I'm learning as I build.
-
October 2026
We prototyped fast. We learned faster.
A fleet owner liked the redesign. Then he pulled out his phone and showed us the WhatsApp group his drivers actually use instead.
Read the full article -
September 2026
Our Figma prototype couldn't keep up
Figma prototypes used to be the best option we had. Then Claude made it fast to spin up a coded one that actually behaves like the app.
Read the full article -
September 2026
I give my AI bots job descriptions
When I cleaned up our design file this spring, I didn't use one AI. I used a small team of them, and each had a list of things it wasn't allowed to do.
Read the full article