Hi, I'm Tea.
I run Studio Eaden on my own, on purpose: one person who can sit with your problem, design the answer, and build it properly, with no team you never meet in between.
- Based in
- Kansas City, MO
- Working with
- Clients anywhere
- Studied
- Computer science at UMKC, data science at Mizzou
How it started
Serious work, without the pressure.
I found coding through a web development elective in high school. I didn’t know what I wanted to do yet, only that it would be something in STEM, and I was already my parents’ in-house tech support. That class was my first taste of real code, and I liked it enough to study computer science in college.
College was hard. Honestly, it kicked my butt, and it was worth every bit. From there I worked as a software engineering intern, then in programmer roles. The work was good. The environment wasn’t: office politics, rigid process, and whole days where I barely spoke to anyone.
Studio Eaden is my answer to that. I take the work seriously, but good work doesn’t need to be rigid or high-pressure. Working directly with people, one conversation at a time, is how I do my best work, and it’s a lot closer to who I am.
I named it after Eden: a small place tended by hand. That is the whole idea. Software grown for you, tended rather than stamped out.
Education
Missouri-made.
- Master of Science in Data ScienceUniversity of Missouri–Columbia
- Bachelor of Science in Computer ScienceUniversity of Missouri–Kansas City
Outside of work
A few things about me.
Fair warning: I have more hobbies than free time.
- Grew up in
- Liberty, Missouri
- Hands busy with
- Crochet and needlepoint
- In the garage
- Working on my car
- Unwinding with
- A good sudoku
- Favorite KC spot
- Third Street Social
- Always nearby
- A Snoopy trinket, at my desk and at home
How I work
Close, direct, and built to last.
You talk to the maker
No account managers and no junior team you never meet. The person who designs it is the person who builds it and the person who answers your email.
We build it together
I share progress as I go and think out loud, so what ships is the thing you actually wanted, not a surprise at the end.
Serious under the hood
The data discipline I learned on large systems runs quietly underneath, so the surface can stay calm and simple.
Plain language, always
No jargon and no buzzwords. If I can't explain what I'm building in plain words, I don't understand it well enough yet.
If you’re wondering
What if I’m unavailable?
Fair question when you work with one person. Everything I build is in your name from day one, with plain-language docs and a 30-day fix window, so you’re never stuck.
Get in touch
Tell me what you're stuck on.
An idea in your head, a process held together with spreadsheets, a tool that almost works. Send it my way and we'll figure out what to build.