<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        
        <title>The Goodcatch blog</title>
        <link>https://goodcatch.dev/blog</link>
        <description>Writing from Goodcatch.</description>
        <language>en</language>
        <atom:link href="https://goodcatch.dev/blog/feed.xml" rel="self" type="application/rss+xml"/>
                    <item>
                <title>Security Issues Junior Developers Most Often Miss in Pull Requests</title>
                <link>https://goodcatch.dev/blog/security-issues-junior-developers-most-often-miss-in-pull-requests</link>
                
                <guid isPermaLink="true">https://goodcatch.dev/blog/security-issues-junior-developers-most-often-miss-in-pull-requests</guid>
                <pubDate>Fri, 25 Sep 2026 19:00:03 +0000</pubDate>
                <description>Security bugs don&#039;t look broken. They hide inside clean, idiomatic code that works perfectly for the expected caller. Here are four vulnerability patterns that consistently slip through junior code reviews, and the specific habits that catch each one.</description>
            </item>
                    <item>
                <title>How to Spot Logic Bugs in a Pull Request Before They Hit Production</title>
                <link>https://goodcatch.dev/blog/how-to-spot-logic-bugs-in-a-pull-request-before-they-hit-production</link>
                
                <guid isPermaLink="true">https://goodcatch.dev/blog/how-to-spot-logic-bugs-in-a-pull-request-before-they-hit-production</guid>
                <pubDate>Wed, 23 Sep 2026 15:00:01 +0000</pubDate>
                <description>Logic bugs survive code review because they don&#039;t look wrong. Here&#039;s a practical method for catching them at the edges, plus how to build the pattern-recognition that makes it reliable.</description>
            </item>
            </channel>
</rss>
