AI and IaC have made writing code much easier, yet even a small change can still mean quotes, approvals, and a contract with an outside vendor. That is the norm in Japan, where most IT engineers work at vendors rather than at the companies that use the systems. This post sorts out seven situations where you could build it in-house but have to outsource anyway, when outsourcing is the right call, and how to work your way out.
Yosuke Maruyama
I am a software engineer based in Tokyo (JST, UTC+9). I design and build APIs with Python and TypeScript, and take projects end to end — requirements, design, implementation, testing, operations, and maintenance. I also work independently across AWS and Docker infrastructure and CI/CD, React / Vue front-end development, and LLM integration. See About for my background, and Work for past projects.
RECENT POSTS
Coming into the office has real costs, but when a team is deciding on requirements and design, being in the same room gives it an edge. Splitting development into a "deciding" phase and a "building" phase, I lay out how to use office days well.
The matching side of an anonymous chat app, which puts people who picked the same topic into rooms of two or three. The waiting queue is a Redis sorted set, and taking people off it is a single Lua script, so no one gets assigned twice even when both servers try at the same moment.
If you have plenty of on-prem infrastructure experience but are new to both the cloud and IaC, this post explains how IaC differs from building by hand in the console, why you should use it, and which tool to pick.
For project enquiries, please review the terms on Work, then get in touch via About.