Vibe coding · AI pair programming · shipping ideas into working software

I use AI as a real coding partner: brainstorming the product shape, turning vague ideas into specs, building fast prototypes, debugging stubborn issues, and polishing the parts that make software feel usable.

My favorite work starts with a sentence like "what if this could just work?" and ends with a tool that actually runs, explains itself, and saves time.

Vibe -> Spec      turn loose ideas into clear product direction
Spec -> Working   build the smallest useful version quickly
Working -> Better test, refactor, document, and make it pleasant to use
Better -> Habit   keep improving the workflow until shipping feels natural

• Small tools that remove repetitive work.
• Internal systems that make information easier to notice and act on.
• Automation flows that connect data, decisions, and notifications.
• AI-assisted development workflows for faster iteration and cleaner delivery.

• Start from the user's real workflow, not a technology checklist.
• Let AI accelerate exploration, implementation, testing, and review.
• Keep the public surface simple; keep sensitive project details private.
• Prefer useful, running software over impressive but unfinished demos.
• Write enough docs and logs that tomorrow-me can still understand today-me.

Most of my current projects are private, so this profile intentionally avoids internal project names, repository links, data sources, and deployment details.

Vibe coding is not skipping engineering. It is using better leverage to get to better engineering faster.