Namakoo
Turning real-world problems into tools that work.
I studied information engineering (Doshisha University, Faculty of Science and Engineering, Department of Intelligent Information Engineering), then worked as an in-house SE in the pharmaceutical industry, building, together with the people on the floor, things they could actually use: going paperless, rolling out business systems, VBA development. What I find most rewarding is delivering working systems to the people who need them.
These days I keep building my own projects with AI. Code is written by AI now. That's exactly why what I take on is deciding and finishing: choosing what to build, choosing how to get there, judging whether the result is genuinely usable, and staying responsible until it actually works.
I don't leave everything to the AI. Whatever I have it implement, I always run and check myself; I judge acceptance on real devices and real use; and when something is off, I track down the cause and fix it. Not skipping this step of verifying is, I believe, what separates “looks like it works” from “actually works.”
Adding tests to the tools I publish, and honestly writing down even what I haven't verified, is an expression of that stance. When I build, I care about standing in the user's shoes and making something that fits the client's needs, balancing usability and function.
Solving real-world problems by using AI well to turn them into things that actually work. That's the kind of work I want to settle into and stay with for the long term.
I usually switch off in front of a board or screen with someone on the other side.
Every move changes the read. A match that truly clicks stays with me longer than the win or loss.
Quiet time spent reading ahead. The more I play, the more I notice my own habits of thought.
Read your opponent, try something, come back and try again. It's the process of getting a little better that I love.