Brian Chang is the Owner and Lead Software Developer at Sazokashi.

Available for engineering work where secure web and cyber operations, technical depth, steady execution, and strong ownership matter.

Owner and Lead Software Developer

Aspiring for secure, dependable web systems with strong ownership and careful operational judgment.

I run Sazokashi as a humble, hands-on software practice. I do the work end to end: product thinking, scoping, design, architecture, implementation, deployment, security, and the steady operational discipline required to keep production systems trustworthy after launch.

My work is grounded in ownership. As a sole developer, I am responsible not only for code, but also for the decisions, tradeoffs, and follow-through around it. I translate ambiguous needs into clear plans, align scope with business reality, and build systems that remain understandable and maintainable under real-world pressure.

Most of my time is spent building full stack web applications with React, Next.js, Express.js, TypeScript, and SQL/NoSQL databases. Around that core, I handle the surrounding work that serious software requires: interface design, system architecture, data modeling, workflow design, project management, research, deployment strategy, and production operations.

I care deeply about security and sound engineering judgment. That includes secure defaults, careful validation, authentication and authorization boundaries, access discipline, observability, and practical hardening across the stack. I pay close attention to who should have access, when they should have it, and how systems can make the safe path the easy path.

End-to-End Delivery

I can take a product from concept to production: discovery, scoping, roadmap shaping, implementation, launch, iteration, and maintenance.

Architecture With Operational Constraints In Mind

I design systems around clarity, reliability, and long-term operability rather than novelty. Good architecture should reduce risk, create understandable workflows, and make incidents easier to reason about.

Security, Access, And Trust Boundaries

I treat security as part of engineering, not a final checklist. Web security, defensive design, authorization boundaries, and practical cybersecurity thinking are part of how I build every feature and process.

Automation And Production Discipline

I look for repeatable, paved-path ways to handle provisioning, validation, access-sensitive workflows, deployment, and maintenance so systems are easier to support and harder to misuse.

How I Work

Careful ownership, clear thinking, steady execution.

The best software work is usually quiet. It is disciplined planning, good tradeoffs, strong communication, and a willingness to handle the unglamorous details that determine whether a product actually succeeds.

I stay close to outcomes.

I do not separate technical work from operational or business consequences. I think about users, operators, maintainers, timelines, access patterns, and risk together.

I prefer durable decisions.

I research carefully, scope realistically, and choose solutions that make future change, review, and support easier instead of merely making the present look impressive.

I value polish with purpose.

Details matter when they improve comprehension, performance, accessibility, maintainability, or trust. The goal is software that feels considered, not decorative.