Designer + Developer

No longer just handing off specs.

Actively contributing to production codebases: installing dev dependencies, writing real code, and merging PRs with hundreds of lines changed. The lines between design and development are thinning.

Git + GitHub Prod-Ready Code Dev Dependencies Merged PRs Released Features
Contributions (3 months)
16 and growing
Lines changed
+759 / -124
Files changed
36 files
Started
Recently, 2026
GitHub contribution graph
Status
Merged
PR into master, 3 commits
Files changed
36
Across layouts, components, styles
Lines added
+759
Prod-ready, reviewed, shipped
Contributions
16
In just 3 months, ramping up
Recent Work

First Merged Pull Request

Real code. Real review. Real release. This PR touched 36 files, added 759 lines, and shipped to production.

Merged pull request: feat: update create page
Pull Request
Merged
feat: update create page

Updated the Create Decision page end to end: two-column card layout with full-width rows and a delete icon, updated typography grid, two-state driver section cards with selected state and NEWBETA badges, driver section label alignment fixes, and solid purple primary/tertiary buttons built via CreateV2ActionButtons styles.

36 files changed Layouts, components, and styles updated across the board
+759  -124 Net additions merged into master
Reviewed and approved Passed compliance checks, code review, and release gate
Released to production Tagged and live, not just a prototype
GitHub Activity

16 Contributions. 3 Months. Just Getting Started.

The graph is young because the journey is new. Started in early 2026 and already shipping consistently into production.

GitHub contribution graph showing 16 contributions in 3 months
GitHub Contribution Graph
16 contributions in just 3 months. Activity picks up sharply from March 2026 onward. The lines between design and development are thinning with every commit.
The Shift

What This Actually Changes

When a designer can also push code, the whole team moves faster. The lines between design and development thin with every PR.

No More Handoff Gap

Writing code directly means designs are built exactly as intended. No translation layer, no "this can't be done in dev" back-and-forth.

Real Dev Setup

Installing dev dependencies, running local builds, reading error logs. The full engineering environment, not just a Figma file handed over Slack.

Code That Gets Reviewed

PRs go through the same review process as any engineer. Compliance checks, code review, approval, release gate. No shortcuts.

Faster Iteration

Spotting a spacing issue or a broken state? Fix it directly in the branch instead of filing a ticket and waiting. Iteration velocity goes up immediately.

Better Engineering Conversations

Understanding the codebase means design decisions are grounded in what's actually feasible. No more guessing what's expensive to build.

Shipped, Not Just Specced

The work doesn't stop at handoff. It ships to production, gets tagged in a release, and goes live for real users. That's the standard now.

Designer. Developer. Both.

This is just the beginning. If you want someone who can own the full stack from research to release, let's talk.

Get in Touch Back to AI Work