<?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: Lin JunJie</title>
    <description>The latest articles on DEV Community by Lin JunJie (@linjunjie525).</description>
    <link>https://dev.to/linjunjie525</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%2F3574496%2Fa732825a-8be2-4f08-afd5-1f7d1dd32053.jpg</url>
      <title>DEV Community: Lin JunJie</title>
      <link>https://dev.to/linjunjie525</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/linjunjie525"/>
    <language>en</language>
    <item>
      <title>Evidence-Based Engineering: How Research Shapes My Full Stack Development Process</title>
      <dc:creator>Lin JunJie</dc:creator>
      <pubDate>Tue, 21 Oct 2025 11:43:39 +0000</pubDate>
      <link>https://dev.to/linjunjie525/evidence-based-engineering-how-research-shapes-my-full-stack-development-process-gkm</link>
      <guid>https://dev.to/linjunjie525/evidence-based-engineering-how-research-shapes-my-full-stack-development-process-gkm</guid>
      <description>&lt;p&gt;Many developers focus on shipping features fast, but speed without structure often leads to technical debt.&lt;/p&gt;

&lt;p&gt;I’ve been exploring an approach I call Evidence-Based Engineering &lt;br&gt;
It’s about:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Measuring performance instead of guessing&lt;/li&gt;
&lt;li&gt;Designing modular, testable systems&lt;/li&gt;
&lt;li&gt;Documenting everything like a research process&lt;/li&gt;
&lt;li&gt;Learning continuously from academic findings&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This mindset helps me build software that’s not just fast, but sustainable and data-backed.&lt;/p&gt;

&lt;p&gt;Do you use research or data-driven approaches in your dev workflow? &lt;/p&gt;

</description>
      <category>fullstack</category>
      <category>productivity</category>
      <category>ai</category>
      <category>softwareengineering</category>
    </item>
    <item>
      <title>Understanding Caching in Web Development</title>
      <dc:creator>Lin JunJie</dc:creator>
      <pubDate>Tue, 21 Oct 2025 10:01:55 +0000</pubDate>
      <link>https://dev.to/linjunjie525/understanding-caching-in-web-development-1hm3</link>
      <guid>https://dev.to/linjunjie525/understanding-caching-in-web-development-1hm3</guid>
      <description>&lt;p&gt;Caching plays a crucial role in improving performance and reducing latency in modern applications. &lt;br&gt;
From CPUs to CDNs, caching is everywhere, and understanding how to use it effectively can make a huge difference in your system’s scalability.&lt;/p&gt;

&lt;p&gt;In this post, I explore:&lt;br&gt;
Cache-Aside (Lazy Loading): Fetch from DB on a miss, then store in cache.&lt;br&gt;
Write-Through: Update DB and cache simultaneously for strong consistency.&lt;br&gt;
Write-Behind: Write to cache first, update DB asynchronously for speed.&lt;/p&gt;

&lt;p&gt;Each pattern comes with its own trade-offs between performance, consistency, and complexity, and choosing the right one depends on your use case.&lt;/p&gt;

&lt;p&gt;Always remember: your database is the source of truth, and your cache is the performance booster.&lt;/p&gt;

&lt;p&gt;If you found this useful, drop a ❤️ or share your caching strategy below!&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>redis</category>
      <category>backend</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
