<?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/><link>https://geekyschmidt.com/</link><description>Recent content on</description><image><title/><url>https://geekyschmidt.com/images/papermod-cover.png</url><link>https://geekyschmidt.com/images/papermod-cover.png</link></image><generator>Hugo</generator><language>en</language><copyright>Copyright ©2002-2026, Nicholas Schmidt; all rights reserved.</copyright><lastBuildDate>Wed, 08 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://geekyschmidt.com/index.xml" rel="self" type="application/rss+xml"/><item><title>The 20-Year Tech Debt: Why Burning Junior Talent is a Strategic Defeat</title><link>https://geekyschmidt.com/post/2026-07-06-jrdevsandai/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://geekyschmidt.com/post/2026-07-06-jrdevsandai/</guid><description>&lt;p&gt;&lt;strong&gt;BLUF:&lt;/strong&gt; If we keep burning junior talent today, we will have nobody to inherit tomorrow. The industry&amp;rsquo;s loss of patience with entry-level devs is creating a 20-year problem we are refusing to see.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="the-vanishing-entry-level"&gt;The Vanishing Entry Level&lt;/h2&gt;
&lt;p&gt;Had a good conversation with fellow geeks Fernando Covatti and Dávid Kőszeghy about AI and junior programmers as we think about talent.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Everybody is losing patience with juniors.&lt;/li&gt;
&lt;li&gt;Fair enough; they need hand-holding, they make mistakes, and they cost time.&lt;/li&gt;
&lt;li&gt;But here is the question nobody is answering: &lt;strong&gt;what happens in 20 years when the current senior engineers are retired?&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I think about this because I lived a version of it.&lt;/p&gt;</description></item><item><title>The New Fuel for the Field is Electrons</title><link>https://geekyschmidt.com/post/2026-06-29-armyevtruck/</link><pubDate>Mon, 29 Jun 2026 10:02:24 -0400</pubDate><guid>https://geekyschmidt.com/post/2026-06-29-armyevtruck/</guid><description>&lt;figure class="center"&gt;
&lt;img loading="lazy" src="https://geekyschmidt.com/assets/images/lightningairstreampower.jpg"
alt="F-150 Lightning illuminating an Airstream at night in the woods"/&gt; &lt;figcaption&gt;
&lt;p&gt;Mobile power generation in the field.&lt;/p&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;&lt;strong&gt;BLUF: The new fuel for the field is electrons, not diesel.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Having spent my career building military and ISR systems, I know firsthand that power generation is a massive bottleneck. Diesel is a logistical vulnerability—fuel convoys are targets, and traditional generators ruin noise discipline while lighting up thermal sensors. The Army developing the ISV-Heavy as a roving 60-kWh power station is a necessary shift in operational architecture.&lt;/p&gt;</description></item><item><title>The Strategic Imperative of Edge Generation</title><link>https://geekyschmidt.com/post/2026-06-28-spanishtowersbattery/</link><pubDate>Sun, 28 Jun 2026 09:58:44 -0400</pubDate><guid>https://geekyschmidt.com/post/2026-06-28-spanishtowersbattery/</guid><description>&lt;p&gt;Spain’s new mandate requiring telecom operators to maintain 4 hours of backup battery power at their transmission masts is a major victory for clean distributed energy assets at the edge of the grid.&lt;/p&gt;
&lt;p&gt;My buddy Jesse Gary was well ahead of the curve on this. Long before the current energy transition, he wasn&amp;rsquo;t advocating for deploying &lt;em&gt;new&lt;/em&gt; diesel gensets, but rather utilising our &lt;em&gt;existing&lt;/em&gt; ones as a strategic lever to supercharge investments into the clean energy space. His core argument remains absolute: any generation at the edge has usefulness, and by extracting maximum value from legacy infrastructure, we can fund and accelerate the transition to cleaner replacement assets like batteries.&lt;/p&gt;</description></item><item><title>The Danger of Abstraction: Why Deep Technical Curiosity is Still an Engineer’s Best Asset</title><link>https://geekyschmidt.com/post/2026-06-22-passiontechai/</link><pubDate>Thu, 18 Jun 2026 13:22:00 -0400</pubDate><guid>https://geekyschmidt.com/post/2026-06-22-passiontechai/</guid><description>&lt;p&gt;The year was 1997. A younger, spikey-haired version of myself was running a shiny AMD K6 processor on Debian 1.3 &amp;ldquo;Bo.&amp;rdquo; At the time, I was working at a German ISP doing UNIX System Administration. It was a trial by fire where I learned how practical networking functioned whilst supporting customers in two languages.&lt;/p&gt;
&lt;p&gt;Flipping through an issue of &lt;a href="https://en.wikipedia.org/wiki/Computer_Shopper_(American_magazine)"&gt;&lt;em&gt;Computer Shopper&lt;/em&gt;&lt;/a&gt;, I came across a DEC advertisement for their 500 MHz Alpha chip.&lt;/p&gt;</description></item><item><title>Curriculum Vitae</title><link>https://geekyschmidt.com/cv/</link><pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate><guid>https://geekyschmidt.com/cv/</guid><description>Nicholas Schmidt - Chief Technology Officer &amp;amp; Technology Leader</description></item><item><title>128GB of Local VRAM vs The Cloud: Cost Optimisation, Zero Telemetry, and What’s Possible with Local Dev Stacks</title><link>https://geekyschmidt.com/post/2026-06-15-localllmdevelopmentpebble/</link><pubDate>Sun, 14 Jun 2026 08:00:00 +0000</pubDate><guid>https://geekyschmidt.com/post/2026-06-15-localllmdevelopmentpebble/</guid><description>&lt;p&gt;Token counts, cloud subscriptions, and API rate limits are a constant drain. Beyond the monthly line items and the continuous cost optimisation of running infrastructure, the primary driver for me is data containment. Ensuring that not a single packet of proprietary code or infrastructure configuration leaks into an outbound telemetry stream to an external corporate LLM provider is a massive win.&lt;/p&gt;
&lt;p&gt;As a follow-up to my last post exploring the trade-offs of RSS feeds versus heavy-handed cloud AI agents, I decided to run an architectural experiment. Can you build a complete, functional smartwatch application end to end inside a strictly self-contained, local AI stack?&lt;/p&gt;</description></item><item><title>We Shouldn't Use Probabilistic Models to Solve Deterministic Problems: The Economics of Data Architecture</title><link>https://geekyschmidt.com/post/2026-06-13-probabilisticsolvedeterministic/</link><pubDate>Sat, 13 Jun 2026 11:45:00 -0400</pubDate><guid>https://geekyschmidt.com/post/2026-06-13-probabilisticsolvedeterministic/</guid><description>&lt;p&gt;&amp;ldquo;We Shouldn&amp;rsquo;t Use Probabilistic Models to Solve Deterministic Problems&amp;rdquo;: Why AI &amp;ldquo;Browsing Agents&amp;rdquo; Cost $281/Month to Do What a $5 VPS Can Do 📊📉&lt;/p&gt;
&lt;p&gt;I recently ran some analytics on my self-hosted Postgres database for &lt;strong&gt;Miniflux&lt;/strong&gt;, and the raw metrics tell a fascinating story about the real-world economics of data retrieval.&lt;/p&gt;
&lt;p&gt;Across my &lt;strong&gt;300 RSS feeds&lt;/strong&gt;, I am averaging exactly &lt;strong&gt;1,000 new articles every single day&lt;/strong&gt;; roughly &lt;strong&gt;30,000 articles a month&lt;/strong&gt; flowing into my reader.&lt;/p&gt;</description></item><item><title>Four Years and 65,000 Kilometres with the Ford F-150 Lightning: An Unvarnished TCO and Utility Review</title><link>https://geekyschmidt.com/post/2026-06-08-4yearslightning/</link><pubDate>Sun, 07 Jun 2026 11:00:00 -0400</pubDate><guid>https://geekyschmidt.com/post/2026-06-08-4yearslightning/</guid><description>An honest, data-driven look at living with the first-generation Ford F-150 Lightning after nearly four years, 65,000 kilometres, and heavy real-world utility use.</description></item><item><title>The Story of C++: Reflecting on Computing History and Systems Architecture</title><link>https://geekyschmidt.com/post/2026-06-06-cplusplus/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://geekyschmidt.com/post/2026-06-06-cplusplus/</guid><description>&lt;p&gt;I just finished watching CultRepo’s brilliant new documentary, &lt;em&gt;The Story of C++: The World&amp;rsquo;s Most Consequential Programming Language&lt;/em&gt;, and it sparked a lot of nostalgia.&lt;/p&gt;
&lt;p&gt;Looking back, I sometimes wish I had dove deeper into the C/C++ ecosystem early on. My own journey started with BASIC on the Commodore 64, but my career path ultimately deployed me straight into the infosec and sysadmin world. In that sector of the sandbox, tools like TCL/TK, Perl, Python, and Java became my primary operational assets.&lt;/p&gt;</description></item><item><title>Scaling the Moat: Overcoming the Talent Constraint in Domain-Driven AI Development</title><link>https://geekyschmidt.com/post/2026-06-01-ai-moat/</link><pubDate>Sun, 31 May 2026 06:10:00 +0000</pubDate><guid>https://geekyschmidt.com/post/2026-06-01-ai-moat/</guid><description>&lt;p&gt;Aaron Brethorst&amp;rsquo;s &lt;a href="https://www.brethorsting.com/blog/2026/05/domain-expertise-has-always-been-the-real-moat/"&gt;recent piece&lt;/a&gt; argues that domain expertise is the ultimate moat in an AI-driven world. He is spot on. AI has commoditised code generation, shifting the bottleneck from &amp;ldquo;can you build it&amp;rdquo; to &amp;ldquo;do you actually understand the problem well enough to know if the output is right.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;But a deep domain moat introduces a brutal operational reality: it drastically shrinks your talent pool. Finding engineers who understand high-performance architecture and niche industry nuance is like searching for a unicorn.&lt;/p&gt;</description></item></channel></rss>