Working with the developer community means listening closely to a question before trying to answer it. A working example often tells me more than a long description of the problem.
I enjoy the point where helping one person reveals something that could be clearer for everyone else. That might be an explanation, a missing step, or a control whose behavior needs another look.
How I work
I move between the design and the implementation. Putting real words into a layout or connecting a button to its action can expose a question that the sketch left open.
I prefer to keep those questions small enough to try. Once the interaction works, I can judge it by using it, including the awkward cases that a polished preview tends to leave out.
How this site is builtBackground and contributions
My CV covers my experience. My Raycast profile collects the extensions I've shared.