<?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: Trần Nguyên Châu</title>
    <description>The latest articles on DEV Community by Trần Nguyên Châu (@chautnus).</description>
    <link>https://dev.to/chautnus</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3931686%2F7a6266e6-8f17-4d56-9c5e-0f22edb90b48.jpg</url>
      <title>DEV Community: Trần Nguyên Châu</title>
      <link>https://dev.to/chautnus</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chautnus"/>
    <language>en</language>
    <item>
      <title>How AI made my workflow more mouse-driven than keyboard-driven</title>
      <dc:creator>Trần Nguyên Châu</dc:creator>
      <pubDate>Thu, 14 May 2026 16:57:00 +0000</pubDate>
      <link>https://dev.to/chautnus/how-ai-made-my-workflow-more-mouse-driven-than-keyboard-driven-2cb6</link>
      <guid>https://dev.to/chautnus/how-ai-made-my-workflow-more-mouse-driven-than-keyboard-driven-2cb6</guid>
      <description>&lt;p&gt;A small shift happened in my workflow over the last year, and I didn’t fully notice it until recently:&lt;/p&gt;

&lt;p&gt;I don’t type nearly as much anymore.&lt;/p&gt;

&lt;p&gt;A lot of my day used to be spent writing — code, messages, docs, search queries, notes.&lt;br&gt;
Now a much bigger portion of it is spent reading, reviewing, comparing, monitoring, and switching between contexts.&lt;/p&gt;

&lt;p&gt;AI is a big reason why.&lt;/p&gt;

&lt;p&gt;Instead of generating every draft from scratch, I’m now often:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;reviewing AI output&lt;/li&gt;
&lt;li&gt;comparing versions&lt;/li&gt;
&lt;li&gt;checking whether something is correct&lt;/li&gt;
&lt;li&gt;jumping between browser tabs, apps, terminals, and docs&lt;/li&gt;
&lt;li&gt;monitoring results instead of manually producing every line myself
That sounds like a software change.
But for me, it also became a physical interaction change.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;My hand is on the mouse most of the day now.&lt;/p&gt;

&lt;p&gt;And that exposed something I hadn’t really questioned before: most of my productivity actions are still designed around the keyboard.&lt;/p&gt;

&lt;p&gt;Things like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;taking a screenshot&lt;/li&gt;
&lt;li&gt;switching apps&lt;/li&gt;
&lt;li&gt;snapping windows&lt;/li&gt;
&lt;li&gt;opening a bookmarked URL&lt;/li&gt;
&lt;li&gt;triggering a repeated shortcut&lt;/li&gt;
&lt;li&gt;moving between “work surfaces” quickly&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of those are difficult.&lt;br&gt;
But when your workflow becomes more mouse-heavy and less typing-heavy, reaching back to the keyboard starts to feel less like a shortcut and more like a tiny interruption.&lt;/p&gt;

&lt;p&gt;That’s the part that surprised me.&lt;/p&gt;

&lt;p&gt;Keyboard shortcuts used to feel seamless because I was already typing all the time.&lt;br&gt;
Now I’m often reading something on screen, following an AI-generated draft, comparing outputs, or scanning multiple windows. In that mode, my mouse is already “active,” while the keyboard feels secondary.&lt;/p&gt;

&lt;p&gt;So the old shortcut model still works.&lt;br&gt;
It just no longer fits the flow as naturally.&lt;/p&gt;

&lt;p&gt;That mismatch is what pushed me to build a small Windows tool for myself: RightWheel.&lt;/p&gt;

&lt;p&gt;The idea is simple:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;hold right-click, scroll, and trigger an action.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I started using it for the handful of things I kept doing over and over:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;switching tasks&lt;/li&gt;
&lt;li&gt;launching common shortcuts&lt;/li&gt;
&lt;li&gt;opening frequently used links&lt;/li&gt;
&lt;li&gt;taking screenshots&lt;/li&gt;
&lt;li&gt;reducing the constant mouse-keyboard-mouse transition&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What interested me most wasn’t just the tool itself.&lt;br&gt;
It was the realization behind it:&lt;/p&gt;

&lt;p&gt;AI may be changing not only what we do on computers, but how we physically interact with them.&lt;/p&gt;

&lt;p&gt;If more of our work becomes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;reviewing instead of drafting&lt;/li&gt;
&lt;li&gt;orchestrating instead of manually producing&lt;/li&gt;
&lt;li&gt;navigating instead of typing&lt;/li&gt;
&lt;li&gt;supervising systems instead of directly operating every step&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;...then it makes sense that our input habits might shift too.&lt;/p&gt;

&lt;p&gt;The assumption that the keyboard is always the primary productivity surface may come from an earlier shape of digital work.&lt;/p&gt;

&lt;p&gt;I’m curious whether other people are feeling this too.&lt;/p&gt;

&lt;p&gt;Have AI tools changed your mouse-to-keyboard ratio?&lt;br&gt;
Have you adapted your setup in any way — better mouse software, macros, Stream Deck, window managers, voice input, custom gestures?&lt;/p&gt;

&lt;p&gt;I’d love to know what changed in your own day-to-day workflow.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>shortcut</category>
      <category>automation</category>
    </item>
  </channel>
</rss>
