---
title: "Daisuke Masuda (@x5gtrn) | Hashnode"
description: "DJ Ekusi, SAEKIKAZUMI. Read the latest articles by Daisuke Masuda on Hashnode."
url: "https://hashnode.com/@x5gtrn"
---

@x5gtrn

# Daisuke Masuda

@x5gtrn · Hyogo, Japan · Joined July 2022

DJ Ekusi, SAEKIKAZUMI

[Website](https://x5gtrn.tumblr.com/)

## Comments

[Yes—that is an important distinction. I would keep the superseded ADR as historical evidence, but change its metadata to something like status: superseded and superseded\_by: ADR-0042. For runbooks and knowledge notes, I use an explicit field such as depends\_on: \[ADR-0017\] or a direct link to the ADR. A review query can then surface every current note that still depends on a superseded decision. I would not automatically mark those notes as wrong—the operational guidance may still be valid—but I would flag them as review\_required until someone verifies them against the replacement ADR. That preserves the decision trail while making the possible blast radius visible. It is also a good example of why queries should be treated as views: the durable truth is the explicit dependency recorded in each note, while the query simply shows which dependencies now require attention.](https://hashnode.com/posts/article-2026-10-26-0519/6ade649f9a9caf1ce03fbe28/comment/6ae0789987f3dfa3c6294f41#reply-6ae08370432ab635a1b322cc)

Reply · Article · Oct 27 · [Stop Choosing an Obsidian Template. Engineer a Vault Architecture.](https://hashnode.com/posts/article-2026-10-26-0519/6ade649f9a9caf1ce03fbe28)

[That’s exactly the failure mode I wanted to address: once the vault’s structure becomes harder to trust than a plain folder of notes, the system is working against you. Treating queries as disposable views—and keeping truth in a small, explicit folder and metadata contract—makes hybrid approaches much less fragile. I’m especially glad the Spring Boot latency walkthrough helped. I wanted the architecture discussion to survive contact with real engineering work, where one incident can involve logs, hypotheses, source material, decisions, and reusable knowledge without all of them becoming the same kind of note. Thanks for articulating this so clearly.](https://hashnode.com/posts/article-2026-10-26-0519/6ade649f9a9caf1ce03fbe28/comment/6adf01be526d33fbe6c6e9f4#reply-6adf98aea80e040568ca2c29)

Reply · Article · Oct 26 · [Stop Choosing an Obsidian Template. Engineer a Vault Architecture.](https://hashnode.com/posts/article-2026-10-26-0519/6ade649f9a9caf1ce03fbe28)

[I’d report both, with total rework time per task as the headline and a breakdown by failure class underneath. Class counts alone can hide the difference between five quick fixes and one issue that takes an hour to untangle. For a small pilot, I’d keep the logging lightweight: minutes spent diagnosing, repairing, and revalidating, plus a primary failure class—such as misunderstood requirements, missing context, environment problems, or regressions. If one repair spans several classes, I’d record the time once and note the overlap rather than force a precise split. Your point about variability matters, too. I’d show individual task results alongside the median and range, including abandoned attempts. That would make it easier to see whether the savings are repeatable or whether a few expensive repairs wipe them out. The useful comparison is how much human effort it takes to reach an accepted change.](https://hashnode.com/posts/article-2026-10-21-0400/6ad7ba53c429c7a403085e55/comment/6ad9f6b211f2c6d0c5124e48#reply-6ada5daa13b6878167803eef)

Reply · Article · Oct 22 · [What Is JetBrains Air?](https://hashnode.com/posts/article-2026-10-21-0400/6ad7ba53c429c7a403085e55)

[Thanks for such thoughtful reading! You’ve picked up on the part I most wanted to emphasize: faster implementation makes the surrounding engineering work more visible, and often more important. For me, a useful review question is: “What could still be wrong even if every test passes?” The tests might encode the wrong assumption, miss a compatibility requirement, or never exercise the failure path that matters in production. A clear task contract gives us a basis for asking those questions—but we still have to challenge the contract itself. That’s where I see agents being most useful: helping us gather evidence and explore those gaps, while a human remains accountable for deciding whether the change is ready to ship.](https://hashnode.com/posts/article-2026-10-21-0400/6ad7ba53c429c7a403085e55/comment/6ad9e855bc4868d3cac35f11#reply-6ada5d6d8e426f81fa2b9401)

Reply · Article · Oct 22 · [What Is JetBrains Air?](https://hashnode.com/posts/article-2026-10-21-0400/6ad7ba53c429c7a403085e55)

[You’re welcome! As a fellow JetBrains user, I’d love to hear what you think of Air if you get a chance to try it. 👍](https://hashnode.com/posts/article-2026-10-21-0400/6ad7ba53c429c7a403085e55/comment/6ad929304f0fe0198b2f38f0#reply-6ada5d2213b6878167803b9b)

Reply · Article · Oct 22 · 1 · [What Is JetBrains Air?](https://hashnode.com/posts/article-2026-10-21-0400/6ad7ba53c429c7a403085e55)

[That’s exactly the connection I hoped to make. If the contract stays in the reviewer’s head, the agent and reviewer can end up working from different definitions of “done.” I’d take it one step further: define the evidence when assigning the task. Which behavior must change, what must stay compatible, and which check would fail if the fix were wrong? That gives the agent a clearer target and the reviewer something concrete to challenge. A second agent’s review can help, but it still needs to point to a reproducible issue or a missing check.](https://hashnode.com/posts/article-2026-10-21-0400/6ad7ba53c429c7a403085e55/comment/6ad8b82a0b893ee410285227#reply-6ada5be613b6878167803570)

Reply · Article · Oct 22 · [What Is JetBrains Air?](https://hashnode.com/posts/article-2026-10-21-0400/6ad7ba53c429c7a403085e55)

[Agreed on the order: sandbox first, then evaluate whether a model swap actually helps. A better model won’t fix an overprivileged executor or a command running in the wrong directory. That’s the distinction I wanted to make in the article: policy checks decide whether an action should run, while execution boundaries constrain what it can touch if something goes wrong. Explicit working directories, restricted filesystem and network access, and scoped credentials belong in that execution layer—not just in the prompt. Debugging should let us reproduce a bad tool call without turning the investigation into another production incident. Thanks for making the priority explicit.](https://hashnode.com/posts/article-2026-09-22-1843/6ab24e1dad174d23b1e2b209/comment/6ab3e63405613eb605b75ee4#reply-6ab4161e3bb4a819888b307e)

Reply · Article · Sep 23 · [Making AI Agents Safe and Fast](https://hashnode.com/posts/article-2026-09-22-1843/6ab24e1dad174d23b1e2b209)

[Thanks for calling this out—and for the concrete migration example. I’d fold it into the execution layer’s contract. The article leaves that concurrency requirement underspecified. You’re right that binding approval to an action hash prevents substitution, but doesn’t make two independently approved actions safe to execute concurrently. The executor should acquire a lock scoped to the affected resource before execution, with conflicting approved actions remaining queued. I’d add one requirement after acquiring that lock: revalidate the action’s preconditions against the current resource state. If migration A changes the schema that migration B was evaluated against, B’s approval may still be unexpired and correctly bound to its action, while the assumptions behind that approval no longer hold. In that case, the executor should stop and return it for re-evaluation—and renewed approval if the approved assumptions or operation change. So the contract I’d make explicit is: acquire the resource lock, recheck approval validity and resource preconditions, execute, and record the resulting state before releasing the lock. A queued action gets those checks when it actually reaches execution. That belongs alongside the credential boundary you highlighted. Approval establishes authority for an operation; the executor also has to establish that the operation is valid against the state it is about to change.](https://hashnode.com/posts/article-2026-09-22-1843/6ab24e1dad174d23b1e2b209/comment/6ab258761da04364a31ee2cc#reply-6ab25d6d6991703e7eb67c87)

Reply · Article · Sep 22 · [Making AI Agents Safe and Fast](https://hashnode.com/posts/article-2026-09-22-1843/6ab24e1dad174d23b1e2b209)

[Thank you so much, Sanoary! I really appreciate your thoughtful comment. I completely agree—the real measure of AI tooling is not how impressive the technology looks in isolation, but whether it helps teams solve meaningful problems and deliver reliable, accepted engineering outcomes. I’ll keep exploring that intersection between technology, engineering practice, and business value in future articles. Thanks again for reading!](https://hashnode.com/posts/article-2026-09-07-0152/6a9d9afdf86e60ec7168fb55/comment/6a9f9147e30b74f15b01d9b5#reply-6a9fd942473c79aec4749706)

Reply · Article · Sep 8 · [Where Is JetBrains AI Heading?](https://hashnode.com/posts/article-2026-09-07-0152/6a9d9afdf86e60ec7168fb55)

[Thank you for the thoughtful comment. I partially agree. You're right that thorough review remains essential — no one should blindly accept changes without understanding them. That said, I've found that in many cases, it's actually more effective to re-engage the agent and ask it to explain or walk through the specific changes it made, rather than reading every single line manually from scratch. This often helps highlight the important or risky parts more efficiently while still keeping human oversight. Of course, for critical or high-risk changes, there's no substitute for carefully reading through the diff yourself. Do you have any particular methods or prompts you use when reviewing agent-generated code?](https://hashnode.com/posts/article-2026-06-19-1822/6a350aa2effbf7457ec5f789/comment/6a37df9dc2c46193d44c532b#reply-6a38611ae20dbbf0dc512d95)

Reply · Article · Jun 21 · [Developing with AI Agents: A Practical Field Guide to Codex, Claude Code, and Claude Cowork](https://hashnode.com/posts/article-2026-06-19-1822/6a350aa2effbf7457ec5f789)
