<?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: milo4210</title>
    <description>The latest articles on DEV Community by milo4210 (@zhaodx_milo4210_f77b96b3d).</description>
    <link>https://dev.to/zhaodx_milo4210_f77b96b3d</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%2F4145492%2Ff7b459bf-5438-433f-9a91-4a7dac089e32.png</url>
      <title>DEV Community: milo4210</title>
      <link>https://dev.to/zhaodx_milo4210_f77b96b3d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zhaodx_milo4210_f77b96b3d"/>
    <language>en</language>
    <item>
      <title>My Coworker Was Using Ctrl+C and Ctrl+V to Check Hundreds of References, So I Built This</title>
      <dc:creator>milo4210</dc:creator>
      <pubDate>Sun, 27 Sep 2026 12:28:08 +0000</pubDate>
      <link>https://dev.to/zhaodx_milo4210_f77b96b3d/my-coworker-was-using-ctrlc-and-ctrlv-to-check-hundreds-of-references-so-i-built-this-53oe</link>
      <guid>https://dev.to/zhaodx_milo4210_f77b96b3d/my-coworker-was-using-ctrlc-and-ctrlv-to-check-hundreds-of-references-so-i-built-this-53oe</guid>
      <description>&lt;p&gt;A coworker asked me to build a small tool for checking academic references.&lt;/p&gt;

&lt;p&gt;Part of his job is reviewing references and making sure the papers actually exist and the information is correct.&lt;/p&gt;

&lt;p&gt;His workflow was basically:&lt;/p&gt;

&lt;p&gt;Ctrl+C → search → open the paper → check DOI, authors, title, journal, year → record the result&lt;/p&gt;

&lt;p&gt;Then repeat it for the next reference.&lt;/p&gt;

&lt;p&gt;And sometimes there are hundreds of references to check.&lt;/p&gt;

&lt;p&gt;So he asked me if I could automate some of it.&lt;/p&gt;

&lt;p&gt;I built a very simple internal tool first.&lt;/p&gt;

&lt;p&gt;He shared it with a few coworkers, and that's where things got interesting. They started finding cases that the first version couldn't handle:&lt;/p&gt;

&lt;p&gt;DOI doesn't match the paper&lt;br&gt;
title or author information is different&lt;br&gt;
wrong journal or publication year&lt;br&gt;
incomplete metadata&lt;br&gt;
the paper can't be found at all&lt;/p&gt;

&lt;p&gt;So I kept adding checks and fixing edge cases.&lt;/p&gt;

&lt;p&gt;Eventually, that little internal tool became CiteWise.&lt;/p&gt;

&lt;p&gt;The idea behind CiteWise is pretty simple: instead of just formatting a citation, it checks whether the reference itself looks correct.&lt;/p&gt;

&lt;p&gt;You can use it to verify DOI and bibliographic information, find mismatches, and check references in batches.&lt;/p&gt;

&lt;p&gt;CiteWise: [&lt;a href="https://cietwise.dev" rel="noopener noreferrer"&gt;https://cietwise.dev&lt;/a&gt;]&lt;/p&gt;

&lt;p&gt;I'm putting it out there now and would like to see how other people handle this problem.&lt;/p&gt;

&lt;p&gt;If you've ever had to manually check a large bibliography, what does your workflow look like?&lt;/p&gt;

</description>
      <category>automation</category>
      <category>productivity</category>
      <category>tooling</category>
      <category>tools</category>
    </item>
  </channel>
</rss>
