Funding Finder
Designing trust into a faster private lending application.
Explore · card direction
One card, one drawing. Each entry gets a thin line object on a pale plate, all pushed through the same 2:1 isometric projection so they read as one hand. The symptom checker is the first entry drawn for itself: a phone whose screen carries a body and two answer rows. Every other entry still takes a generic phone, window, or block in rotation until its own scene is drawn. Stacked ghost copies sit under each object and spread a few pixels on hover while the badge lifts off the top edge. The name is set right, the sentence left under it, both held to the right half of the card.
Designing trust into a faster private lending application.
Under NDA. Password protected, shown in interview.
Making certification workflows and delivery status easier to read.
Reframing a clinical path so people could finish it with confidence and reach the right care.
Helping research and faculty teams get ERA submissions ready sooner.
An AI speech analytics tool that helps call centre QA teams monitor compliance across inbound and outbound calls.
Two iPad apps to replace BHP's paper work instructions for mining workers.
A working MVP of the BRDT portal, built with Kiro at a hackathon hosted by Amazon.
I kept rebuilding the same AI chat screens for every client, so I built them once: a set of ready made, animated chat components that a designer can brand in minutes and put together just by prompting any AI tool, like Claude Design.
This is post one of a series where I document what I'm learning about how software actually works as someone who's been building with AI tools and want to understand what's happening under the hood.
A practical, copy-paste guide with limits, trade-offs, and examples
What building a testing agent taught me about where judgement still sits.
Why shipping fast doesn't mean building well
Everything you need to install, enable, and run the Figma dev mode MCP server with AI tools.
Part one of this article details all the parts you need to get started
Moving a team toward new tools when you cannot mandate anything.
Documenting something I learned when prompting and not reading the code enough
Documenting this to learn about design engineering and to help me communicate with Frontend Engineers better
This is a documentation for my learning of git
Documenting a guide best daily practice so I may reference it
Structuring design files so the handoff to production stops losing information.
Blueprint for a Next.js (App Router) App
Between what we gain and what we lose
How a mob session with Kiro taught me to ship code for the first time at work
On exploring workflows, guiding models, and supporting a team in the age of intelligent agents
On learning, self-awareness, and human nature in the age of AI