<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Careers on Giovanni Tirloni</title><link>https://gtirloni.com/tags/careers/</link><description>Recent content in Careers on Giovanni Tirloni</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 17 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://gtirloni.com/tags/careers/index.xml" rel="self" type="application/rss+xml"/><item><title>AI and the externalization trap</title><link>https://gtirloni.com/posts/ai-and-the-externalization-trap/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://gtirloni.com/posts/ai-and-the-externalization-trap/</guid><description>&lt;p&gt;Koshy John&amp;rsquo;s recent article, &lt;a href="https://www.koshyjohn.com/blog/ai-should-elevate-your-thinking-not-replace-it/"&gt;&amp;ldquo;A.I. Should Elevate Your Thinking, Not Replace It,&amp;rdquo;&lt;/a&gt; made the &lt;a href="https://news.ycombinator.com/item?id=47913650"&gt;Hacker News front page&lt;/a&gt; and resonated with a lot of engineers. The core thesis is right: AI is splitting the profession into people who use it to think better and people who use it to avoid thinking. I agree with the analogies and the warnings about simulated competence.&lt;/p&gt;
&lt;p&gt;But John writes from an engineering management perspective. He describes what the split looks like from above. I&amp;rsquo;m a senior SRE at big tech trying to apply this advice in production. From the inside, it&amp;rsquo;s harder than it sounds because, although choosing to elevate your thinking isn&amp;rsquo;t easy, the altitude keeps changing.&lt;/p&gt;</description></item></channel></rss>