Keep asking what better means.
Better for whom, and in what way? I revisit problems and assumptions, using people’s experiences and real feedback to clarify what we should aim for.
Build. Learn. Make it better.
A freelance developer based in Yokohama, Japan.
I've developed web applications since 2016 and worked independently since 2023.
My experience spans front-end, back-end, and infrastructure, from design to implementation and operations.
01 / HOW I WORK
Assumptions shift. What we need changes.
I value the agility to keep moving, learning and revisiting decisions along the way.
Better for whom, and in what way? I revisit problems and assumptions, using people’s experiences and real feedback to clarify what we should aim for.
I turn hypotheses into working software and learn from the response. Moving between design and implementation, I update decisions and use what I learn to improve the next iteration.
I think about boundaries that make the effects of change clear, and checks that let us make changes with confidence. I record the reasons behind decisions so the product and team can keep moving.
02 / SELECTED WORKS
An interactive star-map site that connects technical vocabulary through the genealogy of "why it was born." Features a d3-force Canvas star map, Content-as-Code with MDX + Zod, 40+ interactive learning components, and zero-cost operation on Cloudflare Workers.
About the design and development
A web service that records and archives Japan's disappearing soundscapes as 'bookmarks of memory'. Features sample-accurate loop playback with the Web Audio API, content-as-code, a full Cloudflare stack, and a Python audio preprocessing pipeline.
About the design and development
03 / NOTES & IDEAS
Notes on the questions I encounter while designing and developing software.
Running Qwen3.8-27B Q4_K_M on an M4 Mac mini and an RTX 3090, comparing speed, memory bandwidth, build costs, and rationality against GPT-5.6 Luna.
A problem-and-solution guide to building API gateways on Envoy Proxy, covering control plane options, authorization patterns, and a comparison with OSS gateways that ship authorization as plugins.
Part 1 of a 5-part series that traces OAuth/OIDC through the lens of why each architecture became necessary. It walks through the limits of monolithic session auth, the password anti-pattern, and the introduction of an Identity Provider (IdP).
04 / CONTACT
For work requests or inquiries about my independent apps and services.
Please include the details in the contact form.