<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Oloodi Blog | AI, Cloud &amp; Engineering Insights</title><link>https://oloodi.com/blog/</link><description>Recent content on Oloodi Blog | AI, Cloud &amp; Engineering Insights</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 26 Jun 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://oloodi.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Wait, Is Vertex AI Gone? Making Sense of Google's AI Rebrand</title><link>https://oloodi.com/blog/making-sense-of-googles-ai-rebrand/</link><pubDate>Fri, 26 Jun 2026 09:00:00 -0500</pubDate><guid>https://oloodi.com/blog/making-sense-of-googles-ai-rebrand/</guid><description>&lt;p&gt;On client call after client call, I hear the same confusion:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;ldquo;Wait, is Vertex AI gone?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;&amp;ldquo;Is Gemini Enterprise and the Agent Platform the same thing?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;&amp;ldquo;So do I build my agent in Gemini Enterprise now, or somewhere else?&amp;rdquo;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;If you are confused by Google&amp;rsquo;s AI rebrand, you are not alone. The good news: almost nothing about &lt;em&gt;how you build&lt;/em&gt; has actually changed. What changed is the &lt;strong&gt;map&lt;/strong&gt;, not the territory.&lt;/p&gt;</description></item><item><title>My Experience as a Software Engineer in the Modern AI-Focused Development Era</title><link>https://oloodi.com/blog/ai-engineer-modern-era/</link><pubDate>Thu, 14 May 2026 09:00:00 -0500</pubDate><guid>https://oloodi.com/blog/ai-engineer-modern-era/</guid><description>&lt;p&gt;This is an article I&amp;rsquo;ve been thinking about writing for quite some time—mainly about my experience working with AI and how it has affected the way I build software.&lt;/p&gt;
&lt;p&gt;For people who don&amp;rsquo;t know me, I started my journey into software development back in my university days around 2016. Even before that, I was always interested in computers and hardware.&lt;/p&gt;
&lt;h2 id="the-pre-ai-era"&gt;The Pre-AI Era&lt;/h2&gt;
&lt;p&gt;Back then, for university projects, we used the tools available to us at the time: good old debugging, reading documentation, Stack Overflow, or some random YouTube video with less than 100 views that somehow solved the exact issue you were facing.&lt;/p&gt;</description></item><item><title>The CTO’s Dilemma: Building for Speed vs. Building for Scale</title><link>https://oloodi.com/blog/cto-dilemma-speed-vs-scale/</link><pubDate>Tue, 20 Jan 2026 09:00:00 -0500</pubDate><guid>https://oloodi.com/blog/cto-dilemma-speed-vs-scale/</guid><description>&lt;p&gt;It’s the classic startup trap.&lt;/p&gt;
&lt;p&gt;On one side, investors and sales teams are screaming for features. &amp;ldquo;Ship it now, fix it later.&amp;rdquo;
On the other side, your engineers are warning about &amp;ldquo;technical debt&amp;rdquo; and &amp;ldquo;scalability bottlenecks.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;If you ship too slow, you miss the market. If you ship too fast without structure, your product collapses under its own weight just as you start to grow.&lt;/p&gt;
&lt;p&gt;This is the &lt;strong&gt;CTO&amp;rsquo;s Dilemma&lt;/strong&gt;. And for early-stage startups that can&amp;rsquo;t afford a full-time, experienced executive, this dilemma often leads to fatal mistakes.&lt;/p&gt;</description></item><item><title>Automating SR&amp;ED: Turning Code into Tax Credits</title><link>https://oloodi.com/blog/automating-sred/</link><pubDate>Thu, 08 Jan 2026 11:15:00 -0500</pubDate><guid>https://oloodi.com/blog/automating-sred/</guid><description>&lt;p&gt;For many Canadian tech companies, the SR&amp;amp;ED (Scientific Research and Experimental Development) tax credit is a vital source of funding. Yet, preparing the claim is often a nightmare of digging through old emails, Jira tickets, and commit logs months after the fact.&lt;/p&gt;
&lt;p&gt;We realized that &lt;strong&gt;SR&amp;amp;ED compliance should be a byproduct of good engineering, not a post-mortem activity.&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id="the-shift-left-approach-to-compliance"&gt;The &amp;ldquo;Shift-Left&amp;rdquo; Approach to Compliance&lt;/h3&gt;
&lt;p&gt;With Oloodi &lt;a href="https://oloodi.com/products/studio/"




 target="_blank"
 


&gt;Studio&lt;/a&gt;, we analyze your engineering activity in real-time.&lt;/p&gt;</description></item><item><title>My Technical Manifesto: Values for a Thriving Team</title><link>https://oloodi.com/blog/my-technical-manifesto/</link><pubDate>Mon, 05 Jan 2026 09:00:00 -0500</pubDate><guid>https://oloodi.com/blog/my-technical-manifesto/</guid><description>&lt;p&gt;&lt;em&gt;Editor&amp;rsquo;s Note: I originally wrote this manifesto in 2022 on my personal blog. Today, as we build Oloodi Technologies, these values are more relevant than ever. They are the DNA of our engineering culture.&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;We often talk about corporate culture, developer culture, or the mindset of a software engineer within a team. Throughout my experiences, I’ve often faced the question: &lt;em&gt;does this person have the right mindset to join our team?&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>