freelance / practical technical work
Build. Fix. Deploy.
I build, fix, and deploy projects that need technical problem-solving.
- Work
- Build / debug / deploy
- Scope
- Small, focused projects
- Approach
- Understand before adding code
- Small asks
- Welcome
01 / what I can help with
Technical work with a clear problem to solve.
I am most useful when something needs to be built, connected, repaired, secured, or made to work outside localhost.
- 01Backends and APIs that do the required jobDesigning endpoints, data flows, authentication, and the server-side logic behind a small product or feature.
- 02Frontends that actually reach the backendConnecting forms, sessions, APIs, errors, and state when the two halves currently disagree.
- 03Existing projects brought back to lifeTracing bugs, finishing partially working builds, and making sense of code generated with AI but never fully integrated.
- 04Deployments that work beyond one laptopFinding environment, configuration, domain, HTTPS, database, and production-only failures.
- 05Small tools that remove repetitive workScripts, command-line utilities, data helpers, and focused automation built around a real workflow.
- 06Security-minded custom developmentAuthentication, input handling, secret storage, access control, and small technical projects where trust boundaries matter.
02 / work as proof
Things I have already had to make work.
These are real projects with real tradeoffs—not a list of technologies I once opened.
Built browser-side encryption, authentication and OTP flows, API storage, sessions, controlled team access, and deployment.
Read project notesConnected a custom input-classification model to a public interface while keeping its weak classes and evaluation limits visible.
Read project notesCreated this responsive project workspace, its theme system, case-study structure, and the deployment around it.
See the siteBuilt a tool that gathers CVE context and public research material so the repetitive searching happens in one workflow.
Read project notes03 / contact
Need something built, fixed, or debugged? Get in touch.
Email is best when you already know what is broken or what you want to build. A short description, any useful links, and what “working” should look like are enough to start.
Instagram and Discord are fine for a quick first message. No pitch deck required.