<?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: jongmin kim</title>
    <description>The latest articles on DEV Community by jongmin kim (@jongmin_kim_26e6d6df88003).</description>
    <link>https://dev.to/jongmin_kim_26e6d6df88003</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%2F4233210%2Fb4b8add4-ff10-407b-80a5-853954ebff63.png</url>
      <title>DEV Community: jongmin kim</title>
      <link>https://dev.to/jongmin_kim_26e6d6df88003</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jongmin_kim_26e6d6df88003"/>
    <language>en</language>
    <item>
      <title>What I measured when searching 30 minutes of dashcam footage</title>
      <dc:creator>jongmin kim</dc:creator>
      <pubDate>Wed, 11 Nov 2026 09:00:00 +0000</pubDate>
      <link>https://dev.to/jongmin_kim_26e6d6df88003/what-i-measured-when-searching-30-minutes-of-dashcam-footage-1jfo</link>
      <guid>https://dev.to/jongmin_kim_26e6d6df88003/what-i-measured-when-searching-30-minutes-of-dashcam-footage-1jfo</guid>
      <description>&lt;p&gt;A single search time can hide where a video review tool actually makes you wait. While testing Dashcam Finder, a Windows app I am building at JM Soft, I timed preparation, analysis, and the first set of suggestions separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  The test
&lt;/h2&gt;

&lt;p&gt;I used a 30-minute test file made from 29 minutes and 30 seconds of public road footage and a 30-second public dashcam excerpt. I sampled one frame per second and searched for &lt;code&gt;a traffic sign&lt;/code&gt;.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Stage&lt;/th&gt;
&lt;th&gt;Time in this run&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Startup preparation&lt;/td&gt;
&lt;td&gt;44.14 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Video analysis&lt;/td&gt;
&lt;td&gt;123.75 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Initial search after analysis&lt;/td&gt;
&lt;td&gt;3.32 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Combined time through first suggestions&lt;/td&gt;
&lt;td&gt;171.21 s&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These numbers come from one run. The initial search took 3.32 seconds because the video had already been analyzed. A separate detailed search added 111.62 seconds in this test.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I checked the result
&lt;/h2&gt;

&lt;p&gt;I selected a suggested timestamp and opened the original footage to check what was actually visible. A suggestion gives me a place to look. The original video is what I use to confirm the result. Sampling once per second can miss a detail that appears only between samples.&lt;/p&gt;

&lt;p&gt;The same distinction matters for a small car in the distance. The app can suggest vehicle models to compare, and the reviewer can inspect the original scene before drawing a conclusion.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://today-tip.com/video-search-preview/#traffic-sign-demo" rel="noopener noreferrer"&gt;Watch the traffic sign demo&lt;/a&gt; or &lt;a href="https://today-tip.com/video-search-preview/#vehicle-model-demo" rel="noopener noreferrer"&gt;see the separate small-vehicle comparison&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you have built a video review workflow, which would you time separately next: seeking to the original frame, or narrowing the candidate list?&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I build Dashcam Finder. This article was drafted with AI assistance using my test records.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>performance</category>
      <category>software</category>
    </item>
  </channel>
</rss>
