<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Research on The Coders Blog</title><link>https://thecodersblog.com/categories/research/</link><description>Recent content in Research on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 22:01:39 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/categories/research/index.xml" rel="self" type="application/rss+xml"/><item><title>Stop Letting LLMs Corrupt Your Research: Guarding Your .bib Files</title><link>https://thecodersblog.com/preventing-llm-editing-of-bib-files-2026/</link><pubDate>Wed, 06 May 2026 22:01:39 +0000</pubDate><guid>https://thecodersblog.com/preventing-llm-editing-of-bib-files-2026/</guid><description>&lt;p&gt;You asked your LLM to &amp;ldquo;clean up my bibliography,&amp;rdquo; and now your &lt;code&gt;.bib&lt;/code&gt; file looks like a cryptic puzzle. Welcome to the club. My own &lt;code&gt;.bib&lt;/code&gt; file, the meticulously curated backbone of countless research papers, has suffered the indignity of LLM-induced gibberish more times than I care to admit. This isn&amp;rsquo;t a theoretical concern; it&amp;rsquo;s a practical, infuriating problem that directly undermines research integrity.&lt;/p&gt;
&lt;h3 id="the-core-problem-llms-dont-understand-your-bib"&gt;The Core Problem: LLMs Don&amp;rsquo;t Understand Your &lt;code&gt;.bib&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Your &lt;code&gt;.bib&lt;/code&gt; file isn&amp;rsquo;t just a text file; it&amp;rsquo;s a structured database essential for academic publishing. It adheres to a specific syntax, and any deviation breaks your entire compilation pipeline. LLMs, while impressive language generators, fundamentally lack an inherent understanding of file system semantics, the critical nature of structured data, and the consequences of their probabilistic outputs. Granting them direct write access to such vital files is, frankly, asking for trouble.&lt;/p&gt;</description></item></channel></rss>