<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Secure Coding on Rav3nf0</title>
    <link>https://rav3nf0.github.io/tags/secure-coding/</link>
    <description>Recent content in Secure Coding on Rav3nf0</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Sep 2025 13:40:21 +0530</lastBuildDate>
    <atom:link href="https://rav3nf0.github.io/tags/secure-coding/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Secure Coding the Heck Out of Your Web Apps</title>
      <link>https://rav3nf0.github.io/posts/securecode/</link>
      <pubDate>Mon, 01 Sep 2025 13:40:21 +0530</pubDate>
      <guid>https://rav3nf0.github.io/posts/securecode/</guid>
      <description>In web development, writing secure code isn&amp;rsquo;t just a &amp;ldquo;nice-to-have&amp;rdquo; – it&amp;rsquo;s absolutely critical. One tiny vulnerability can blow up in your face, exposing sensitive user data, trampling on privacy, and, let&amp;rsquo;s be real, absolutely trashing your reputation. I want to walk you through some of the most common web application vulnerabilities I see out there, share how we tackle them, and give you some pointers on what I zero in on during a good old-fashioned code review.</description>
    </item>
  </channel>
</rss>
