Work

A curated case library, not a project dump

First: three flagship case studies. Below: experiments and one-off product work—still real constraints, with less narrative around them. Prefer depth over list length.

Flagship work

The same case studies you see on the home page—narrated as problem, solution, architecture, tradeoff, and outcome. One story per product.

Turnox product screenshot
Turnox — live site

SaaS · booking

Turnox

Problem · Service businesses need reliable scheduling without a heavy enterprise stack. The product had to feel instant on mobile and stay operable on flaky networks.

Solution · A focused client-and-admin flow for appointments, with a frontend tuned for quick first paint and predictable state after navigation.

Architecture

Separation of public booking and authenticated views, with shared design primitives so UX stays consistent as features ship.

Tradeoffs

Favored convention and speed of iteration over a maximal component library, while keeping routes and data boundaries clear for future growth.

Outcomes

Operators onboard in minutes. The surface area stays small on purpose, which keeps maintenance cost predictable as usage scales.

Wanna Work product screenshot
Wanna Work — live site

Productivity · documents

Wanna Work

Problem · Resume builders often ship generic templates; users need confidence that what they see is what recruiters see, and fast time-to-export.

Solution · Template system with a strong default visual hierarchy, optimized asset loading so the editor remains responsive on average hardware.

Architecture

Content and presentation are structured so new templates do not require forked logic; export paths stay stable as layouts evolve.

Tradeoffs

Chose a thinner animation layer in favor of consistent layout and print-friendly output, which is where the product’s credibility lives.

Outcomes

Users can go from sign-up to a presentable document quickly, with fewer support edge cases from layout breakage across viewports.

Blabi product screenshot
Blabi — live site

Platform · no-code web

Blabi

Problem · Non-technical users need a site that feels custom without a full agency engagement. Page weight and clarity matter as much as templates.

Solution · A generator-led experience that keeps pages lean and enforces a coherent structure so sites stay performant and accessible by default.

Architecture

Treating pages as composable blocks with shared head metadata patterns, so SEO and social previews stay correct as users iterate.

Tradeoffs

Narrower layout freedom than a raw CMS, in exchange for fewer performance cliffs and a more supportable long tail of customers.

Outcomes

Faster paths from idea to published site, with frontends that remain easy to reason about as the product adds vertical-specific flows.

Experiments and labs

Smaller surfaces, spikes, and client work—useful to show range without pretending they all have the same depth as the featured row.

¿Qué puedo ver?

A discovery surface for series and film recommendations—opinionated UX, fast browse paths.

Stack · NextJs · NodeJs · SASS · TypeScript

Lighthouse reports
Download desktop reportDownload Mobile report

Mac Bash Aliases

Developer-ergonomics site: a friendly layer on top of shell config—clarity over cleverness.

Stack · Astro · Javascript · Tailwindcss

Calierno & Schumacher

A credibility-first landing: typography, contact paths, and trust over novelty.

Stack · Astro · JavaScript · Tailwindcss · TypeScript

Hiring Jr

A lightweight marketplace connecting local companies and junior talent—intentionally simple, human-readable flows.

Stack · NextJs · NodeJs · SASS · Google Sheets

GitHub profile