Testing background, product instincts
My default lens is quality engineering: clear boundaries, observable behavior, realistic failure modes, and no blind faith in hype. That affects how I build macOS apps, browser extensions, and MCP servers.
My default lens is quality engineering: clear boundaries, observable behavior, realistic failure modes, and no blind faith in hype. That affects how I build macOS apps, browser extensions, and MCP servers.
AI integrations should make a narrow job faster and safer. Reads can be broad, writes need explicit gates, and every product should be useful even when the model is wrong.
Practical automation courses without bullshit, including AI-track work.
A charity tech conference built around real conversations, not stage polish.
Regular meetups for QA people who want useful technical depth.
Media and commentary about the parts people usually do not say out loud.
A macOS browser picker utility for routing links across contexts.
A macOS dictation/transcription app with Dynamic Notch behavior.
A backup-first MCP server for domain and DNS operations.