Good technical writing conveys not just knowledge, but perspective. This is where I think and write.
In software development, we call major changes that alter existing behavior "breaking changes." Over the past few years, I’ve made several breaking changes to my own life. On paper, everything was an upgrade, but some things that used to work just fine ended up broken along the way.
Preparing for tech interviews has always been challenging. One of the most frustrating parts is the heavily one-sided power dynamic. As a candidate, it's hard to gauge their actual standards, and it's easy to spiral into self-doubt afterward. Let's talk about it.
Using React Three Fiber, I brought my real room into the browser—turning physical objects into an interactive table of contents, and using spatial memory to tell the story of my life and work over the past few years.
I came across a video from ten years ago of myself playing and singing in a rooftop shack apartment. It brought back the recording studio I paid for in high school, and the version of me who once considered going into music. If I had one piece of advice for my younger self, it would be: keep a record of your life.
Back in college, trying to learn Japanese, I looked for language exchange partners on Lang-8 and JCInfo.net. It wasn't the most efficient approach, but it led me to two wonderful people: once over fugu hot pot in Osaka, and another in a reunion five years later in Taipei. Being able to come together without any agenda might be becoming increasingly precious in this day and age.
I once wrote a script to tally how many PRs I contributed in a quarter, how many reviews I left, and how many tickets I closed, hoping to use numbers to prove my output to my manager. My manager simply remarked that performance isn't just about output. Years later, I finally understood—when a measure becomes a target, it ceases to be a good measure. From the British window tax and the Hanoi rat bounty to evaluating developers by PR counts today, the underlying mechanism is exactly the same.
Putting an image on a webpage is the simplest task in frontend development. But doing it properly—including resizing, generating multiple formats, and withstanding heavy traffic—is actually an entire end-to-end solution. Eventually, I offloaded everything to Cloudflare Images, keeping only a single original image.
At the end of 2024, I left LINE Fukuoka (now LY Corporation). This post reflects on what I built, the managers and colleagues I worked with, and why I ultimately decided to move on.
Feynman, Chaplin, and the movie Hyakumeter: from an insecure boy to someone capable of helping others, sharing the reflections and life philosophies that shaped me most.
Why spend time running your own blog in an era dominated by short-form video and social media? Here are my thoughts after nearly a decade of blogging.
Sharing my thoughts and journey with weight training over the past period.
Want employees to work late every day and hustle like a founder? Give them equity.
Expanding on Jake Archibald's article, this post organizes how modern responsive images should be written: why width/height are still necessary, when to use CSS aspect-ratio, how to choose between AVIF and WebP, and using picture/source/srcset for art direction on mobile devices.
Just go program
An essay spurred by Wiwi's "Be the Default"—touching on the unwritten rules of Fukuoka's escalators, how AI content dominates SEO rankings, and Voltaire's definition of taste.
Many engineers use "it depends" to shut down a discussion. But as I see it, what matters most is actually driving the discussion forward.
Previously, auto-resizing a textarea required listening to scrollHeight in JavaScript. With CSS field-sizing: content, a single line replaces it all, supporting textarea, input, and select. This article covers the pain points of older approaches and how to use field-sizing.
Being a cynical critic feels great and gives a sense of superiority, but in the end, you realize it only leaves you with emptiness.
When is JWT suitable, and when are session cookies better? A re-examination of this classic topic from the perspectives of security, implementation cost, and user experience.
Many people use words like "startup," "growth-stage," or "stable" to describe companies, but these terms are too vague to serve as real criteria for judgment. What does the company currently survive on? How does it grow? What is its most painful problem? By understanding what stage a company is in, you will truly know what problems you are solving every day—and whether the company is the right fit for you.
