<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on Erkid Hoxholli</title>
    <link>https://erkidhoxholli.gitlab.io/tags/security/</link>
    <description>Recent content in Security on Erkid Hoxholli</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://erkidhoxholli.gitlab.io/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>10 Practical Tips for an Engineering-Grade AI SDLC</title>
      <link>https://erkidhoxholli.gitlab.io/posts/ai-sdlc-for-engineers/</link>
      <pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://erkidhoxholli.gitlab.io/posts/ai-sdlc-for-engineers/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;A Note on &amp;ldquo;Vibe Coding&amp;rdquo;:&lt;/strong&gt;&lt;br&gt;&#xA;There is nothing wrong with &amp;ldquo;vibe coding&amp;rdquo; in the right context. If you are building a quick prototype for a hackathon, trying a new library, experimenting with UI design without a database, or making a small internal tool where bugs do not cause real damage, asking an AI to quickly generate code is totally fine.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;This post is not for that.&lt;/strong&gt;&lt;br&gt;&#xA;If you are building production software—especially where users trust you with personal data (PII), health information (PHI), payment details, or mission-critical workflows—users deserve software that is secure, stable, and well-tested. You cannot rely on luck when real people and paying customers depend on your systems.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
