<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ChatGPT on David Cajio</title><link>https://davidcajio.com/tags/chatgpt/</link><description>Recent content in ChatGPT on David Cajio</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 David Cajio</copyright><lastBuildDate>Fri, 12 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://davidcajio.com/tags/chatgpt/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Second Brain for AWS Certification with Obsidian and AI</title><link>https://davidcajio.com/posts/aws-second-brain-obsidian-ai-workflow/</link><pubDate>Fri, 12 Jun 2026 00:00:00 +0000</pubDate><guid>https://davidcajio.com/posts/aws-second-brain-obsidian-ai-workflow/</guid><description>&lt;p&gt;When I started seriously preparing for AWS certifications, I hit a familiar problem for anyone working in infrastructure: the volume of information isn’t the hard part — retention and structure are.&lt;/p&gt;
&lt;p&gt;You can watch hours of training, build labs, and take pages of notes, but unless that information is continuously refined, it decays quickly. A few weeks later, the details blur: IAM evaluation logic, VPC routing behavior, the subtle differences between endpoint types — all of it starts to fade.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://davidcajio.com/posts/aws-second-brain-obsidian-ai-workflow/feature.jpg"/></item></channel></rss>