I’m passionate about breaking down complex systems, understanding them piece by piece, and rebuilding them into something clear and dependable. In my work, I value reducing hidden assumptions and implicit knowledge, and aim for designs with well-defined responsibilities that are easier to read and reason about. Rather than stopping at “it works,” I care about shaping software into something that is easier to verify, maintain, and continuously improve.
| Date | Title | Overview |
|---|---|---|
| 2026/05/01 | Rewriting a WebDAV Implementation from Apache + Perl to Go: Migration Design Was Harder Than Implementation Apache + Perl の WebDAV 実装を Go に刷新した話 — 実装より難しかった「移行設計」 |
Modernizing a long-running WebDAV service is less about rewriting code than about designing a safe migration path, with clear compatibility boundaries, release criteria, observable operations, and shared architectural decisions. |
| 2026/04/06 | Improving Code Review Quality with GitHub Copilot Custom Instructions GitHub Copilot で Custom Instructions を活用し、コードレビューの品質を上げる |
AI code review becomes more reliable when its role and industry standards (e.g., CWE, OWASP) are made explicit through custom instructions, while humans still need to guide the broader design judgment and architectural decisions. |
| 2025/10/07 | Redesigning a Perl Codebase: A Go-Based Approach to Modernization Perlコードベースの再設計：Go 言語によるモダン化へのアプローチ |
A legacy-to-Go migration succeeds when AI is treated as an accelerator inside a human-led strategy: minimize scope, redesign responsibilities, and build confidence through tests rather than chasing wholesale replacement. |
| 2025/04/17 | Effective Load Testing with Grafana k6 and AWS Fargate Grafana k6 × AWS Fargate で実現する効果的な負荷テスト |
Effective load testing should be easy to model, repeat, and scale, and combining k6 with AWS Fargate makes realistic backend performance validation practical for development and operations teams. |
| 2024/12/24 | For Those Starting OSS Activities: Personal Development with Go これから OSS 活動を始める方へ：Go を使用した個人開発の話 |
Starting OSS work is most approachable when you build a small working system first, document decisions as you learn, and let incremental progress turn uncertainty into durable technical experience. |