Crema
№ 01A design system and component library serving twelve product teams — tokens, primitives, and docs that made "consistent" the default instead of the exception.
I design and build web applications the way a good bar pulls espresso — measured, repeatable, and never rushed. Databases to interfaces, every layer gets the same attention.
Pick a method. Each one is a different way I work the stack — dialed in over six years of daily service.
Interfaces are espresso: short extraction, zero room to hide flaws. I build component systems that render fast, read clearly, and hold up under a designer's squint — accessible by default, not by audit.
APIs are pour-overs: the quality is decided by the setup. I design services with clean contracts, honest error handling, and docs the next developer thanks you for — REST or GraphQL, whatever the cup calls for.
Databases and infrastructure reward patience. I model schemas that survive pivots, tune the queries everyone else gave up on, and wire deploys that are boring in the best possible way.
Every great café weighs its shots. I treat tests and tooling the same way — coverage where it counts, e2e flows for the money paths, and DX tooling so the whole team pours faster.
I write code like a recipe card: someone else should be able to make the same cup without calling me. Clear names, small functions, and the occasional strong opinion about tea.
I'm Jess — a full-stack developer who believes software and coffee fail the same way: rushing the process, skipping the measurements, and serving it before it's ready. So I don't. I've spent three years building for startups and product teams, and I still get excited when a query plan comes back clean.
Jess is the engineer you hand the messy, load-bearing problem to — and get back something simple enough that everyone claims it was obvious all along.
Whether it's a greenfield build, a rescue mission, or a team that needs another pair of steady hands — the bar is open. First consult is on the house.
or write directly: [email protected]