<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Portfolio on Tiberiu Petre - Software Engineer</title><link>https://petretiberiu.dev/tags/portfolio/</link><description>Recent content in Portfolio on Tiberiu Petre - Software Engineer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 20 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://petretiberiu.dev/tags/portfolio/index.xml" rel="self" type="application/rss+xml"/><item><title>Sovereign AI Nexus, Part 1: Starting Small, On Purpose</title><link>https://petretiberiu.dev/posts/sovereign-ai-nexus-01-starting-small/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate><guid>https://petretiberiu.dev/posts/sovereign-ai-nexus-01-starting-small/</guid><description>&lt;p&gt;I&amp;rsquo;ve had portfolio project ideas for Backend and AI Engineering before — written at different times, each answering the same question differently: do I position myself for a specific role, or build what I find interesting and let the résumé follow?&lt;/p&gt;
&lt;p&gt;None of them got built. Not because the ideas were bad — the architectures were actually fairly detailed — but because each one tried to prove too much at once: a backend split across multiple languages &amp;ldquo;to show I know them all,&amp;rdquo; telemetry, observability, multi-agent orchestration, all in the same first version. The kind of scope that feels good on paper and turns overwhelming right when you&amp;rsquo;d need to write the first line of code.&lt;/p&gt;</description></item></channel></rss>