<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Training on Alexander Arvidsson</title>
    <link>/tags/training/</link>
    <description>Recent content in Training on Alexander Arvidsson</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    
    <lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/training/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>The Whiplash Effect - The Skills We Forgot We&#39;d Need</title>
      <link>/posts/whiplash-effect/</link>
      <pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/whiplash-effect/</guid>
      <description>Data sovereignty concerns - driven by the CLOUD Act and NIS2 obligations - are pushing Swedish organizations to reconsider on-premises analytics. The problem: a decade of cloud adoption has quietly eroded the skills needed to execute on-prem projects. The Microsoft stack in 2026 is more capable than most assume, but lacks a Fabric equivalent. The real decision is operational ownership, not technology preference. Organizations that can reason across the full cloud-to-on-prem spectrum will navigate the uncertainty best.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="/posts/whiplash-effect/cover.jpg" />
    </item>
    
    <item>
      <title>We&#39;ve Been Training Junior Data Engineers Wrong: Now Let&#39;s Fix It.</title>
      <link>/posts/eating-the-seed-corn-2/</link>
      <pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/eating-the-seed-corn-2/</guid>
      <description>The tech industry is cutting junior roles at record pace, calling it AI efficiency. But here&amp;rsquo;s the problem: you can&amp;rsquo;t skip a generation of practitioners and expect institutional knowledge to survive. The seniors who remain were once juniors who had space to build understanding from the ground up. That pipeline is being shut off. Part 2 is about what to do about it. How to mentor like you prompt. How to train for reasoning, not just execution - and why this might be the best time to hire juniors, not the worst.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="/posts/eating-the-seed-corn-2/cover.jpg" />
    </item>
    
    <item>
      <title>We&#39;ve Been Training Junior Data Engineers Wrong: AI Just Made It Obvious.</title>
      <link>/posts/eating-the-seed-corn-1/</link>
      <pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/eating-the-seed-corn-1/</guid>
      <description>A Wharton study put 1,372 people in front of a deliberately wrong AI. 73% followed it anyway. Not from carelessness - from fluency, confidence, and the absence of a trained skeptical reflex. We built that gap ourselves: ten years of certifications that taught procedure and skipped judgment. Now the procedures belong to agents, and the engineers we trained have no independent model to cross-check against. This is about what we teach instead - and why broken things are the best place to start.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="/posts/eating-the-seed-corn-1/cover.jpg" />
    </item>
    
  </channel>
</rss>
