<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fabio Oliveira</title><link>https://fbdo.github.io/index.html</link><description>Recent content on Fabio Oliveira</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 16 Jul 2026 10:00:00 +0100</lastBuildDate><atom:link href="https://fbdo.github.io/index.xml" rel="self" type="application/rss+xml"/><item><title>AI-DLC v2, Part 1: What Actually Changes</title><link>https://fbdo.github.io/posts/ai-dlc-v2-part-1-what-changes.html</link><pubDate>Thu, 16 Jul 2026 10:00:00 +0100</pubDate><guid>https://fbdo.github.io/posts/ai-dlc-v2-part-1-what-changes.html</guid><description>&lt;h1 id="ai-dlc-v2-part-1-what-actually-changes"&gt;
 AI-DLC v2, Part 1: What Actually Changes
 &lt;a class="heading-link" href="#ai-dlc-v2-part-1-what-actually-changes"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;Most teams have settled into a comfortable arrangement with AI in their software delivery: the model writes code, a human reviews it, and everyone moves on. It works, but it quietly caps how far the automation can go — every stage still waits on a person to say &amp;ldquo;yes, continue.&amp;rdquo; The AI-Driven Development Life Cycle (AI-DLC) was built to challenge that ceiling, and its second version, now in preview, sharpens the challenge considerably.&lt;/p&gt;</description></item><item><title>The AI Act Deadline Didn't Move — Not the Part That'll Bite You</title><link>https://fbdo.github.io/posts/ai-act-deadline-evidence-problem.html</link><pubDate>Wed, 15 Jul 2026 09:00:00 +0100</pubDate><guid>https://fbdo.github.io/posts/ai-act-deadline-evidence-problem.html</guid><description>&lt;h1 id="the-ai-act-deadline-didnt-move--not-the-part-thatll-bite-you"&gt;
 The AI Act Deadline Didn&amp;rsquo;t Move — Not the Part That&amp;rsquo;ll Bite You
 &lt;a class="heading-link" href="#the-ai-act-deadline-didnt-move--not-the-part-thatll-bite-you"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;Half my DACH customers relaxed last month. They read &amp;ldquo;EU AI Act high-risk rules delayed to 2027&amp;rdquo; and quietly stood their compliance programs down.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s a mistake, and it&amp;rsquo;s worth being precise about why.&lt;/p&gt;
&lt;p&gt;The Digital Omnibus split the August 2, 2026 deadline into two piles. One moved. The other — the one most likely to touch a mainstream business — did not. And this is no longer a proposal: the Council gave the amendments &lt;a href="https://www.dlapiper.com/en-us/insights/publications/law-in-tech/2026/digital-omnibus-on-ai" class="external-link" target="_blank" rel="noopener"&gt;final green light on June 29&lt;/a&gt;; the delay is binding law, not a rumor you can plan around.&lt;/p&gt;</description></item><item><title>The 59% That Never Ship: Why AI Agents Die Between Demo and Production</title><link>https://fbdo.github.io/posts/59-percent-never-ship-ai-agents-demo-to-production.html</link><pubDate>Mon, 06 Jul 2026 10:00:00 +0100</pubDate><guid>https://fbdo.github.io/posts/59-percent-never-ship-ai-agents-demo-to-production.html</guid><description>&lt;h1 id="the-59-that-never-ship-why-ai-agents-die-between-demo-and-production"&gt;
 The 59% That Never Ship: Why AI Agents Die Between Demo and Production
 &lt;a class="heading-link" href="#the-59-that-never-ship-why-ai-agents-die-between-demo-and-production"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;&lt;img src="https://fbdo.github.io/images/59-percent-never-ship-ai-agents-demo-to-production/hero.png" alt="An AI agent’s happy-path demo giving way to the long tail of production failures"&gt;&lt;/p&gt;
&lt;p&gt;Tian Pan framed this better than anyone I&amp;rsquo;ve read. In &lt;a href="https://tianpan.co/blog/2026-05-17-demo-to-production-cliff-agent-90-percent" class="external-link" target="_blank" rel="noopener"&gt;The Demo-to-Production Cliff&lt;/a&gt;, he makes a claim that sounds wrong until you do the arithmetic: a 90%-accurate per step agent isn&amp;rsquo;t 90% of a product. It&amp;rsquo;s an unshippable one. His diagnosis is airtight, so I&amp;rsquo;m not going to re-litigate it — I&amp;rsquo;m going to take it as given and push on the part that leaves practitioners stuck: &lt;em&gt;how&lt;/em&gt; you make failure cheap on real infrastructure. That&amp;rsquo;s the question I put to 16 CTOs who deploy agents for a living, and their answers are what most of this post is about.&lt;/p&gt;</description></item><item><title>The AI-Powered SDLC Landscape: Where AI-DLC Fits</title><link>https://fbdo.github.io/posts/ai-powered-sdlc-landscape-where-ai-dlc-fits.html</link><pubDate>Mon, 06 Jul 2026 10:00:00 +0100</pubDate><guid>https://fbdo.github.io/posts/ai-powered-sdlc-landscape-where-ai-dlc-fits.html</guid><description>&lt;h1 id="the-ai-powered-sdlc-landscape-where-ai-dlc-fits"&gt;
 The AI-Powered SDLC Landscape: Where AI-DLC Fits
 &lt;a class="heading-link" href="#the-ai-powered-sdlc-landscape-where-ai-dlc-fits"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;AI-DLC v2 just hit preview (&lt;a href="https://github.com/awslabs/aidlc-workflows" class="external-link" target="_blank" rel="noopener"&gt;awslabs/aidlc-workflows&lt;/a&gt;). To mark it, I&amp;rsquo;m running a short series on AI-DLC over the coming weeks. This first post steps back to map the whole AI-powered SDLC landscape and show where AI-DLC fits; the follow-ups go deeper into what v2 changes and how to put it to work.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src="https://fbdo.github.io/images/ai-powered-sdlc-landscape-where-ai-dlc-fits/ai-dlc-journey-4-waypoints.svg" alt="The journey toward an autonomous SDLC — from autocomplete through SDD to an agentic SDLC"&gt;
&lt;em&gt;Figure: The journey to an autonomous SDLC — Autocomplete → SDD → Human-managed SDLC → Agentic SDLC, with a fully-autonomous aspirational endpoint. The single axis — how much of the lifecycle does AI drive? — sorts every framework.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Why Autonomous Cost Governance Is FinOps's SRE Moment</title><link>https://fbdo.github.io/posts/finops-agents-sre-moment.html</link><pubDate>Mon, 06 Jul 2026 10:00:00 +0100</pubDate><guid>https://fbdo.github.io/posts/finops-agents-sre-moment.html</guid><description>&lt;h1 id="why-autonomous-cost-governance-is-finopss-sre-moment"&gt;
 Why Autonomous Cost Governance Is FinOps&amp;rsquo;s SRE Moment
 &lt;a class="heading-link" href="#why-autonomous-cost-governance-is-finopss-sre-moment"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;SRE went from pagers to auto-remediation in a decade. FinOps is about to make that same leap in months — and platform teams who see the pattern have a massive head start.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="the-tipping-point"&gt;
 The Tipping Point
 &lt;a class="heading-link" href="#the-tipping-point"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;On June 9, 2026, AWS launched the &lt;a href="https://aws.amazon.com/finops-agent/" class="external-link" target="_blank" rel="noopener"&gt;FinOps Agent&lt;/a&gt; in public preview at FinOps X in San Diego — the first AWS-native agent that doesn&amp;rsquo;t just &lt;em&gt;show&lt;/em&gt; you cost anomalies, it &lt;em&gt;investigates&lt;/em&gt; them autonomously.&lt;/p&gt;</description></item><item><title>AWS re:Invent 2025 — Accelerating Development and DevSecOps with Amazon Bedrock and Kiro (PEX303)</title><link>https://fbdo.github.io/posts/reinvent-2025-bedrock-kiro-devsecops.html</link><pubDate>Wed, 03 Dec 2025 10:00:00 +0100</pubDate><guid>https://fbdo.github.io/posts/reinvent-2025-bedrock-kiro-devsecops.html</guid><description>&lt;h1 id="accelerating-development-and-devsecops-with-amazon-bedrock-and-kiro"&gt;
 Accelerating Development and DevSecOps with Amazon Bedrock and Kiro
 &lt;a class="heading-link" href="#accelerating-development-and-devsecops-with-amazon-bedrock-and-kiro"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;My AWS re:Invent 2025 session (PEX303) on accelerating software
development and DevSecOps practices with Amazon Bedrock and Kiro.&lt;/p&gt;
&lt;div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;"&gt;
			&lt;iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/P2YX43I8GFI?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="AWS re:Invent 2025 - Accelerating Development and DevSecOps with Amazon Bedrock and Kiro (PEX303)"&gt;&lt;/iframe&gt;
		&lt;/div&gt;</description></item><item><title>Improving Reliability and Performance for Teleoperations for Autonomous Driving Vehicles on AWS</title><link>https://fbdo.github.io/posts/teleoperations-autonomous-driving-aws.html</link><pubDate>Fri, 21 Jul 2023 10:00:00 +0100</pubDate><guid>https://fbdo.github.io/posts/teleoperations-autonomous-driving-aws.html</guid><description>&lt;p&gt;External post on the AWS Industries blog: how automakers can use WebRTC
and AWS services (Kinesis Video Streams, Direct Connect) to build secure,
low-latency communication between autonomous vehicles and remote
teleoperation centers.&lt;/p&gt;</description></item><item><title>Scalability and high availability rules</title><link>https://fbdo.github.io/posts/scalability-and-high-availability-rules.html</link><pubDate>Sun, 27 Jan 2019 20:53:16 +0100</pubDate><guid>https://fbdo.github.io/posts/scalability-and-high-availability-rules.html</guid><description>&lt;h1 id="objectives"&gt;
 Objectives
 &lt;a class="heading-link" href="#objectives"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;This page describes a set of rules and a methodology that, once applied to a system, can help you evaluate how well your system is regarding
scalability and availability, can help you map your weaknesses and plan actions to improve them.
In this context, scalability, availability and performance measured by low latency and high throughput are highly intertwined, as a high available
system need to scale to be available regardless the load, a system with a high throughput scale more easily than one with a low throughput, and
as a consequence is more available.&lt;/p&gt;</description></item><item><title>The belonging clues</title><link>https://fbdo.github.io/posts/belonging-clues.html</link><pubDate>Sun, 13 Jan 2019 18:39:50 +0100</pubDate><guid>https://fbdo.github.io/posts/belonging-clues.html</guid><description>&lt;h1 id="dont-forget-the-belonging-clues"&gt;
 Don&amp;rsquo;t forget the belonging clues
 &lt;a class="heading-link" href="#dont-forget-the-belonging-clues"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;A reminder to myself, from the book &lt;a href="https://www.goodreads.com/book/show/33517721-the-culture-code" class="external-link" target="_blank" rel="noopener"&gt;Culture Code&lt;/a&gt;, a book I can recommend:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Posture and expressions are important&lt;/li&gt;
&lt;li&gt;Avoid interruptions&lt;/li&gt;
&lt;li&gt;Spotlight your weakness (I can be wrong here)&lt;/li&gt;
&lt;li&gt;Embrace the message (hug the messager)&lt;/li&gt;
&lt;li&gt;Preview future connections&lt;/li&gt;
&lt;li&gt;Overdue thank yous&lt;/li&gt;
&lt;li&gt;Design a painstakingly interview&lt;/li&gt;
&lt;li&gt;Eliminate bad apples (no dickhead policy)&lt;/li&gt;
&lt;li&gt;Design spaces that maximaze collisions&lt;/li&gt;
&lt;li&gt;Everyone has a voice&lt;/li&gt;
&lt;li&gt;Pick up trash&lt;/li&gt;
&lt;li&gt;Capitalize in threshold moments (day one)&lt;/li&gt;
&lt;li&gt;Avoid to give sandwich feedback&lt;/li&gt;
&lt;li&gt;Embrace fun&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>AWS Observability Handbook</title><link>https://fbdo.github.io/book.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://fbdo.github.io/book.html</guid><description>&lt;div class="book-page"&gt;
 &lt;a class="book-cover-link" href="https://amzn.eu/d/050S80h2" target="_blank" rel="noopener"&gt;
 &lt;img class="book-cover" src="https://fbdo.github.io/images/book/aws-observability-handbook-cover.jpg"
 alt="Cover of AWS Observability Handbook"&gt;
 &lt;/a&gt;
 &lt;div class="book-details"&gt;
 &lt;h2 class="book-title"&gt;AWS Observability Handbook&lt;/h2&gt;
 &lt;p class="book-subtitle"&gt;Monitor, trace, and alert your cloud applications with AWS' myriad observability tools&lt;/p&gt;
 &lt;p class="book-meta"&gt;By &lt;strong&gt;Fabio Oliveira&lt;/strong&gt; and &lt;strong&gt;Phani Kumar Lingamallu&lt;/strong&gt; · Published by Packt&lt;/p&gt;
 &lt;a class="book-buy" href="https://amzn.eu/d/050S80h2" target="_blank" rel="noopener"&gt;Get the book on Amazon&lt;/a&gt;
 &lt;/div&gt;
&lt;/div&gt;
&lt;h2 id="about-the-book"&gt;
 About the book
 &lt;a class="heading-link" href="#about-the-book"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;As modern application architecture grows increasingly complex, identifying potential points of failure and measuring end user satisfaction, in addition to monitoring application availability, is key. This book helps you explore AWS observability tools that provide end-to-end visibility, enabling quick identification of performance bottlenecks in distributed applications.&lt;/p&gt;</description></item><item><title>Contact me</title><link>https://fbdo.github.io/contact.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://fbdo.github.io/contact.html</guid><description>&lt;p&gt;Want to get in touch? Drop a message below and it lands straight in my
inbox. I read everything, though I can&amp;rsquo;t always promise a fast reply.&lt;/p&gt;
&lt;form action="https://api.web3forms.com/submit" method="POST" class="contact-form"&gt;
 &lt;!-- Web3Forms access key (public by design; only authorizes sending to my inbox) --&gt;
 &lt;input type="hidden" name="access_key" value="6c47e903-5bf5-4a43-a280-2a163f81e0c4"&gt;
 &lt;input type="hidden" name="subject" value="New message from fbdo.github.io"&gt;
 &lt;input type="hidden" name="from_name" value="fbdo.github.io contact form"&gt;
&lt;p&gt;&lt;label for="cf-name"&gt;Name&lt;/label&gt;
&lt;input id="cf-name" type="text" name="name" placeholder="Your name" required autocomplete="name"&gt;&lt;/p&gt;
&lt;p&gt;&lt;label for="cf-email"&gt;Email&lt;/label&gt;
&lt;input id="cf-email" type="email" name="email" placeholder="you@example.com" required autocomplete="email"&gt;&lt;/p&gt;
&lt;p&gt;&lt;label for="cf-message"&gt;Message&lt;/label&gt;&lt;/p&gt;
 &lt;textarea id="cf-message" name="message" rows="6" placeholder="What's on your mind?" required&gt;&lt;/textarea&gt;
 &lt;!-- Honeypot: hidden from humans, bots fill it and get dropped --&gt;
 &lt;input type="checkbox" name="botcheck" class="hidden" style="display:none" tabindex="-1" autocomplete="off"&gt;
&lt;p&gt;&lt;button type="submit"&gt;Send message&lt;/button&gt;&lt;/p&gt;</description></item></channel></rss>