<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Opemipo Jokotagba</title>
    <description>Opemipo Jokotagba — Docs Engineer, Technical Writer, and Software Developer. Passionate about making complex tech topics accessible through clear documentation and engaging content.</description>
    <link>https://opemipo-jokotagba.vercel.app</link>
    <atom:link href="https://opemipo-jokotagba.vercel.app/rss.xml" rel="self" type="application/rss+xml"/>
    <language>en-us</language>
    <lastBuildDate>Thu, 21 May 2026 21:14:42 GMT</lastBuildDate>
    <item>
      <title>Documentation is Infrastructure, Not an Afterthought</title>
      <link>https://opemipo-jokotagba.vercel.app/blog/documentation-is-infrastructure-not-an-afterthought/</link>
      <guid>https://opemipo-jokotagba.vercel.app/blog/documentation-is-infrastructure-not-an-afterthought/</guid>
      <description>Engineering orgs pour millions into reliability for systems they consider mission-critical, then let their docs rot. Teams that break this pattern treat documentation like infrastructure.</description>
      <pubDate>Mon, 18 May 2026 00:00:00 GMT</pubDate>
      <author>Opemipo Jokotagba</author>
      <category>Documentation</category>
        <category>Docs as Code</category>
        <category>Engineering Culture</category>
    </item>
    <item>
      <title>How I Built My Portfolio: Every Decision, Every Change</title>
      <link>https://opemipo-jokotagba.vercel.app/blog/building-my-portfolio-with-astro/</link>
      <guid>https://opemipo-jokotagba.vercel.app/blog/building-my-portfolio-with-astro/</guid>
      <description>A full breakdown of how I took an Astro 6 template and turned it into a production portfolio — covering identity, content, tooling, SVG banners, deployment, and the AI-augmented workflow behind it.</description>
      <pubDate>Wed, 06 May 2026 00:00:00 GMT</pubDate>
      <author>Opemipo Jokotagba</author>
      <category>Docs Engineering</category>
        <category>Astro</category>
        <category>Developer Experience</category>
    </item>
    <item>
      <title>What Does a Docs Engineer Actually Do?</title>
      <link>https://opemipo-jokotagba.vercel.app/blog/what-does-a-docs-engineer-do/</link>
      <guid>https://opemipo-jokotagba.vercel.app/blog/what-does-a-docs-engineer-do/</guid>
      <description>The role sits between writing and software engineering — here&apos;s what that looks like in practice, and why it matters for developer-facing products.</description>
      <pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate>
      <author>Opemipo Jokotagba</author>
      <category>Docs Engineering</category>
        <category>Career</category>
        <category>Technical Writing</category>
    </item>
    <item>
      <title>Writing API Documentation That Developers Actually Read</title>
      <link>https://opemipo-jokotagba.vercel.app/blog/writing-api-docs-developers-actually-read/</link>
      <guid>https://opemipo-jokotagba.vercel.app/blog/writing-api-docs-developers-actually-read/</guid>
      <description>Most API docs are technically complete but practically useless. Here&apos;s the framework I use to write reference documentation that developers trust and return to.</description>
      <pubDate>Fri, 20 Mar 2026 00:00:00 GMT</pubDate>
      <author>Opemipo Jokotagba</author>
      <category>API Documentation</category>
        <category>Technical Writing</category>
        <category>Developer Experience</category>
    </item>
    <item>
      <title>Why I Test Every Code Sample I Publish</title>
      <link>https://opemipo-jokotagba.vercel.app/blog/why-i-test-every-code-sample/</link>
      <guid>https://opemipo-jokotagba.vercel.app/blog/why-i-test-every-code-sample/</guid>
      <description>Untested code samples are a liability disguised as documentation. Here&apos;s the process I use to make sure every example in my docs actually runs.</description>
      <pubDate>Sat, 14 Feb 2026 00:00:00 GMT</pubDate>
      <author>Opemipo Jokotagba</author>
      <category>Technical Writing</category>
        <category>Code Quality</category>
        <category>Developer Experience</category>
    </item>
    <item>
      <title>Security Implications of AI Agents in Software Development</title>
      <link>https://opemipo-jokotagba.vercel.app/blog/security-implications-of-ai-agents-in-software-development/</link>
      <guid>https://opemipo-jokotagba.vercel.app/blog/security-implications-of-ai-agents-in-software-development/</guid>
      <description>AI coding assistants can introduce vulnerabilities just as easily as they remove them. Understanding what to watch for is now a core engineering competency.</description>
      <pubDate>Thu, 27 Feb 2025 00:00:00 GMT</pubDate>
      <author>Opemipo Jokotagba</author>
      <category>AI</category>
        <category>Security</category>
        <category>Software Development</category>
    </item>
    <item>
      <title>Why Ethics Matter in AI-Powered Documentation</title>
      <link>https://opemipo-jokotagba.vercel.app/blog/why-ethics-matter-in-ai-powered-documentation/</link>
      <guid>https://opemipo-jokotagba.vercel.app/blog/why-ethics-matter-in-ai-powered-documentation/</guid>
      <description>AI tools are changing how documentation gets written. That shift comes with responsibilities most teams haven&apos;t thought through yet — bias, accuracy, transparency, and accountability.</description>
      <pubDate>Tue, 04 Feb 2025 00:00:00 GMT</pubDate>
      <author>Opemipo Jokotagba</author>
      <category>AI</category>
        <category>Ethics</category>
        <category>Documentation</category>
    </item>
    <item>
      <title>Markdown Mastery: Tips for Writing Clear and Concise Docs</title>
      <link>https://opemipo-jokotagba.vercel.app/blog/markdown-mastery-tips-for-writing-clear-and-concise-docs/</link>
      <guid>https://opemipo-jokotagba.vercel.app/blog/markdown-mastery-tips-for-writing-clear-and-concise-docs/</guid>
      <description>Markdown is the default language of technical documentation. Here&apos;s how to use it well — from core syntax to the habits that separate readable docs from forgettable ones.</description>
      <pubDate>Tue, 21 Jan 2025 00:00:00 GMT</pubDate>
      <author>Opemipo Jokotagba</author>
      <category>Technical Writing</category>
        <category>Documentation</category>
        <category>Markdown</category>
    </item>
    <item>
      <title>5 Software Development Challenges That Can Be Solved With AI</title>
      <link>https://opemipo-jokotagba.vercel.app/blog/5-software-development-challenges-that-can-be-solved-with-ai/</link>
      <guid>https://opemipo-jokotagba.vercel.app/blog/5-software-development-challenges-that-can-be-solved-with-ai/</guid>
      <description>AI isn&apos;t replacing software developers — it&apos;s changing which problems require human attention. Here are five challenges where AI is making a measurable difference.</description>
      <pubDate>Sun, 12 Jan 2025 00:00:00 GMT</pubDate>
      <author>Opemipo Jokotagba</author>
      <category>AI</category>
        <category>Software Development</category>
        <category>Developer Experience</category>
    </item>
  </channel>
</rss>