<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ben Petito</title><link>http://peti.to/</link><description>Recent content on Ben Petito</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 12 Jun 2026 09:00:00 +1030</lastBuildDate><atom:link href="http://peti.to/index.xml" rel="self" type="application/rss+xml"/><item><title>My First Public Talk — What Actually Stuck With Me</title><link>http://peti.to/posts/my-first-public-talk/</link><pubDate>Fri, 12 Jun 2026 09:00:00 +1030</pubDate><guid>http://peti.to/posts/my-first-public-talk/</guid><description>&lt;p&gt;I gave my first public talk a few weeks ago. Then I spent four days proving my own point — not on the AI, on the slides.&lt;/p&gt;
&lt;p&gt;It was at the Adelaide Azure User Group. Thanks to Simon Cook from Encode Talent for the introduction and nudge to speak, and to Sam Fernando for running it. I dragged my coworker Simeon from Biz Hub along for the ride.&lt;/p&gt;
&lt;p&gt;The talk was about practical AI implementation in enterprise environments. The central theme was simple: the AI model is usually the easy part. Everything around it is where the real work happens.&lt;/p&gt;</description></item><item><title>Can a 2-Digit MFA Code Really Be More Secure Than 6?</title><link>http://peti.to/posts/mfa-2-digit-vs-6-digit/</link><pubDate>Wed, 15 Apr 2026 09:00:00 +1030</pubDate><guid>http://peti.to/posts/mfa-2-digit-vs-6-digit/</guid><description>&lt;p&gt;I had an interesting chat with a co-worker a couple of weeks ago about Microsoft&amp;rsquo;s move to use a 2-digit MFA prompt instead of the traditional 6-digit time-based code. At first glance, that sounds like a downgrade; fewer digits must mean weaker security, right? But the truth is, the mechanism behind it is very different.&lt;/p&gt;
&lt;h2 id="email-codes-and-magic-links"&gt;Email codes and &amp;ldquo;magic links&amp;rdquo;&lt;/h2&gt;
&lt;p&gt;Many applications send a one-time code or magic link to your email. While convenient, this is only as secure as your email account. If an attacker already has access to your inbox, they can trivially intercept those links and reset your password.&lt;/p&gt;</description></item><item><title>APIs Don't Fail Loudly Enough</title><link>http://peti.to/posts/apis-dont-fail-loudly-enough/</link><pubDate>Fri, 10 Apr 2026 09:00:00 +1030</pubDate><guid>http://peti.to/posts/apis-dont-fail-loudly-enough/</guid><description>&lt;p&gt;When enterprise integrations fail, they rarely fail cleanly.&lt;/p&gt;
&lt;p&gt;We inherited a system syncing financial data between a property development platform and our database. On paper, it &amp;ldquo;worked&amp;rdquo;. In reality, it was quietly dropping records and skipping certain transaction types.&lt;/p&gt;
&lt;p&gt;This is the worst kind of failure: no outage, no alert, just silent data loss over time.&lt;/p&gt;
&lt;p&gt;The bigger problem: there was no architecture or process documentation explaining how the sync worked — or was supposed to work.&lt;/p&gt;</description></item><item><title>Using AI to Surface Insights From Two Decades of Audit History</title><link>http://peti.to/posts/ai-audit-summaries/</link><pubDate>Tue, 13 May 2025 09:00:00 +0930</pubDate><guid>http://peti.to/posts/ai-audit-summaries/</guid><description>&lt;p&gt;A couple of months ago, I met with a client to explore how AI might help streamline some of their internal processes. Their application contains nearly two decades of audit history, yet despite the volume of data, it wasn&amp;rsquo;t being actively used.&lt;/p&gt;
&lt;p&gt;Last week, they reached out with a specific request: could we generate a summary of the past three years of audits so that auditors could quickly understand recurring issues and common themes when preparing for an upcoming audit?&lt;/p&gt;</description></item></channel></rss>