01 / About
A developer interested in how technology serves people.
I explore how AI, automation, and software engineering can make public services smarter, simpler, and more accessible.
I build web applications, APIs, and practical experiments that explore how technology can improve the way people work, access information, and use digital services.
Most of my work sits between three interests: applying AI where it genuinely reduces effort, automating the repetitive parts of a workflow, and engineering systems that stay maintainable after the first release. Public services are where those three things matter most, because reliability and clarity affect real access.
I treat AI as an assistant, not an authority. Every experiment on this site records what the model does, what a person is still responsible for, and where the approach breaks down.
I enjoy exploring new tools, turning rough ideas into working prototypes, and learning how technology can improve the way people interact with services.
02Working principles
How I decide what to build and how far to take it.
Clarity first
Write interfaces and documentation that a first-time visitor can follow without a manual.
Responsible by default
Consider privacy, accessibility, security, and human oversight from the start.
Learn by building
Use practical experiments to turn ideas into working systems.
Human in the loop
AI drafts and suggests. A person stays accountable for the final decision.
03Responsible AI
What I check before an AI feature ships.
- State clearly when content or a suggestion was produced by AI.
- Keep a person accountable for anything that is published or acted on.
- Document known limitations and hallucination risk alongside the feature.
- Use synthetic or illustrative data unless real data is genuinely required.
- Explain output in plain language rather than presenting it as fact.
04Capabilities