<?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: Eric</title>
    <description>The latest articles on DEV Community by Eric (@eric666).</description>
    <link>https://dev.to/eric666</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%2F3032242%2Ff019d506-873d-4ad9-b763-f0cfdd303194.png</url>
      <title>DEV Community: Eric</title>
      <link>https://dev.to/eric666</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/eric666"/>
    <language>en</language>
    <item>
      <title>The Video I Kept Avoiding</title>
      <dc:creator>Eric</dc:creator>
      <pubDate>Mon, 15 Jun 2026 13:41:20 +0000</pubDate>
      <link>https://dev.to/eric666/the-video-i-kept-avoiding-1bib</link>
      <guid>https://dev.to/eric666/the-video-i-kept-avoiding-1bib</guid>
      <description>&lt;p&gt;I had this one video sitting on my desktop for days.&lt;br&gt;
Not a polished video. Not something I was excited to edit. Just one of those long recordings where I knew there was probably something useful inside, but every time I opened it, the timeline looked like a threat.&lt;/p&gt;

&lt;p&gt;So I did what every reasonable person does: I ignored it.&lt;br&gt;
The annoying part was that I did not need the video itself. I needed the words. There were a few ideas, a couple of lines I wanted to reuse, and maybe one section that could turn into a note or post later. But finding those parts meant scrubbing through the whole thing, guessing from the waveform, stopping every few seconds, and slowly losing interest in my own material.&lt;br&gt;
That little frustration is one of the reasons I started building NeatScribe.&lt;/p&gt;

&lt;p&gt;At first, I thought of it as a simple transcription tool. Upload a file, get the text, move on. But the more I used it myself, the clearer the real problem became: recordings are useful, but they are hard to enter. Text is the doorway.&lt;/p&gt;

&lt;p&gt;So I built a &lt;a href="https://neatscribe.com" rel="noopener noreferrer"&gt;video to text&lt;/a&gt; workflow into NeatScribe for exactly this kind of moment. Not for perfect studio content. For the messy files people actually have: product demos, calls, lectures, interviews, screen recordings, half-forgotten ideas.&lt;/p&gt;

&lt;p&gt;The transcript does not magically make the video better.&lt;br&gt;
It just makes the video usable.&lt;/p&gt;

&lt;p&gt;And honestly, that is the part I care about most. I do not want every recording to become “content.” I just want the useful parts to stop being trapped in the timeline.&lt;/p&gt;

</description>
      <category>podcast</category>
      <category>video</category>
      <category>whisper</category>
      <category>transcription</category>
    </item>
    <item>
      <title>test</title>
      <dc:creator>Eric</dc:creator>
      <pubDate>Mon, 15 Jun 2026 13:30:21 +0000</pubDate>
      <link>https://dev.to/eric666/test-4ih6</link>
      <guid>https://dev.to/eric666/test-4ih6</guid>
      <description>&lt;p&gt;test&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
