<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Aiko Shirasawa</title>
    <description>The latest articles on DEV Community by Aiko Shirasawa (@aiko_shirasawa_752ab763ba).</description>
    <link>https://dev.to/aiko_shirasawa_752ab763ba</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4206283%2F904df588-0f15-4780-8999-2999afa6045a.png</url>
      <title>DEV Community: Aiko Shirasawa</title>
      <link>https://dev.to/aiko_shirasawa_752ab763ba</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/aiko_shirasawa_752ab763ba"/>
    <language>en</language>
    <item>
      <title>AI Is Helping Us Build Faster-But Are We Still Understanding What We Build?👁‍🗨</title>
      <dc:creator>Aiko Shirasawa</dc:creator>
      <pubDate>Tue, 27 Oct 2026 17:43:06 +0000</pubDate>
      <link>https://dev.to/aiko_shirasawa_752ab763ba/ai-is-helping-us-build-faster-but-are-we-still-understanding-what-we-build-1apj</link>
      <guid>https://dev.to/aiko_shirasawa_752ab763ba/ai-is-helping-us-build-faster-but-are-we-still-understanding-what-we-build-1apj</guid>
      <description>&lt;p&gt;AI-assisted development has changed the way many of us write software.&lt;/p&gt;

&lt;p&gt;Today, a developer can use tools like ChatGPT, Claude, Cursor, Copilot, or autonomous coding agents to generate features, refactor code, debug issues, and even design parts of an application architecture.&lt;/p&gt;

&lt;p&gt;The productivity gains are real.&lt;/p&gt;

&lt;p&gt;But there is another side of this shift that I think deserves more attention:&lt;/p&gt;

&lt;p&gt;We are producing code faster than we are producing understanding.&lt;/p&gt;

&lt;p&gt;And over time, that can become a serious engineering problem.&lt;/p&gt;

&lt;p&gt;The New Problem: Comprehension Debt&lt;/p&gt;

&lt;p&gt;Traditional technical debt is familiar.&lt;/p&gt;

&lt;p&gt;We make a fast implementation today, knowing that we may need to improve it later.&lt;/p&gt;

&lt;p&gt;But AI-assisted development introduces something slightly different.&lt;/p&gt;

&lt;p&gt;I think of it as comprehension debt.&lt;/p&gt;

&lt;p&gt;This happens when a project evolves faster than the developer or team can fully understand the reasoning behind it.&lt;/p&gt;

&lt;p&gt;For example, imagine this workflow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;You ask an AI agent to build authentication.&lt;/li&gt;
&lt;li&gt;It generates several files and dependencies.&lt;/li&gt;
&lt;li&gt;You ask it to fix a bug.&lt;/li&gt;
&lt;li&gt;It changes the architecture.&lt;/li&gt;
&lt;li&gt;You ask another AI tool to optimize the implementation.&lt;/li&gt;
&lt;li&gt;A week later, you discover another issue.&lt;/li&gt;
&lt;li&gt;A month later, someone asks:&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;“Why was this implemented this way?”&lt;/p&gt;

&lt;p&gt;At that moment, Git may tell you what changed.&lt;/p&gt;

&lt;p&gt;But it may not tell you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;why a certain approach was chosen,&lt;/li&gt;
&lt;li&gt;what alternatives were considered,&lt;/li&gt;
&lt;li&gt;which attempts failed,&lt;/li&gt;
&lt;li&gt;what the AI suggested,&lt;/li&gt;
&lt;li&gt;what the developer rejected,&lt;/li&gt;
&lt;li&gt;or what finally solved the problem.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That context may exist somewhere inside chat history, issue trackers, notes, commits, or personal memory.&lt;/p&gt;

&lt;p&gt;And that is exactly where things become difficult.&lt;/p&gt;

&lt;p&gt;Our Development History Is Becoming Fragmented&lt;/p&gt;

&lt;p&gt;Modern development already uses many tools.&lt;/p&gt;

&lt;p&gt;A typical project might include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;GitHub for source code and commits,&lt;/li&gt;
&lt;li&gt;Jira or Linear for issues,&lt;/li&gt;
&lt;li&gt;Slack for team discussions,&lt;/li&gt;
&lt;li&gt;Notion for documentation,&lt;/li&gt;
&lt;li&gt;AI assistants for technical reasoning,&lt;/li&gt;
&lt;li&gt;local notes for temporary decisions,&lt;/li&gt;
&lt;li&gt;and sometimes multiple coding agents at once.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each tool contains a piece of the story.&lt;/p&gt;

&lt;p&gt;But the complete development story is often missing.&lt;/p&gt;

&lt;p&gt;A commit may say:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Fix payment flow&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;An issue may say:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Checkout occasionally fails.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;An AI conversation may contain the real explanation:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The original implementation created a race condition when two asynchronous requests completed in a different order.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That reasoning is often more valuable than the commit message itself.&lt;/p&gt;

&lt;p&gt;Yet months later, it may be extremely difficult to recover.&lt;/p&gt;

&lt;p&gt;Git Tracks Code-Not Always Reasoning&lt;/p&gt;

&lt;p&gt;Git is one of the most important tools in software engineering.&lt;/p&gt;

&lt;p&gt;But Git was primarily designed to track changes in source code.&lt;/p&gt;

&lt;p&gt;It answers questions like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What changed?&lt;/li&gt;
&lt;li&gt;Who changed it?&lt;/li&gt;
&lt;li&gt;When did it change?&lt;/li&gt;
&lt;li&gt;Which version introduced this behavior?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But increasingly, developers also need answers to questions like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Why did we choose this architecture?&lt;/li&gt;
&lt;li&gt;What problem were we actually trying to solve?&lt;/li&gt;
&lt;li&gt;Which approaches failed before this one worked?&lt;/li&gt;
&lt;li&gt;What did the AI agent recommend?&lt;/li&gt;
&lt;li&gt;Why did we ignore another option?&lt;/li&gt;
&lt;li&gt;What assumptions existed at the time?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These questions become especially important when AI generates a significant portion of the code.&lt;/p&gt;

&lt;p&gt;AI Agents Make This Problem Bigger&lt;/p&gt;

&lt;p&gt;The more autonomous coding agents become, the more important development context becomes.&lt;/p&gt;

&lt;p&gt;Imagine an agent that can:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;create multiple files,&lt;/li&gt;
&lt;li&gt;update database schemas,&lt;/li&gt;
&lt;li&gt;install packages,&lt;/li&gt;
&lt;li&gt;generate tests,&lt;/li&gt;
&lt;li&gt;modify APIs,&lt;/li&gt;
&lt;li&gt;and refactor existing architecture.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All of that might happen during one interaction.&lt;/p&gt;

&lt;p&gt;The amount of code produced can be enormous compared with traditional manual development.&lt;/p&gt;

&lt;p&gt;But if we only preserve the final code, we lose the reasoning process that produced it.&lt;/p&gt;

&lt;p&gt;That becomes dangerous when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;another developer joins the project,&lt;/li&gt;
&lt;li&gt;the original developer leaves,&lt;/li&gt;
&lt;li&gt;a bug appears six months later,&lt;/li&gt;
&lt;li&gt;security decisions need to be reviewed,&lt;/li&gt;
&lt;li&gt;or a team needs to understand why a system behaves in a particular way.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Development History May Become a First-Class Engineering Asset&lt;/p&gt;

&lt;p&gt;I believe one important evolution in developer tooling will be the preservation of &lt;strong&gt;development reasoning&lt;/strong&gt;, not just source code.&lt;/p&gt;

&lt;p&gt;Imagine a project where you could see:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Requirement
    ↓
Initial idea
    ↓
AI discussion
    ↓
First implementation
    ↓
Problem discovered
    ↓
Alternative considered
    ↓
Architecture decision
    ↓
Final fix
    ↓
Lesson learned
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That is much more useful than looking at isolated commits.&lt;/p&gt;

&lt;p&gt;It creates something closer to institutional memory for software.&lt;/p&gt;

&lt;p&gt;This Is Why Tools Like HindSite Are Interesting&lt;/p&gt;

&lt;p&gt;I recently came across an early-stage project called HindSite that is exploring this problem.&lt;/p&gt;

&lt;p&gt;The concept is interesting because it focuses on reconstructing the development journey from different traces such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;commits,&lt;/li&gt;
&lt;li&gt;AI conversations,&lt;/li&gt;
&lt;li&gt;issues,&lt;/li&gt;
&lt;li&gt;notes,&lt;/li&gt;
&lt;li&gt;blockers,&lt;/li&gt;
&lt;li&gt;decisions,&lt;/li&gt;
&lt;li&gt;and fixes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Instead of only asking:&lt;/p&gt;

&lt;p&gt;“What code changed?”&lt;/p&gt;

&lt;p&gt;the idea is to help answer:&lt;/p&gt;

&lt;p&gt;“What actually happened while we were building this?”&lt;/p&gt;

&lt;p&gt;The workflow is centered around capturing development activity, reconstructing the timeline, reviewing important moments, reflecting on decisions, and eventually exporting useful knowledge.&lt;/p&gt;

&lt;p&gt;It is still an early-stage concept, but I think the underlying problem is important regardless of which product ultimately solves it.&lt;/p&gt;

&lt;p&gt;Why This Matters for Teams&lt;/p&gt;

&lt;p&gt;This kind of development memory could be useful in several situations.&lt;/p&gt;

&lt;p&gt;Developer onboarding&lt;/p&gt;

&lt;p&gt;A new developer could understand not only the current architecture but also the decisions that created it.&lt;/p&gt;

&lt;p&gt;Project handoffs&lt;/p&gt;

&lt;p&gt;Freelancers and contractors could leave behind a much clearer explanation of what they built.&lt;/p&gt;

&lt;p&gt;Debugging&lt;/p&gt;

&lt;p&gt;Engineers could understand the sequence of decisions that introduced a difficult problem.&lt;/p&gt;

&lt;p&gt;Architecture reviews&lt;/p&gt;

&lt;p&gt;Teams could revisit old technical decisions with the original context still available.&lt;/p&gt;

&lt;p&gt;AI oversight&lt;/p&gt;

&lt;p&gt;Developers could better understand how much of a system was influenced by an AI agent and why certain recommendations were accepted.&lt;/p&gt;

&lt;p&gt;Retrospectives&lt;/p&gt;

&lt;p&gt;Instead of relying on memory, teams could analyze actual development events:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Where did we lose time?&lt;/li&gt;
&lt;li&gt;Which approaches failed?&lt;/li&gt;
&lt;li&gt;Which bugs repeated?&lt;/li&gt;
&lt;li&gt;What patterns helped us move faster?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The Future Developer May Need Two Histories&lt;/p&gt;

&lt;p&gt;For years, software teams have preserved one major history:&lt;/p&gt;

&lt;p&gt;the history of the code.&lt;/p&gt;

&lt;p&gt;In an AI-assisted world, we may also need:&lt;/p&gt;

&lt;p&gt;the history of the reasoning.&lt;/p&gt;

&lt;p&gt;The first tells us:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Here is what changed.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The second tells us:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Here is why it changed.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And increasingly, both may be necessary to maintain complex software responsibly.&lt;/p&gt;

&lt;p&gt;A Question for Developers&lt;/p&gt;

&lt;p&gt;As AI becomes more involved in your development workflow, how are you preserving the reasoning behind your code?&lt;/p&gt;

&lt;p&gt;Do you rely on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;commit messages,&lt;/li&gt;
&lt;li&gt;architecture decision records,&lt;/li&gt;
&lt;li&gt;AI conversation history,&lt;/li&gt;
&lt;li&gt;project documentation,&lt;/li&gt;
&lt;li&gt;issue trackers,&lt;/li&gt;
&lt;li&gt;or just memory?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I am curious how other developers are dealing with this.&lt;/p&gt;

&lt;p&gt;Because AI is making us faster.&lt;/p&gt;

&lt;p&gt;The next challenge may be making sure we still understand what we are building.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>softwareengineering</category>
    </item>
    <item>
      <title>Let's Grow Together 🌱</title>
      <dc:creator>Aiko Shirasawa</dc:creator>
      <pubDate>Mon, 26 Oct 2026 09:12:17 +0000</pubDate>
      <link>https://dev.to/aiko_shirasawa_752ab763ba/lets-grow-together-6j5</link>
      <guid>https://dev.to/aiko_shirasawa_752ab763ba/lets-grow-together-6j5</guid>
      <description>&lt;p&gt;Let's Grow Together 🌱&lt;/p&gt;

&lt;p&gt;Every developer starts as a beginner.&lt;/p&gt;

&lt;p&gt;We make mistakes, face difficult problems, and learn something new every day.&lt;/p&gt;

&lt;p&gt;We don't need to know everything. We just need to keep learning, keep building, and help each other along the way.&lt;/p&gt;

&lt;p&gt;A small act of kindness or a simple piece of advice can make a big difference in someone's journey.&lt;/p&gt;

&lt;p&gt;Let's be developers who share knowledge, support others, and build things that make life better. ❤️&lt;/p&gt;

&lt;p&gt;What's one lesson you've learned that you'd like to share with other developers?&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>community</category>
      <category>discuss</category>
      <category>learning</category>
    </item>
  </channel>
</rss>
