Blog
#Essay
26 post(s)
-
"Why Study for Certifications When AI Exists?" — Returning to Basics
AI-driven development cuts learning costs to near zero and boosts productivity. The more I leaned on that convenience, the more I doubted whether studying still mattered. Here is why I returned to basics and chose to face the Information Processing Engineer Exam head-on.
-
Tasukiba's Tidy UI — Roots in a High-School Notebook
Tasukiba, an AI operations secretary, has a UI built on one belief: things belong where they belong. The root traces back to a high-school notebook redesigned for the reader every term — a habit that, twenty years later, shapes how project management and knowledge management feel on screen. Told as five definitions.
-
Changing Sunday Night and Monday Morning — Tasukiba's Worldview as an AI Operations Secretary
Sunday evening, you sigh about Monday's escalation. Tasukiba, an AI operations secretary, surfaces the project management context you need by semantic search before you go looking. Every product decision is judged by one question: does this brighten Monday morning? Here's the worldview, written with its emotional temperature intact.
-
An Hour a Day Was Evaporating — Why I Built Tasukiba, an AI Operations Secretary
Six people times ten minutes equals an hour a day, evaporating from meetings just to find a file. Data piles up unused while judgment leans on a few heads. I built Tasukiba, an AI operations secretary, to dissolve that with semantic search across project management and knowledge management.
-
Think Again and the Binary Bias I Couldn't See in Myself
Adam Grant's 'Think Again' named a habit I'd never noticed — collapsing nuance into either/or. Four thinking modes and three daily practices for the gray zone.
-
Five hours that felt like two — Adler's 'now, here' as I actually felt it
A night studying for an InfoSec certification when five hours felt like two: body exhausted, time forgotten. That, I realized, is what 'live now, here' actually feels like. The closing post of the three-part Adler series, woven with my habit of overthinking my career and the moment a teammate said 'thank you' for an AI rollout.
-
'Only I protect me' — how The Courage to Be Disliked handed me back the steering wheel
From caring deeply about how others saw me, to noticing 'how others evaluate me is their task' and starting to show up as myself. The Courage to Be Disliked's teleology rejects causal blame of the past and returns the steering wheel of life to your own hands. A reading note on the path through a job change and side-project that the book quietly backed me through.
-
Knowing psychological safety isn't enough — the four stages: understand, design, implement, reproduce
Many people can say psychological safety matters. Few can actually design it into a team, and fewer still can reproduce the same level in a different team. A four-stage model — built on Amy Edmondson's research — for moving from understanding to reproduction, the four leader behaviors that make it concrete, and why psychological safety only works when paired with accountability.
-
The urge to decide fast is your strength's shadow — Need for Cognitive Closure and the 2-week rule
People praised as fast decision-makers are often the most vulnerable to the Need for Cognitive Closure — the psychological pull to escape ambiguity by reaching for an answer too early. A look at Arie Kruglanski's concept, why structural thinkers are especially susceptible, and three small daily habits — the 3-column journal, the 2-week rule, and stopping at three Whys — that I'm using to retune my own judgment.
-
When I realized my biggest gap wasn't technical — what an outside review showed me
Approaching a career change at 27, I asked someone outside my circle to do a gap analysis on me. The most important line in the report wasn't about new skills or certifications. It was about turning the experience I already had into transferable knowledge, and seeing my own thinking habits more clearly. A reflection on the gap mid-career engineers most often miss.
-
An Objective Self-Portrait — Five Strengths, Five Weaknesses
Subjective intro is on the profile page. Here is the third-party fact-based view: five strengths and five weaknesses with evidence, plus what I am improving.
-
From Funeral to Adventure: A Manager's Real Art of Asking
A manager's words decide if meetings feel like funerals or adventures. From The New Art of Asking: expedition mindset, four rules, the see-build-ask cycle.
-
Anything But Absolute Yes Is a No — Essentialism in Practice
Essentialism: anything but absolute yes is a no. The pickle jar, sleep as the foundation of mastery, and the courage to stop. Applied to engineer life.
-
16 Person-Days of Development Done in 2 Hours — Design Doc Completeness Determines Speed
In a personal project, AI-driven development completed 16 person-days of work in 2 hours. The biggest factor wasn't AI speed — it was the completeness of the design document that eliminated all decision-making.
-
The Power of Small Contributions — Reflections from Tokyo Blaze Symphonic Band's 13th Concert
Attending the Tokyo Blaze Symphonic Band's concert for the third consecutive year, I witnessed how individual efforts converge into a single piece of music — and what it taught me about team building and psychological safety.
-
Don't Bring Motivation to Work — Deliver Consistent Results Through Systems, Like Brushing Your Teeth
Motivation-driven action inevitably burns out. Understanding how self-preservation instincts block change, and how systematizing actions like brushing teeth enables consistent output regardless of mood.
-
"Essentialism" and "Effortless" — The Two Wheels of What to Do and How to Do It
Reading Essentialism (what to do) and Effortless (how to do it), I explored how to focus on essential tasks and build systems to make them easier. Applying the Pickle Jar Theory, 10,000-hour rule, and broaden-and-build theory to engineering work.
-
"Black Box Thinking" — Life Is Too Short to Experience Every Failure Yourself
Reading 'Black Box Thinking' revealed how ego blocks learning from failure. I explore the mechanisms of self-esteem-driven denial and how engineers can build systems to detect, report, and leverage failure.
-
Why I Built This Homepage — Walking with Astro v6
Why I built this homepage and what I poured into it. Plus the characteristics of Astro v6, a framework still under-documented in Japanese.
-
What Money Really Is — Connecting People
An essay on what money really is. Money has no inherent value; it pays for human labor. With Zimbabwe hyperinflation, an engineer view on why value attaches.
-
What Reading Gave Me Wasn't Knowledge — It Was the Habit of Thinking from Multiple Angles
The greatest value from reading isn't the volume of knowledge gained, but the ability to interpret things from multiple perspectives. Here's how the self-questioning habit cultivated through reading benefits code reviews and requirements analysis.
-
"No Effort Goes Unrewarded" — How the Concept of Accumulating Luck Changed My Work
I used to believe some efforts are wasted. A single book changed my definition of effort: time spent for others accumulates as luck. Here's how this shift transformed my approach as an engineer.
-
Janet's Law — How to Counter Time Feeling Shorter as You Age
Janet's Law: why each year feels shorter as we age. Countermeasures using new experiences and continuous learning — stretching subjective time as an engineer.
-
"Words Are Blades" — How a Single Phrase Can Stay with Someone Forever
Inspired by a line from Detective Conan — 'Words are blades' — I reflect on the dual nature of language: the power to uplift and the power to wound. As an engineer, I practice 'maturing words before speaking.'
-
INTJ-AS (The Lone Grand Designer) — My Working Style Through Personality Assessment
My extended MBTI (64-type) result is INTJ-AS. I've articulated my communication style, team behavior, and growth areas as self-disclosure for future collaborators.
-
From "YumeLog" to "YumeHashi" — Building a Bridge Between Dreams and Reality
The story behind renaming my personal app from YumeLog to YumeHashi, the 3-step design philosophy (write, break down, keep going) for turning dreams into action, and why I keep building despite zero revenue.