<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[ThoughtfulTechnologist: Root Cause]]></title><description><![CDATA[Everyone talks about the future of tech. Few talk about the consequences. ROOT CAUSE brings together senior operators. Engineers, DevOps leaders, founders, former CTOs. To dissect the real stories behind big technical decisions. What happens after the migration? After the pivot? After the AI integration? Our show is dedicated to answering what nobody tells you about scaling systems, what nobody tells you about leadership or the vicious hype cycles. If you’ve built, broken, fixed, and rebuilt systems at scale, this show is for you. Let’s root cause this.]]></description><link>https://www.thoughtfultechnologist.com/s/root-cause</link><image><url>https://substackcdn.com/image/fetch/$s_!_zaX!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2368eae1-a48b-4fd5-9b1a-f47bb24f3f91_1000x1000.png</url><title>ThoughtfulTechnologist: Root Cause</title><link>https://www.thoughtfultechnologist.com/s/root-cause</link></image><generator>Substack</generator><lastBuildDate>Mon, 16 Nov 2026 01:54:23 GMT</lastBuildDate><atom:link href="https://www.thoughtfultechnologist.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Nune Isabekyan]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[thoughtfultechnologist@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[thoughtfultechnologist@substack.com]]></itunes:email><itunes:name><![CDATA[Nune Isabekyan]]></itunes:name></itunes:owner><itunes:author><![CDATA[Nune Isabekyan]]></itunes:author><googleplay:owner><![CDATA[thoughtfultechnologist@substack.com]]></googleplay:owner><googleplay:email><![CDATA[thoughtfultechnologist@substack.com]]></googleplay:email><googleplay:author><![CDATA[Nune Isabekyan]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Three Decades in Security: Same Old Bugs, New Hype, and the Hacker Mindset]]></title><description><![CDATA[Watch now (72 mins) | Root Cause with Adrianus Warmenhoven, on the moral barriers before GenAI, hackability index, dominating GenAI market, good-old internet days and the importance of having FUN.]]></description><link>https://www.thoughtfultechnologist.com/p/three-decades-in-security-same-old-92f</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/three-decades-in-security-same-old-92f</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Tue, 10 Nov 2026 13:56:11 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/224308619/3c1d3a4d542e4e1e5caa92ef90da1f91.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>The only reason I didn&#8217;t become a hacker as a teenager, I think, was my morality. And, let&#8217;s be honest, being danger averse. That was before I learned that hacking mostly means understanding how systems work. Taking a thing apart piece by piece and putting it back together, until you&#8217;re confident you can improve it if you need to, or break it if you want to. By that definition, I became one.</p><p>One of the people who got me there is Adrianus Warmenhoven. I met him at BarCamp Yerevan when I was a student, and he was one of the people we looked up to, a reference that what we were doing could go somewhere. He built one of the first internet businesses in the Netherlands in 1993. He ran a free ISP for ING in the late nineties with a crew of fifteen, and put a satellite internet link into Tanzania. Then came decades in security: evangelist at Bitdefender, CISO at Tesorion, defensive strategist at Nord Security. He holds around ten US patents and taught a university class literally called Hack Everything. One recommendation on his profile says you may not agree with this man, but if you don&#8217;t at least listen, it will be your detriment.</p><p>So we listened. I came in grumpy about the state of things and hoping we&#8217;d find a more positive outlook together. We did, eventually. Getting there took a detour through some dark places.</p><h2>The same old bugs</h2><p>Adrianus recently joined the Guild of the Grumpy Old Hackers, a group of peers, mostly Gen X. Most of them are really affable people. The grumpiness comes from watching the same mistakes get redone in every hype cycle. New technology arrives, and the same old bugs and the same old vulnerabilities come back with it.</p><p>I asked whether AI is any different. His answer started with the internet itself. It was built to share information. Telnet, almost no security, no firewalls, and it went fine for a couple of years. Then people started making money with it, and the moment money is involved, there are people trying to get some of it in less nice ways. So security was added afterwards: SSH, SSL, TLS. It never slowed development down.</p><p>The same thing is happening with AI. He compares it to the arrival of home improvement stores. Everyone thought it was the end of contractors, because now anyone could go and get the wood. What actually happened was more accidents, a lot of shoddy work, and the contractors are still in business. Vibe coding an app that organizes your files is fine. A service for other people brings resource starvation, lock congestion and memory pressure, terms nobody has heard of when they start vibe coding. So they don&#8217;t mention them to their AI, and the AI doesn&#8217;t take them into account.</p><h2>The engineer who said no</h2><p>This is the part of the conversation I didn&#8217;t see coming.</p><p>Adrianus calls AI the most inefficient programming language humanity has ever invented, and also the most flexible one. When I asked why it&#8217;s being abused so much, he pointed at something I had never thought about. My &#8220;problem&#8221; with AI is not really a technological one. It&#8217;s an ethical one.</p><p>Until a couple of years ago, anyone who wanted to build software that manipulates people, tracks everything and squeezes money out of them had to find like-minded developers first. That was a small barrier, and it held back a lot of people, because a lot of engineers are pretty ethical. If you found one, it meant a lot of other people didn&#8217;t find that one.</p><p>Now they don&#8217;t need anybody. They can sit down for a week, have servers running, and nobody will tell them &#8220;we shouldn&#8217;t do this&#8221; or &#8220;we shouldn&#8217;t track somebody.&#8221;</p><blockquote><p>&#8220;There&#8217;s no backtalk on any of the bad moral decisions.&#8221;</p></blockquote><p>The morality of the engineer was a barrier nobody designed. And it&#8217;s gone.</p><h2>Nobody cares about your local harness</h2><p>I pushed back with the question a lot of engineers are asking. Doing things right usually means doing them slowly, and the local models don&#8217;t match the speed and quality of the proprietary ones. So what can people do?</p><p>&#8220;I&#8217;m not happy to give this answer, but the answer is not a lot.&#8221; In the old days, a web server behind Cloudflare put him on equal footing with any enterprise online. With AI, there is nothing a person or a small company can buy or rent that does the same against racks and racks of H200s.</p><p>He thinks the current pricing is a startup strategy with an extremely large venture capitalist behind it: shape the field so competitors can&#8217;t follow, the way Netflix did. And the target isn&#8217;t us. It&#8217;s large enterprises, governments and militaries, hooked on one ecosystem the way they got hooked on Microsoft Office. If the two of us ran a local model and earned 10,000 euros a month with it, he says, they couldn&#8217;t care less.</p><h2>Crickets</h2><p>I used to tell people not to share their birthday online. Now people hand their mental health, where they live and what they eat to companies that are a few years old. Adrianus is beyond worried. He&#8217;s flabbergasted. A leak of ten thousand records from a company makes the news and people get angry. A week later there&#8217;s an article about 100,000 leaked AI chats. Crickets.</p><p>His explanation is the &#8220;does this benefit me&#8221; equation. The risk isn&#8217;t immediate and you can&#8217;t see it. The benefit, the answer from the AI, is right there. And from his work on NordVPN&#8217;s security advisory board he knows the risk doesn&#8217;t expire. Aggregated data sets on the dark web contain small nuggets about him that haven&#8217;t been online for ten or fifteen years. Once it&#8217;s online, it finds its way to your profile, and deleting it later doesn&#8217;t matter anymore.</p><p>Then he talked about undress apps, and about what it takes to build one, train it, and ship it, and why nobody is picking up pitchforks. I&#8217;ll let you hear that part in his words.</p><h2>Locks buy you time</h2><p>I dug out an article Adrianus wrote in 2015, where he named abundance as the root cause of security problems: we push out far more code than there are people who can secure it. I asked whether security is now catching up with the amount of code.</p><p>On the defender side, he says, there are leaps and bounds. Scanning code and reasoning about it got much faster. But he also ran a few tests on the money side, and by his estimate it&#8217;s now five to seven thousand times cheaper to produce new code than to review it. For most code, unless it&#8217;s critical, nobody will pay for that review, not even with AI.</p><p>So we&#8217;re where physical locks are. A lock never promises that no burglar gets in. Read the rating and it says how long it resists an attack. Half an hour, maybe. When a former chief of the Dutch intelligence service started a cybersecurity company, one of the first things he did was buy cyber insurance. Adrianus took that as telling. Someone with that much inside knowledge doesn&#8217;t believe you can defend everything either. Security is now partly an insurance question, and you pick your battles: what is critical, and what are you willing to let break.</p><h2>It&#8217;s just data</h2><p>This was the part that shifted something for me. Targeting used to start with a company: they&#8217;ve got money, let&#8217;s try to hack them. Now it runs the other way. It starts with a cookie. An ad network sees the same cookie on website A and website B. A data leak puts your email address on a dating site. The profile grows, gets sold on the dark web, enriched, and sold again, until it&#8217;s big enough to point at places where your data is vulnerable. Then it gets picked automatically.</p><blockquote><p>&#8220;You will be automatically selected without the criminal ever knowing anything really about you. It&#8217;s just data.&#8221;</p></blockquote><p>I called it a hackability index. Once you reach critical mass, you just get hacked. He liked the term, and then explained how the Shodan part of it works.</p><h2>The opposite of a zip file</h2><p>I grew up with the internet of the nineties, a place a million times bigger than a library, where you could reach people who knew things and actually talk to them. The day before we recorded, I saw a musician who is entirely AI-generated, with a Spotify account and thousands of followers. So I asked whether the internet is dying.</p><p>In its current form, maybe. Adrianus described the report pipeline we&#8217;ve all seen. Someone has a few facts, asks the AI for a nice one-page report with diagrams, and sends it to their manager. The manager doesn&#8217;t want to read a full page and asks the AI to summarize it. We&#8217;re doing the opposite of zip files.</p><p>He also watches Reddit, Hacker News and Quora with his own bot detectors. The &#8220;your pet&#8217;s name plus the last thing you ate&#8221; posts we&#8217;ve all scrolled past are engagement bait, there to get more information out of people. Then he took it somewhere I didn&#8217;t expect: a 15-minute bike tire repair, and why skipping it explains the subscription economy. If he wrote his 2015 article again today, he says, the root cause would be convenience.</p><h2>Iron Man in the cave</h2><p>There is a positive outlook, and Adrianus didn&#8217;t make me wait too long for it. LLMs might be the final interface between people and computers. He already codes by voice sometimes. And outside the corporate sphere, people are building again. The Internet Archive takes in about a petabyte every ten days and stores it the old-school engineering way. And this year&#8217;s DEF CON badge carried bunnie Huang&#8217;s open source chip, which anyone can download, inspect and build on, in the hands of thousands of attendees.</p><p>That&#8217;s why he&#8217;s cautiously optimistic. Cautiously, because most of humanity will stay with the short videos and the dopamine. His advice is not to look at them, and to look at the hacker communities instead. That&#8217;s where people are figuring out how to build things themselves, how to protect the people they love, and what happens if the internet breaks.</p><p>The difference between a hacker and a security professional, in his talks, comes down to two Marvel pictures: Iron Man in the cave and War Machine. Which one he identifies with, and why the security boom didn&#8217;t produce more of the first, is worth hearing in his own words.</p><p>And when I asked how he lives with knowing how all of this works, the answer was simpler than I expected. You&#8217;ll hear it near the end.</p><p>He also has book recommendations: one he calls not very positive but important, which most people only know from the movie, and the cyberpunk he thinks people have forgotten the meaning of. Markus&#8217;s question from the previous episode, about what grounds you, got an answer I recognized. His question for the next guest is on the cover of this episode.</p><p>Find Adrianus at <a href="https://www.warmenhoven.co/">warmenhoven.co</a>, on <a href="https://www.linkedin.com/in/adrianuswarmenhoven/">LinkedIn</a>, and if you&#8217;re serious, on <a href="https://mentorcruise.com/mentor/AdrianusWarmenhoven/">MentorCruise</a>. In his own words: friendly, yes. Easy, no.</p><p></p>]]></content:encoded></item><item><title><![CDATA[Adopting Kubernetes, Then AI: Who Ends Up Running It?]]></title><description><![CDATA[Root Cause with Markus D&#246;pke, on when you don&#8217;t need Kubernetes, platform teams that become magnets, and a driving license for AI agents]]></description><link>https://www.thoughtfultechnologist.com/p/adopting-kubernetes-then-ai-who-ends-90a</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/adopting-kubernetes-then-ai-who-ends-90a</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Tue, 27 Oct 2026 07:50:04 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/222303498/3c14a1d9fcba8f76f6073e020b89318c.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>This episode is for a very specific person. You&#8217;re a manager inside a fairly large company, and someone, possibly you, has decided you&#8217;re adopting Kubernetes. AI is right behind it. Do you restructure the teams first? Hire consultants? Do you need any of this? And every person you ask for a straight answer turns out to be selling something.</p><p>I wanted an answer from someone who isn&#8217;t. Markus D&#246;pke is a senior solutions architect at AWS in Germany, and his job means he sees more production Kubernetes than most engineers see in a career. The inside of the clusters, the inside of the org charts, and the inside of the postmortems. We&#8217;ve worked together, and what stands out to me isn&#8217;t the title or the talks. He wants to understand, he wants to help, and he shares what he knows. That&#8217;s rarer than it should be.</p><p>So I started at day zero. A large enterprise decides it needs Kubernetes, and Markus gets the call. How did they get there?</p><h2>Back to virtual machines</h2><p>Markus&#8217;s first answer was that Kubernetes is so ubiquitous that there&#8217;s no single story. Look long enough and you&#8217;ll find a five-person carpenter shop somewhere in a Bavarian village running WordPress on it. But in the engagements where it was justified, the customer always wanted to scale something. A software company moving from perpetual licenses to SaaS. A company entering a new geography that doesn&#8217;t want to hire for a follow-the-sun model. A team that needs to experiment faster than its book of standards allows.</p><p>Then I asked where the decision usually comes from. Ideally from business goals, he said, with the tech people confirming the fit. But resume-driven development isn&#8217;t a cliche someone made up. Delegate the choice entirely to the engineering org, and the probability that you end up with Kubernetes goes up.</p><p>He shared a story where it wasn&#8217;t justified. A small German software company, talked into Kubernetes by a delivery partner who never looked at the whole picture. After a year the budget ran out, the product team had to take over something they hadn&#8217;t asked for, and a year after that management pulled the plug. Back to virtual machines. Markus&#8217;s take: the same time and money, spent on doing VM deployments well, would have solved the actual problem.</p><h2>An organization is not a university</h2><p>If you&#8217;ve rightfully decided on Kubernetes, is the next step a platform team? Markus&#8217;s warning is that you shouldn&#8217;t take the nerdiest people you have, let them build a platform, and have everyone throw their things on top. That&#8217;s unlikely to work.</p><p>What he recommends instead comes from Team Topologies, and he summarized the book in about two minutes, better than any AI would. There are four team types, and only one you really need to understand: the stream-aligned team, which creates the value in your organization, full stop. Every other team exists to remove its bottlenecks. The platform team looks at the value chain, finds where the stream-aligned teams aren&#8217;t self-sufficient, and builds self-service for that. The enablement team teaches people how to work with it. And the complicated subsystem team owns the legacy API nobody else should have to understand. (Give that one an MCP server, he suggests, and it becomes part of the platform.)</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!Wnq1!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36347358-0eb2-4776-8e21-12001520192e_900x1000.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!Wnq1!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36347358-0eb2-4776-8e21-12001520192e_900x1000.png 424w, https://substackcdn.com/image/fetch/$s_!Wnq1!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36347358-0eb2-4776-8e21-12001520192e_900x1000.png 848w, https://substackcdn.com/image/fetch/$s_!Wnq1!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36347358-0eb2-4776-8e21-12001520192e_900x1000.png 1272w, https://substackcdn.com/image/fetch/$s_!Wnq1!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36347358-0eb2-4776-8e21-12001520192e_900x1000.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!Wnq1!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36347358-0eb2-4776-8e21-12001520192e_900x1000.png" width="900" height="1000" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/36347358-0eb2-4776-8e21-12001520192e_900x1000.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1000,&quot;width&quot;:900,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:101446,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.thoughtfultechnologist.com/i/222303498?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36347358-0eb2-4776-8e21-12001520192e_900x1000.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!Wnq1!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36347358-0eb2-4776-8e21-12001520192e_900x1000.png 424w, https://substackcdn.com/image/fetch/$s_!Wnq1!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36347358-0eb2-4776-8e21-12001520192e_900x1000.png 848w, https://substackcdn.com/image/fetch/$s_!Wnq1!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36347358-0eb2-4776-8e21-12001520192e_900x1000.png 1272w, https://substackcdn.com/image/fetch/$s_!Wnq1!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F36347358-0eb2-4776-8e21-12001520192e_900x1000.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>I pushed on the part that worried me. Over time the platform team understands the platform and the product team understands the product, and the gap between them grows. Isn&#8217;t that a risk?</p><blockquote><p>&#8220;An organization is not a university.&#8221;</p></blockquote><p>Some focus, some bounded context, is the price of flow. The product team shouldn&#8217;t be as deep in the Kubernetes trenches as the people operating the cluster. But the platform team&#8217;s mission is to support them, so they have to sit together, and the product teams have to take some ownership of the interfaces, because the poor people in the platform team are usually underfunded.</p><p>That led us to AI. Everyone is worried that AI creates knowledge gaps. I think those gaps existed long before AI in any large organization, in every team that maintained code it never saw written. Markus&#8217;s answer was a framing I liked on the spot: be explicit about where you dive deep and what you take for granted. We&#8217;ve been booking managed services for years. The question is whether the thing is differentiating for your business, and whether you can learn it when you need to. He also pointed out that these are words that can age very badly. We don&#8217;t know what happens in two weeks.</p><h2>Mental load, not access rights</h2><p>I asked whether a platform team cancels &#8220;you build it, you run it.&#8221; Markus answered with a story from his time as CTO of a SaaS startup. The company said it followed that model. When he joined, there was a hard cut between development and operations, and the reason wasn&#8217;t access rights. The developers had far too many of those. The reason was that doing anything in production was too much mental load for a vanilla Java developer, so outages were frequent and recovery was slow.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!BTuW!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff5353735-4069-4da0-9eea-0268c7d3b64c_900x1000.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!BTuW!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff5353735-4069-4da0-9eea-0268c7d3b64c_900x1000.png 424w, https://substackcdn.com/image/fetch/$s_!BTuW!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff5353735-4069-4da0-9eea-0268c7d3b64c_900x1000.png 848w, https://substackcdn.com/image/fetch/$s_!BTuW!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff5353735-4069-4da0-9eea-0268c7d3b64c_900x1000.png 1272w, https://substackcdn.com/image/fetch/$s_!BTuW!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff5353735-4069-4da0-9eea-0268c7d3b64c_900x1000.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!BTuW!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff5353735-4069-4da0-9eea-0268c7d3b64c_900x1000.png" width="900" height="1000" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/f5353735-4069-4da0-9eea-0268c7d3b64c_900x1000.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1000,&quot;width&quot;:900,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:122958,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.thoughtfultechnologist.com/i/222303498?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff5353735-4069-4da0-9eea-0268c7d3b64c_900x1000.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!BTuW!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff5353735-4069-4da0-9eea-0268c7d3b64c_900x1000.png 424w, https://substackcdn.com/image/fetch/$s_!BTuW!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff5353735-4069-4da0-9eea-0268c7d3b64c_900x1000.png 848w, https://substackcdn.com/image/fetch/$s_!BTuW!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff5353735-4069-4da0-9eea-0268c7d3b64c_900x1000.png 1272w, https://substackcdn.com/image/fetch/$s_!BTuW!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff5353735-4069-4da0-9eea-0268c7d3b64c_900x1000.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>What he did about it was one of the simplest building blocks of their platform, and it involves an oil rig. I&#8217;d rather you hear that one from him.</p><h2>It&#8217;s a platform group</h2><p>My next worry: platform teams become a magnet. &#8220;Can you take care of this? You&#8217;re the platform team.&#8221; Markus&#8217;s answer is that the term is misleading. It&#8217;s a platform group. The moment you add an identity provider, database optimization, GPU management for fine-tuning, that&#8217;s a different part of the organization joining the platform, not three more things dropped on the same four people until they burn out.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!zRqO!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fedf246e5-212b-4db4-9ab6-f998e39ba7d6_900x1000.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!zRqO!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fedf246e5-212b-4db4-9ab6-f998e39ba7d6_900x1000.png 424w, https://substackcdn.com/image/fetch/$s_!zRqO!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fedf246e5-212b-4db4-9ab6-f998e39ba7d6_900x1000.png 848w, https://substackcdn.com/image/fetch/$s_!zRqO!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fedf246e5-212b-4db4-9ab6-f998e39ba7d6_900x1000.png 1272w, https://substackcdn.com/image/fetch/$s_!zRqO!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fedf246e5-212b-4db4-9ab6-f998e39ba7d6_900x1000.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!zRqO!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fedf246e5-212b-4db4-9ab6-f998e39ba7d6_900x1000.png" width="900" height="1000" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/edf246e5-212b-4db4-9ab6-f998e39ba7d6_900x1000.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1000,&quot;width&quot;:900,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:105274,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.thoughtfultechnologist.com/i/222303498?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fedf246e5-212b-4db4-9ab6-f998e39ba7d6_900x1000.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!zRqO!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fedf246e5-212b-4db4-9ab6-f998e39ba7d6_900x1000.png 424w, https://substackcdn.com/image/fetch/$s_!zRqO!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fedf246e5-212b-4db4-9ab6-f998e39ba7d6_900x1000.png 848w, https://substackcdn.com/image/fetch/$s_!zRqO!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fedf246e5-212b-4db4-9ab6-f998e39ba7d6_900x1000.png 1272w, https://substackcdn.com/image/fetch/$s_!zRqO!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fedf246e5-212b-4db4-9ab6-f998e39ba7d6_900x1000.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>And on justifying a team that doesn&#8217;t ship features: add a vocal person. A product manager for the platform who does the internal marketing and owns the KPIs, and maybe developer advocates showing how much faster the product teams move because of it. Markus sees the willingness to fund this growing, for one reason. Unless your AI is a chatbot answering questions about the product, you&#8217;re building a system that can manipulate state in your systems. Companies that never had a platform initiative are starting one for that.</p><h2>&#8220;We bought Claude Code subscriptions&#8221;</h2><p>That&#8217;s the sentence I keep hearing from engineering managers, followed by &#8220;so we&#8217;ve adopted AI.&#8221; I asked Markus whether that&#8217;s enough.</p><blockquote><p>&#8220;You cannot expect to simply buy a tool, throw it over the fence and everyone in the organization figures out how to use it the right way.&#8221;</p></blockquote><p>There are different implementations of an AI development lifecycle, from on-demand help in the IDE to loops that build the product with little human involvement, and you have to decide where you want to go before you decide how to get there. I grouped the companies I see into three buckets: bought a subscription, integrated AI into the IDE, and building a pipeline that works instead of developers. Then I asked whether he knows anyone actually in the third bucket. His answer involved a conference talk we both sat in and a prediction he made about me that turned out to be true.</p><p>My own position hasn&#8217;t changed. If someone tells you they know exactly how to integrate AI into your SDLC, they&#8217;re selling you something. We haven&#8217;t had the time as an industry to figure it out.</p><p>Markus&#8217;s idea for operations is a driving license for AI agents in production. The more you know about the system, the more autonomy the agent gets. If you&#8217;re just starting, give it read access and let it teach you. In the end it&#8217;s running kubectl and correlating with your observability stack, and if you pay attention, you learn how to approach problems in production. What he thinks of YOLO mode, you can guess.</p><h2>What you would have told your juniors</h2><p>We didn&#8217;t plan to talk about juniors, but we&#8217;d been texting about it. Markus told me about a friend, a project manager at an insurance company, who has stopped hiring juniors because he can prompt the agent himself and check the outcomes. Markus asked him whether that&#8217;s how he wants to spend the next five years. What you&#8217;re prompting is more or less what you would have told your juniors to do, and you&#8217;re still checking the outcomes. Not much changed. The work will change, but there will be junior tasks in the future too.</p><p>Markus also has a book recommendation, and it isn&#8217;t a technical one. John Gallagher&#8217;s question from the previous episode, about the most powerful emotion you feel, got the parent&#8217;s answer first and then a second answer that taught Markus to unlearn something. That part turns into the case for why achievements deserve to be celebrated, even the small ones inside a large German enterprise. His question for the next guest involves bees.</p><p>&#127909; <a href="https://youtu.be/ECSbMqdOl-4">Watch on YouTube</a> &#183; &#127911; <a href="https://open.spotify.com/episode/08SwEIBGCSnPIdcfBCyQGO">Spotify</a> &#183; &#127822; <a href="https://podcasts.apple.com/us/podcast/adopting-kubernetes-then-ai-who-ends-up-running-it/id1896559098?i=1000798314395">Apple Podcasts</a></p><p>Find Markus on <a href="https://www.linkedin.com/in/m9e/">LinkedIn</a>.</p>]]></content:encoded></item><item><title><![CDATA[If everyone can build software, what decides who survives?]]></title><description><![CDATA[Watch now (87 mins) | Root Cause with John Gallagher, on culture, feature factories, and a 2 MB game on a 1.5 MB Amiga]]></description><link>https://www.thoughtfultechnologist.com/p/if-everyone-can-build-software-what-753</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/if-everyone-can-build-software-what-753</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Tue, 13 Oct 2026 13:47:01 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/220201546/32f25811a988e108dbc1321d1b6994bc.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>The market is full of tools right now, and most of them have AI in them. Most of them won&#8217;t survive. That was the question I brought to John Gallagher: if anyone can build software now, what actually decides who makes it?</p><p>He said culture. That word can mean almost anything, so most of this episode is me trying to find out what he means by it.</p><p>John has been writing software since 1998, when I was nine. Assembly on microcontrollers, then iOS, then more than a decade of Rails in production. Today he&#8217;s a principal engineer at Dynatrace and the author of Software Design Simplified. At one of his previous companies he lived through the incident we&#8217;ve all had: the app is down, the people who could help are asleep in another time zone, and the logs tell you nothing. He spent the next eighteen months changing how his team saw its own system. Downtime dropped 98%. Then he turned around and cut the observability bill all that new enthusiasm had created.</p><h2>2,000 engineers with AI are still 2,000 engineers</h2><p>I started close to home. The AI SRE space is suddenly crowded, and I wanted to know whether that&#8217;s AI making it easier to build, or something that started earlier. John&#8217;s answer was OpenTelemetry. Before it, a handful of big vendors held the market, and switching meant ripping out their proprietary instrumentation and learning a whole new set of screens. OTel made the instrumentation portable, and the startups followed. The lock-in didn&#8217;t disappear, though. It moved into the dashboards and the two hundred alerts you set up by hand. He told me about a team that switched vendors and found 90% of the cost was in the accumulated cruft, not the instrumentation.</p><p>Then the question I actually wanted to ask. Startups used to win on speed. If AI makes the big companies fast too, what&#8217;s left for the small ones?</p><p>John works with 2,000 engineers. When he joined, he assumed that was the whole company. It&#8217;s 5,000 people. He says AI is massively changing how fast they move. And yet.</p><blockquote><p>&#8220;It&#8217;s a speed up, but it&#8217;s not the same kind of speed up.&#8221;</p></blockquote><p>Conway&#8217;s law didn&#8217;t get repealed. The structure of the teams still shapes the structure of the product, and the number of communication paths in a company that size lives in a different universe from a team of twelve. Big companies also sell something no startup can: we&#8217;ll still be here in ten years. His comparison was jazz and prog rock. Two genres, not a better and a worse.</p><h2>&#8220;We know what the customer wants&#8221;</h2><p>This part was uncomfortable to listen to, because I recognized myself.</p><p>John stays at a company three or four years, because that&#8217;s roughly how long it takes for your own bad design decisions to come back and bite you. (With AI, he says, more like four months.) Across every company he&#8217;s been at, small or large, one anti-pattern refuses to die: resistance to talking to customers. Are you using the product? No. Are you paying five figures for it? No. But we know what it needs, because we made it.</p><p>I suggested it&#8217;s ego. People who build things are creative, and it&#8217;s hard to let other opinions near the thing that exists in your head. John agreed, then made it more complicated. A founder needs that ego. Nobody gets a company off the ground by collecting feedback from a hundred thousand people first. He brought up a Radiolab episode about top athletes being excellent liars to themselves. So you have to be selfish enough to start a company and humble enough to remember you&#8217;re solving somebody else&#8217;s problem. Both at once. I&#8217;m still working on the second half.</p><h2>A software company is not a factory</h2><p>So if culture isn&#8217;t just customer obsession, what is it? First, John wants to put one myth to bed: that the best product wins. The best marketed product that solves the right pain at the right time wins, and luck does a lot of the work. Culture is something else. How people treat each other, and what mental model the company holds of what software even is.</p><p>The model he can&#8217;t stand is the factory. We stamp out features like tin cans, and more features make a better product.</p><blockquote><p>&#8220;If we went into every piece of software and deleted the 80% of features that people rarely use, the software would be better. Undeniably better.&#8221;</p></blockquote><p>Try that with a TV manufacturer and see what happens to sales. This is also why he thinks AI made culture about ten times more important. When a product manager can prototype a feature in an afternoon, the interesting question becomes what stops it from going straight to production. That&#8217;s not a tooling question.</p><h2>Hired Guns</h2><p>Then we got nostalgic. I asked whether the AI shift compares to the shift from physical products to software, which I never lived through. I was born into a world that already had computers. John was born in 1976, into a household where an Amiga cost more than anyone could explain, and his parents found the money anyway.</p><p>The game was Hired Guns. Six floppy disks, and the box said you needed 2 MB of memory. Their Amiga had 1.5. No internet, no manual, no one to ask. He started deleting library files from the operating system one at a time to see what still booted. Hours of it. His brothers told him to let it go. I won&#8217;t spoil the ending, but it&#8217;s where his love of programming started, and he still remembers the intro music.</p><p>People like to say the human brain learns like an LLM, from a lot of data. This story is the opposite. One problem you care about too much teaches you patience, experimenting, verifying. Most of what makes an engineer.</p><h2>Did we waste a year?</h2><p>I asked him something I&#8217;ve been asking myself. I&#8217;ve spent the last year or two trying every new tool, partly so I can argue about the hype from actual experience. And I keep circling back to the same place: things changed, and the fundamentals didn&#8217;t. Should I have spent that year on resilience engineering or residuality theory instead?</p><p>His answer: no learning is wasted, certainly not compared to scrolling your phone, which he admits he&#8217;s done plenty of lately. Then he passed on the advice Jeff Bezos gave 37signals: invest in things that don&#8217;t change. For John that&#8217;s testing, design, and feedback loops at every level of an organization. He also says all his priors are gone. The other day he caught himself rearranging a GitHub issues board by hand.</p><p>My favorite part is about being wrong. He&#8217;s paired with engineers who were certain the bug was a race condition in Redis. The first experiment supports it. So does the second. The third doesn&#8217;t. By the fourth it has nothing to do with Redis, and that&#8217;s the moment you find out how someone handles being wrong.</p><h2>Don&#8217;t read a book</h2><p>My last real question was for people who never had a science education or a childhood of hacking. Is it too late to learn critical thinking? His recipe has three ingredients: obsession, a small feedback loop, and for goodness sake, don&#8217;t read a book. Reading about critical thinking is like reading about tennis. Go get a racket.</p><p>He also thinks your own emotions are a feedback loop, and that group think starts with somebody&#8217;s feeling, not their argument. There&#8217;s a painting class and a tennis court in that part of the conversation, and I&#8217;d rather you hear them from him.</p><p>He also kept his promise about a book recommendation, which I asked him not to reveal before we hit record. And Tamanna&#8217;s question from the previous episode, about which pet he&#8217;d have, found exactly the wrong recipient.</p><p>&#127909; Watch on <a href="https://youtu.be/rF5ILZusm7U">YouTube</a> &#183; &#127911; <a href="https://open.spotify.com/episode/7yaCyvuIwBkskVGowjVMxE?si=bbf57199975342e7">Spotify</a> &#183; &#127822; <a href="https://podcasts.apple.com/us/podcast/if-everyone-can-build-software-what-decides-who-survives/id1896559098?i=1000796143932">Apple Podcasts</a></p><p>Find John at <a href="https://www.joyfulprogramming.com">joyfulprogramming.com</a> and on <a href="https://linkedin.com/in/synapticmishap">LinkedIn</a>.</p>]]></content:encoded></item><item><title><![CDATA[Nine guests, one chain, ten minutes]]></title><description><![CDATA[Every guest leaves a question for the next one]]></description><link>https://www.thoughtfultechnologist.com/p/nine-guests-one-chain-ten-minutes</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/nine-guests-one-chain-ten-minutes</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Tue, 06 Oct 2026 14:33:02 GMT</pubDate><enclosure url="https://substackcdn.com/image/youtube/w_728,c_limit/h0pCJ9KynTE" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>There is a small ritual at the end of every Root Cause episode. The guest doesn&#8217;t get to leave until they ask a question. They don&#8217;t ask me. They ask the next guest, whoever that turns out to be. And the next guest has to answer it on air before they get to ask their own.</p><p>I started it as just a fun idea. It turned into the most honest five minutes of every episode, because nobody prepares for it, not even me. The guest has spent an hour being the expert. Then a stranger&#8217;s question lands and they have to just be a person for a minute.</p><p>So I cut the whole chain together. Nine guests, in the order the questions actually travelled. <a href="https://www.thoughtfultechnologist.com/p/the-root-cause-why-the-experts-stay">Marc Babin</a> opened it without knowing where it would go.</p><div id="youtube2-h0pCJ9KynTE" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;h0pCJ9KynTE&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/h0pCJ9KynTE?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><p>If you&#8217;d rather read than watch, here is the whole chain: every question, and what the next person did with it.</p><div><hr></div><h2>&#8220;What did you learn this week that you didn&#8217;t share with others?&#8221;</h2><p><em>Marc Babin asks. Adrian Hornsby answers.</em></p><p>Adrian spent nine years at AWS as a principal engineer on the team that built its chaos engineering service. Then he left, founded <a href="https://resiliumlabs.com/">Resilium Labs</a>,  a consultancy helping organizations build genuine resilience - both technical and cultural. He&#8217;s also the author of a book called <a href="https://leanpub.com/whywestillsuckatresilience">Why We Still Suck at Resilience</a>. Helping organizations survive the things nobody plans for is his field. </p><p>What he said was that he is still scared. On the day we recorded, he had open sourced a project he built together with Claude - <a href="https://github.com/adhorn/resilience-companion">resilience companion</a>. Every other repository he has published was written entirely by him, without AI, and it took him quite some time to feel comfortable putting this one out. What he learned that week was about himself: the fear of exposing your work never fully goes away.</p><blockquote><p>Even after 20 something years in IT, you can still be scared of posting something online.</p></blockquote><p>He extended it to everything that involves showing up in public. Being on a podcast, sharing ideas, writing a book. All of it is exposure, and all of it is scary. He does it anyway.</p><p>Full conversation with Adrian: <a href="https://www.thoughtfultechnologist.com/p/the-root-cause-of-never-learning">The Root Cause of Never Learning</a></p><h2>&#8220;What surprised you the most in the discipline you were the most comfortable with?&#8221;</h2><p><em>Adrian Hornsby asks. Ia Mg answers.</em></p><p>Ia is an engineer and a former computer science teacher, so she has watched a lot of people meet engineering for the first time. Her answer: the surprise is how different engineering is from what it looks or sounds like from the outside.</p><p>The stereotype says you sit down, write a lot of code, and that&#8217;s the fun. The real thing takes social skills, cooperation, and a good amount of humility. Real projects come with barriers that have nothing to do with syntax. And she doesn&#8217;t describe those as the tax you pay to get to the fun part. Learning to work with those barriers, and to confront them, is its own kind of fun.</p><p>Full conversation with Ia: <a href="https://www.thoughtfultechnologist.com/p/the-root-cause-of-wanting-to-learn">The Root Cause of Wanting to Learn</a></p><h2>&#8220;If you had to start your career or pick a major right now, would it be different? What would it be, and why?&#8221;</h2><p><em>Ia Mg asks. Orel Zilberman answers.</em></p><p>Orel is a solo builder who has lived the before, during and after of AI tooling. If anyone had a reason to say &#8220;skip the degree&#8221;, it would be him.</p><p>He wouldn&#8217;t change a thing. Yes, you can build a lot with AI now. But in his view AI is not taking over the whole sector, not yet and not anywhere in the near future, and he has heard enough confident predictions from very famous people about the end of software development jobs to stop being impressed by them.</p><blockquote><p>I wouldn&#8217;t change my major and I would do exactly what I did.</p></blockquote><p>Full conversation with Orel: <a href="https://www.youtube.com/watch?v=xh4F80Fu458">Root Cause of Solopreneur Success: Before, During, and After AI</a></p><h2>&#8220;What is the one thing you would tell yourself at the start, that you know now?&#8221;</h2><p><em>Orel Zilberman asks. Eric Lubow answers.</em></p><p>Eric has more than twenty years of technology leadership behind him, and he did not reach for career advice.</p><p>He said that when he was younger he did not spend nearly enough time understanding himself through the lens of other people. That gap was a small problem in his professional life and a huge one in his personal life. He wishes emotions, emotional communication and self-awareness had simply been part of growing up. For him they weren&#8217;t.</p><blockquote><p>I&#8217;ve had to learn that the hard way, through many lost relationships that I wish I did not lose.</p></blockquote><p>Full conversation with Eric: <a href="https://www.youtube.com/watch?v=Uv988vzRWOA">Root Cause of a Healthy Team</a></p><h2>&#8220;What is the most benign thing you&#8217;re proud of and never get to talk about?&#8221;</h2><p><em>Eric Lubow asks. Barry O&#8217;Reilly answers.</em></p><p>Barry thinks about software architecture at a level where mathematics and philosophy show up. His answer showed us his human side for a second.</p><p>When he decides to do something, he goes all in. He lives in Sweden, where the water freezes in winter and you can&#8217;t fish, so he spends the cold months on a football pitch in the snow, practising distance casting. He currently throws just over 34 meters of fly line. The world champion, by his estimate, throws somewhere between 37 and 44. Getting there cost him a visit to the physiotherapist, a shoulder and a terrible tennis elbow. He plans to spend the whole summer doing it on lakes in northern Sweden and Norway.</p><p>And the reward, in his words: when you can cast like that, a collection of old men gathers on the bridge to watch you and go &#8220;Ooh!&#8221;.</p><p>Full conversation with Barry: <a href="https://youtu.be/EGwcEQPX-lM">Root Cause of Architectural Thinking</a></p><h2>&#8220;Sent back to 1822, into a room with Charles Babbage and Ada Lovelace: could you help them build a computer?&#8221;</h2><p><em>Barry O&#8217;Reilly asks. Evan Marshall answers.</em></p><p>Barry announced this one as &#8220;a really cruel one&#8221;, and it is. Evan&#8217;s honest answer was: not really. He could probably solve a few problems by pulling on his undergrad education. But he had a more urgent priority.</p><blockquote><p>My first goal would be to not be burned as a witch. Just blend in a little bit, survive.</p></blockquote><p>Then he made the point that stayed with me. Even if you remembered enough of the details to hand them the correct answer, coherently, you would still be stuck. Getting people to accept knowledge, and building consensus around that acceptance, is the tricky part. Knowing the answer was never the whole job. (Anyone who has tried to push a correct idea through an organisation in 2026 already knows this.)</p><p>Full conversation with Evan: <a href="https://youtu.be/7BiDPJN2nmQ">Root Cause of Where You Are on the AI Spectrum</a></p><h2>&#8220;When are we going to get a robot?&#8221;</h2><p><em>Evan Marshall asks. Fraser Merrifield answers.</em></p><p>Evan wanted to look forward instead of back. Everyone has a phone, everyone has a car, so if humanity keeps going, surely everyone gets a robot friend. When?</p><p>Fraser gave him a number, five years, and then spent the rest of his answer explaining why he doesn&#8217;t want one. He finds the idea of anyone living in his house weird enough, and he is selective about the people he spends time with. Then there is trust. People already assume their phones listen to every conversation and report back. Would they accept a robot walking around the house, with the kids, hearing everything?</p><blockquote><p>Just so they can do your laundry, probably quite badly.</p></blockquote><p>His prediction: in five years companies will be shipping commercial robots. His personal limit stays at the robot vacuum cleaner. As he put it, what if you didn&#8217;t get on?</p><p>Full conversation with Fraser: <a href="https://youtu.be/M0HAoWp5vDg">Root Cause of Not Getting Hired</a></p><h2>&#8220;Your top five movies of all time?&#8221;</h2><p><em>Fraser Merrifield asks. Tamanna Haque answers.</em></p><p>Fraser is a recruiter who talks about pop culture a lot, so of course this was his question. After fear, lost relationships and witch trials, the chain got a movie night.</p><p>Tamanna went straight to James Bond. Casino Royale, which she calls one of the last really good Bond films (I agree). Then the guilty pleasure: Tom Cruise, and the Mission Impossible films in particular. She doesn&#8217;t claim they are the best cinema from a critic&#8217;s point of view. She just really enjoys the action.</p><p>She never made it to five. Her own summary: no five films, but two really good sagas.</p><p>Full conversation with Tamanna: <a href="https://youtu.be/HaBYJbqune4">Root Cause of Visibility in the Age of AI</a></p><div><hr></div><h2>To be continued</h2><p>Tamanna left her own question for the next guest. That one is still open, and I&#8217;m keeping it for the next round. The chain continues.</p><p>I love how the questions find their way to the right person. You&#8217;ll appreciate it in the next chain, it&#8217;s starting hilariously. </p><p>Root Cause will continue with the episodes starting next week and I am continuously amazed how these people agreed to share their time and knowledge with us. </p><p>Thanks for reading, watching, sending me your feedback - I get wings when someone says &#8220;I watched your episode, &#8230;&#8221; no matter what comes next :D</p><p>Take care aaaand let&#8217;s keep root causing.</p><div><hr></div><p><strong>The full conversations, in chain order</strong></p><ol><li><p>Marc Babin: <a href="https://www.thoughtfultechnologist.com/p/the-root-cause-why-the-experts-stay">Who&#8217;s Speaking for the Experts?</a></p></li><li><p>Adrian Hornsby: <a href="https://www.thoughtfultechnologist.com/p/the-root-cause-of-never-learning">The Root Cause of Never Learning</a></p></li><li><p>Ia Mg: <a href="https://www.thoughtfultechnologist.com/p/the-root-cause-of-wanting-to-learn">The Root Cause of Wanting to Learn</a></p></li><li><p>Orel Zilberman: <a href="https://www.youtube.com/watch?v=xh4F80Fu458">Root Cause of Solopreneur Success: Before, During, and After AI</a></p></li><li><p>Eric Lubow: <a href="https://www.youtube.com/watch?v=Uv988vzRWOA">Root Cause of a Healthy Team</a></p></li><li><p>Barry O&#8217;Reilly: <a href="https://youtu.be/EGwcEQPX-lM">Root Cause of Architectural Thinking</a></p></li><li><p>Evan Marshall: <a href="https://youtu.be/7BiDPJN2nmQ">Root Cause of Where You Are on the AI Spectrum</a></p></li><li><p>Fraser Merrifield: <a href="https://youtu.be/M0HAoWp5vDg">Root Cause of Not Getting Hired</a></p></li><li><p>Tamanna Haque: <a href="https://youtu.be/HaBYJbqune4">Root Cause of Visibility in the Age of AI</a></p></li></ol>]]></content:encoded></item><item><title><![CDATA[Root Cause of Visibility in the Age of AI]]></title><description><![CDATA[Watch now (42 mins) | What is Generative Engine Optimization (GEO), and does it replace SEO?]]></description><link>https://www.thoughtfultechnologist.com/p/root-cause-of-visibility-in-the-age-436</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/root-cause-of-visibility-in-the-age-436</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Mon, 24 Aug 2026 14:38:42 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/212560740/8d7673c8afa869c6a8bccc7cde903834.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>What is Generative Engine Optimization (GEO), and does it replace SEO? In this episode of Root Cause we get to the root cause of what happens to being findable when people stop Googling and start asking ChatGPT, Gemini or Perplexity. With search engines, a human picks from a list of results. With AI search, the model gives one answer and one recommendation, and if you are not in it, you are not in the consideration set. That shift is what GEO (also called AI search optimization or AI visibility) is trying to address.</p><p>We cover GEO vs SEO and why good SEO is only a subset of AI visibility; the what, where and how of AI-readable content (which topics, which sites like Reddit, G2 and Capterra AI trusts, which formats); whether GEO feeds the AI slop machine (AI-generated content is no more readable to LLMs than human writing, and three purposeful articles beat ten); how fast-changing models affect what you optimize; why millennials using ChatGPT as a search engine and Gen Z using it as a companion are two different problems for a brand; B2B vs B2C vs creator use cases; and the fairness question of manufacturing a persona that ranks above the better product. Then the technical part: how you get a deterministic, credit-score-style AI visibility score out of non-deterministic LLMs, why the LLM should be a data extractor and never a grader, and practical GEO advice for content creators (know your proposition, get cited where AI trusts, transcribe your videos, and yes, bring back the blog).</p><p>My guest is Tamanna Haque, mathematician, lead data scientist with a decade of production AI on real customer data, and co-founder of <a href="http://GenSight.AI">GenSight.AI</a>, a GEO platform she built in her personal time with her husband Jonas. This is her first public conversation about it, and I came in openly skeptical.</p><h2>Chapters and Topics</h2><p>00:00 Introduction of the Episode and the Guest</p><p>02:56 Why Build a GEO Product in the Evenings: Eating Your Own Dog Food</p><p>06:08 What Is Generative Engine Optimization?</p><p>07:21 GEO vs SEO: Being an Option vs Being the Answer</p><p>10:48 The What, the Where and the How of Being Visible to AI</p><p>11:51 Does GEO Feed the AI Slop Machine?</p><p>15:05 Models Change Fast: Optimize Once or Forever?</p><p>17:02 Millennials Search, Gen Z Chats: Two Different Problems</p><p>20:46 B2B vs B2C vs Creators: Who Benefits Most?</p><p>22:35 Manufacturing a Persona: Who Deserves the Top Spot?</p><p>26:58 Deterministic Scores from Non-Deterministic Models</p><p>29:39 The LLM as Data Extractor, Never a Grader</p><p>31:44 Free Advice for Creators: Know Your Proposition, Bring Back the Blog</p><p>36:09 Book Recommendation: Harry Potter</p><p>38:05 Question from Fraser Merrifield: Top Movies</p><p>39:46 Question for the Next Guest: Which Pet Would You Have?</p><p>40:38 Closing</p><p>Find Tamanna at:</p><ul><li><p><a href="http://GenSight.AI">GenSight.AI</a> - <a href="https://gensight.ai">https://gensight.ai</a></p></li></ul><p>Find me (Nune) at:</p><ul><li><p>LinkedIn: <a href="https://www.linkedin.com/in/nisabek/">https://www.linkedin.com/in/nisabek/</a></p></li><li><p>Substack: <a href="https://www.thoughtfultechnologist.com/">https://www.thoughtfultechnologist.com/</a></p></li></ul><h2>References</h2><p>References mentioned during the talk (in order they appeared):</p><p>01:34 - GenSight.AI, the GEO platform Tamanna co-founded with her husband Jonas</p><p><a href="https://gensight.ai">https://gensight.ai</a></p><p>11:26 - Review sites Tamanna names as inherently trusted by AI: Reddit, Capterra, G2</p><p><a href="https://www.reddit.com">https://www.reddit.com</a></p><p><a href="https://www.capterra.com">https://www.capterra.com</a> </p><p><a href="https://www.g2.com">https://www.g2.com</a></p><p>26:58 - GenSight.AI methodology: deterministic scoring, the LLM as data extractor, never a grader</p><p><a href="https://gensight.ai/methodology">https://gensight.ai/methodology</a></p><p>36:38 - Harry Potter, Tamanna&#8217;s book recommendation</p><p><a href="https://en.wikipedia.org/wiki/Harry_Potter">https://en.wikipedia.org/wiki/Harry_Potter</a></p><p>37:23 - Harry Potter and the Methods of Rationality, the alternative universe I mentioned from my episode with Evan Marshall</p><p><a href="https://hpmor.com">https://hpmor.com</a></p><p>38:05 - Question from Fraser Merrifield (&#8221;top five movies&#8221;), his Root Cause episode</p><p>38:46 - Casino Royale (2006)</p><p><a href="https://en.wikipedia.org/wiki/Casino_Royale_(2006_film))">https://en.wikipedia.org/wiki/Casino_Royale_(2006_film))</a></p><p>39:08 - The Mission: Impossible films</p><p><a href="https://en.wikipedia.org/wiki/Mission:*Impossible*(film_series)">https://en.wikipedia.org/wiki/Mission:*Impossible*(film_series)</a></p>]]></content:encoded></item><item><title><![CDATA[The Root Cause of Not Getting Hired]]></title><description><![CDATA[Watch now (56 mins) | In this episode of Root Cause we sit down with Fraser Merrifield, founder of FORM Careers in Glasgow and the self-described craft brewer of digital recruitment, to get to the root cause of the gap between what the hiring market says it wants and what it actually rewards.]]></description><link>https://www.thoughtfultechnologist.com/p/the-root-cause-of-not-getting-hired-2c0</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/the-root-cause-of-not-getting-hired-2c0</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Mon, 10 Aug 2026 15:25:22 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/211561071/beff241d6f01ec9cbd84a51a08462b17.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In this episode of Root Cause we sit down with Fraser Merrifield, founder of FORM Careers in Glasgow and the self-described craft brewer of digital recruitment, to get to the root cause of the gap between what the hiring market says it wants and what it actually rewards. Fraser spent over a decade placing engineers in oil and gas, then bet on software in his late 30s, went fully solo, and now runs deliberately small on what he calls bullshit-free recruitment. He barely reads CVs anymore, and he'll tell you why a perfect one makes him suspicious.</p><p>We dig into why AI has made both hiring and getting hired harder while most of the horror stories stay myths: his clients average two interview stages, and the CV-rejecting AI mostly doesn't exist. Fraser explains the 12-month window on the "AI-native engineer" hype, what happens when an engineer burns through more in tokens than their salary, and why leaning on senior hires is the same mistake that left oil and gas with a talent shortage. And the story that sums up the whole market: 200 applications for one graduate role, one candidate picked up the phone, and he got the job, as the only person interviewed. Three years later he is still there.</p><h2>Chapters and Topics</h2><p>00:00 Cold Open: Six Yes/No Claims About the Job Market</p><p>00:41 Introduction of the Episode and the Guest</p><p>03:35 Writing Like a Human: Pop Culture and Starting in Lockdown</p><p>05:56 Five Views or Five Million: How to Read Your LinkedIn Visibility</p><p>07:45 Everyone's CV Is Perfect Now, So What Stands Out?</p><p>09:23 The Online Mood Hoover: Positivity vs Ranting</p><p>12:22 The Blitz Round: Yes or No</p><p>13:06 Why AI Made Both Hiring and Getting Hired Harder</p><p>14:48 Just Another Hype Cycle? The 12-Month Window</p><p>16:11 When Engineers Burn More in Tokens Than Their Salary</p><p>17:53 Eight-Stage Interviews: Would You Even Want That Job?</p><p>20:36 Can Bullshit-Free Recruitment Scale?</p><p>22:06 CVs After AI: Rejecting the Quick-Appliers, Rewarding the Extra Mile</p><p>25:25 One of 200 Applicants Picked Up the Phone. He Got the Job</p><p>27:06 Glasgow AI and the Return of Offline Networking</p><p>29:10 The Undercurrent of Real People on LinkedIn</p><p>31:18 How Fraser Actually Uses AI (and How It Argued Back)</p><p>37:38 Fraser Flips the Script: The Most In-Demand Skill in Five Years</p><p>43:21 Juniors vs Seniors: The Oil and Gas Warning</p><p>46:11 Asking About Training Without Entitlement</p><p>47:17 Question from Evan Marshall: When Are We Getting Robots?</p><p>52:14 Question for the Next Guest: Top Five Movies</p><p>52:45 Movie Recommendations: Her, Ex Machina, Transcendence</p><p>54:24 Closing</p><p>Find Fraser at:</p><p>&#8226; LinkedIn - <a href="https://www.linkedin.com/in/fraser-merrifield-7b54524/">https://www.linkedin.com/in/fraser-merrifield-7b54524/</a></p><p>&#8226; Form Careers - <a href="https://weformcareers.com/">https://weformcareers.com/</a></p><p>&#8226; Glasgow AI Meetup - <a href="https://www.meetup.com/meetup-group-xnqxwqzu/">https://www.meetup.com/meetup-group-xnqxwqzu/</a></p><p>Find me (Nune) at:</p><ul><li><p>LinkedIn: <a href="https://www.linkedin.com/in/nisabek/">https://www.linkedin.com/in/nisabek/</a></p></li><li><p>Substack: <a href="https://www.thoughtfultechnologist.com/">https://www.thoughtfultechnologist.com/</a></p></li><li><p>Envimate: <a href="https://envimate.com/">https://envimate.com/</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[Root Cause of Where You Are on the AI Spectrum]]></title><description><![CDATA[Watch now (56 mins) | In this episode of Root Cause we sit down with Evan Marshall, co-founder and CTO of Ito.ai, to get to the root cause of where the honest answer sits on the AI adoption spectrum, somewhere between the teams that won't let AI near their codebase and the ones that let it ship with barely a human in the loop.]]></description><link>https://www.thoughtfultechnologist.com/p/root-cause-of-where-you-are-on-the-5be</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/root-cause-of-where-you-are-on-the-5be</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Mon, 27 Jul 2026 11:22:35 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/211561072/15879e3bdc6b7fef44e43180a046d431.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In this episode of Root Cause we sit down with Evan Marshall, co-founder and CTO of Ito.ai, to get to the root cause of where the honest answer sits on the AI adoption spectrum, somewhere between the teams that won't let AI near their codebase and the ones that let it ship with barely a human in the loop. Most of us are somewhere in the middle, moving around and quietly wondering if we've got it right. This conversation is meant to help you gauge where you actually are, and where you want to be. Evan studied computer science at MIT and spent four years building privacy infrastructure for zero-knowledge blockchains, where a slipped bug is a disaster. That experience pushed him toward quality: he now builds a QA agent that actually runs your application and checks the code before it merges.</p><p>We dig into the pressure on Bay Area companies to claim a "software factory" while their engineers might still be shipping like everyone else, why free code generation can at most double you if coding was half your job (and it never was), and the plastic age of coding, where code is generated to be thrown away. Evan shares what a sane monthly AI spend actually looks like and his advice for integrating AI into your software development lifecycle: treat the SDLC as an optimization problem, because once generation is free, the bottleneck moves to verification and quality control. And when someone says "I can just do that with Claude Code", the work that follows is environments that have to heal themselves, caching that breaks on the next migration, and memory layers. As Evan puts it: we spent the tokens so you don't have to.</p><h2>Chapters and Topics</h2><p>00:00 Pre-show Banter and the Cats</p><p>00:59 Introduction of the Episode and the Guest</p><p>03:00 Is the Bay Area Really an AI Echo Chamber?</p><p>05:45 The Pressure to Claim a Software Factory</p><p>07:36 How Much Does AI Actually Speed You Up?</p><p>10:23 How Ito Uses AI in Its Own Engineering</p><p>14:13 The Plastic Age of Coding</p><p>15:53 Can the Software Factory Be Productized?</p><p>18:39 Subscriptions vs API: The Real Cost of Tokens</p><p>20:19 Open Models and Switching Between Them</p><p>21:25 Are the Models Plateauing?</p><p>22:59 "I Can Just Use Claude Code": Where the Hard Parts Hide</p><p>26:19 The Bottlenecks You Don't See: Environments, Caching, Memory</p><p>28:55 Will QA Engineers Be Replaced?</p><p>31:39 Replicators, Waymos, and 3D Printers: Why Change Takes Time</p><p>36:49 Why SaaS Isn't Dead and How Much You Should Spend</p><p>39:23 Advice for Integrating AI into Your SDLC</p><p>42:50 Question from Barry O'Reilly: Building a Computer in 1822</p><p>44:31 Shared Reality, Social Media, and Cooperation</p><p>50:25 Book Recommendations</p><p>53:54 Question for the Next Guest and Closing</p><p>Find Evan at:</p><p>&#8226; LinkedId: <a href="https://www.linkedin.com/in/evan--marshall/">https://www.linkedin.com/in/evan--marshall/</a></p><p>&#8226; his startup - <a href="https://www.ito.ai/">https://www.ito.ai/</a></p><p>Find me (Nune) at:</p><ul><li><p>LinkedIn: <a href="https://www.linkedin.com/in/nisabek/">https://www.linkedin.com/in/nisabek/</a></p></li><li><p>Substack: <a href="https://www.thoughtfultechnologist.com/">https://www.thoughtfultechnologist.com/</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[Root Cause of Architectural Thinking]]></title><description><![CDATA[Watch now (95 mins) | In this episode of Root Cause we sit down with Barry O'Reilly, 25 years in software architecture, former chief architect at Microsoft, startup CTO, and the creator of Residuality Theory, to get to the root cause of what senior architects actually do when they say they run on gut feeling.]]></description><link>https://www.thoughtfultechnologist.com/p/root-cause-of-architectural-thinking-38f</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/root-cause-of-architectural-thinking-38f</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Mon, 13 Jul 2026 15:08:22 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/211561073/49e35379f86d03dd37b479835bb770e9.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In this episode of Root Cause we sit down with Barry O'Reilly, 25 years in software architecture, former chief architect at Microsoft, startup CTO, and the creator of Residuality Theory, to get to the root cause of what senior architects actually do when they say they run on gut feeling. When Microsoft asked Barry to teach junior architects how he did his job, he discovered he couldn't describe his own methods, and neither could any of the senior architects he asked. That frustration turned into two books and a PhD in complexity science. We dig into why a random simulation of stress produces architectures that survive events nobody predicted, why equirements and risk management quietly limit the very thinking they were supposed to support, why our industry spreads ideas through charisma instead of scientific proof, and whether an LLM can ever produce an architecture. If you've ever been told "that's just experience," this episode puts words on it.</p><h2>Chapters and Topics</h2><p>00:00 Cold Open: The Architect vs the Implementer</p><p>02:06 Guest Introduction: Structuring the Magic</p><p>03:00 Pure Mathematics: Help or Trap?</p><p>06:20 Think Less, Do More? The Industry's Thinking Problem</p><p>09:09 Why Software Isn't Developing as a Science</p><p>12:26 Pop Culture, Gurus, and the Hype Machine</p><p>15:09 "My Industry Is Low Stakes": Why Quality Still Pays</p><p>17:54 Two Books That Decide If You're an Architect</p><p>22:09 Creativity vs Craft: Naming the Magic</p><p>25:39 Residuality Theory: The Marbles Analogy</p><p>31:59 How to Start: The Naive Architecture and Random Stress</p><p>36:35 Attractor States: Why Stressing Works</p><p>39:30 All Architecture Is Stress</p><p>44:14 The Trouble with Non-Functional Requirements</p><p>48:49 Should Architects Become Domain Experts?</p><p>52:02 Does This Apply to Small Systems and Startups?</p><p>57:36 Answering the Critics: "We've Always Done This"</p><p>01:01:28 Stressor Analysis: Architecture Never Stops</p><p>01:04:57 Shared Language and Reflective Practice</p><p>01:07:04 Has AI Made Code Cheaper?</p><p>01:12:54 Can LLM Agents Do Residuality?</p><p>01:18:43 The Walk Around the Problem Is the Point</p><p>01:20:40 First Steps into Residuality</p><p>01:25:18 Book Recommendations</p><p>01:29:39 A Benign Pride: Fly Fishing at 34 Meters</p><p>01:32:01 Question for the Next Guest and Closing</p><p>Find Barry at:</p><p>&#8226; LinkedIn: <a href="https://www.linkedin.com/in/barry-o-reilly-b924657/">https://www.linkedin.com/in/barry-o-reilly-b924657/</a></p><p>&#8226; Barry&#8217;s first book: <a href="https://leanpub.com/residuality">https://leanpub.com/residuality</a></p><p>&#8226; Barry&#8217;s second book: <a href="https://leanpub.com/architectsparadox">https://leanpub.com/architectsparadox</a></p><p>&#8226; The intro talk you should watch: <a href="https://www.youtube.com/watch?v=_MPUoiG6w_U">https://www.youtube.com/watch?v=_MPUoiG6w_U</a></p><p>Find me (Nune) at:</p><p>* LinkedIn: <a href="https://www.linkedin.com/in/nisabek/">https://www.linkedin.com/in/nisabek/</a></p><p>* Substack: <a href="https://www.thoughtfultechnologist.com/">https://www.thoughtfultechnologist.com/</a></p>]]></content:encoded></item><item><title><![CDATA[Root Cause of a Healthy Team]]></title><description><![CDATA[Watch now (79 mins) | In this episode of Root Cause we sit down with Eric Lubow, a CTO who treats organizations like distributed systems, which means the root cause of a broken team is usually a design problem, not a people problem.]]></description><link>https://www.thoughtfultechnologist.com/p/root-cause-of-a-healthy-team-b06</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/root-cause-of-a-healthy-team-b06</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Mon, 29 Jun 2026 15:29:20 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/211561074/c610ebf37a4805badc35968081351106.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In this episode of Root Cause we sit down with Eric Lubow, a CTO who treats organizations like distributed systems, which means the root cause of a broken team is usually a design problem, not a people problem. Eric has spent more than 20 years building and repairing teams and platforms, from co-founding SimpleReach to running engineering through dozens of acquisitions at Thrasio, and he is now Chief Product and Technology Officer at Mapp. He is also a jiu-jitsu coach, and that shapes how he leads. We get to the root cause of what actually makes a team healthy, why becoming a manager means changing your definition of done, and why ceding control is the part nobody warns you about. We talk about leading AI agents the way you would lead a person, why silent heroes quietly turn into silent burnouts, and how to hire into a team instead of into a vacuum. Honest and specific, with none of the leadership-content platitudes, including the lonely parts of the job most people at the top never say out loud.</p><p>00:00 Introduction: What Makes a Healthy Team</p><p>03:05 Jiu-Jitsu, Languages, and a Healthy Ego</p><p>08:23 Martial Arts, Balance, and "Everything Is Maintenance"</p><p>13:12 Teams as Distributed Systems and Conway's Law</p><p>16:38 The IC-to-Manager Transition: Ceding Control</p><p>19:10 Delegation and a New Definition of Done</p><p>22:24 Giving Away Your Legos</p><p>23:49 Can You Learn to Be a Manager?</p><p>25:21 Don't Just Become the Opposite of Your Bad Manager</p><p>27:54 Leading AI Agents Like You Lead People</p><p>31:55 Will AI Replace People? Force Multiplier, Not Replacement</p><p>36:45 What Actually Makes a Team Healthy</p><p>38:56 Adoption Curves and Why Teams Mimic Leaders</p><p>42:06 A Culture of Sharing vs Shadow IT and Shadow AI</p><p>47:41 The Hero Problem: Silent Heroes, Silent Burnout</p><p>53:20 Burnout, Boundaries, and Trusting the Team</p><p>55:33 Hiring Into a Team, Not a Vacuum</p><p>1:02:15 The Loneliness of Leadership</p><p>1:06:48 Why "I Don't Know" Is a Sign of Strength</p><p>1:09:13 Book Recommendations: Sci-Fi and Leadership</p><p>1:13:49 What Eric Would Tell His Younger Self</p><p>1:15:45 The Most Benign Thing You're Proud Of</p><p>Find Eric at:</p><p>&#8226; Linkedin: <a href="https://www.linkedin.com/in/eblubow/">https://www.linkedin.com/in/eblubow/</a></p><p>&#8226; His blog: <a href="https://eric.lubow.org">https://eric.lubow.org</a> (which heavily influenced this episode)</p><p>&#8226; Beyond the Belt podcast: <a href="https://www.youtube.com/@beyondthebeltpod">https://www.youtube.com/@beyondthebeltpod</a></p><p>Find me (Nune) at:</p><ul><li><p>LinkedIn<em>:</em> <a href="https://www.linkedin.com/in/nisabek/">https://www.linkedin.com/in/nisabek/</a></p></li><li><p>Substack<em>:</em> <a href="https://www.thoughtfultechnologist.com/">https://www.thoughtfultechnologist.com/</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[Root Cause of Solopreneur Success: Before, During, and After AI]]></title><description><![CDATA[Watch now (47 mins) | In this episode of Root Cause we sit down with Orel Zilberman, the solo builder behind WriteStack, the biggest tool out there for Substack creators.]]></description><link>https://www.thoughtfultechnologist.com/p/root-cause-of-solopreneur-success-458</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/root-cause-of-solopreneur-success-458</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Mon, 22 Jun 2026 13:26:20 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/211561075/768e72abfc206ed71d0d96127998579d.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In this episode of Root Cause we sit down with Orel Zilberman, the solo builder behind WriteStack, the biggest tool out there for Substack creators. Orel spent 599 days shipping around ten products that made zero dollars, then picked one thing, stuck with it for six months, and turned it into a six-figure business. He has lived three versions of solo building in three years: before the current AI tooling, as it arrived, and now. We get to the root cause of what AI actually changed for one-person companies and what it didn't. Building got faster, but knowing what to build, and sticking with it long enough to find out if it works, is exactly as hard as it always was. Honest and unfiltered, including the messy parts most "become an entrepreneur" content leaves out.</p><h2>Chapters and Topics</h2><p>00:00 Introduction to Root Cause and Solo Building</p><p>04:57 The Journey of Building WriteStack</p><p>06:42 What is SubStack and WriteStack?</p><p>09:28 "Why Bother" if the platform / big players will replace you</p><p>13:14 "Why bother" if AI will replace all SaaS</p><p>14:46 Knowing WHAT to Build and How to Distribute</p><p>18:30 Finding the Right Idea to Stick With</p><p>23:22 Learning from Opportunities and Failures</p><p>26:10 Navigating the Cold Start Problem</p><p>28:10 Leveraging AI Tools for Productivity</p><p>30:49 The Future of Software Engineering in the Age of AI</p><p>33:53 Advice for Aspiring Entrepreneurs</p><p>37:20 Being Better Than Most</p><p>38:49 Book Recommendations and Lifelong Learning</p><p>41:04 Reflections on Education and Career Choices</p><p>Find Orel at:</p><p>&#8226; His product - <a href="https://www.writestack.io/">https://www.writestack.io/</a>&nbsp;</p><p>&#8226; His journey - <a href="https://theindiepreneur.substack.com/">https://theindiepreneur.substack.com/</a>&nbsp;</p><p>&#8226; Substack notes analysis - <a href="https://thewritingedge.substack.com/">https://thewritingedge.substack.com/</a></p><p>&#8226; Substack profile - <a href="https://substack.com/@orelzilberman">https://substack.com/@orelzilberman</a></p><p>Find me (Nune) at:</p><ul><li><p>LinkedIn<em>:</em> <a href="https://www.linkedin.com/in/nisabek/">https://www.linkedin.com/in/nisabek/</a></p></li><li><p>Substack<em>:</em> <a href="https://www.thoughtfultechnologist.com/">https://www.thoughtfultechnologist.com/</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[The Root Cause of Wanting to Learn]]></title><description><![CDATA[Listen now (70 mins) | In this episode of Root Cause we sit down with Ia Mg - seasoned engineer, former CS and digital literacy teacher at the Free University of Tbilisi, and the author of the blog Bits Complicated - to get to the root cause of learning itself, and whether the machines we've built are about to make us better at it or worse.]]></description><link>https://www.thoughtfultechnologist.com/p/the-root-cause-of-wanting-to-learn-039</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/the-root-cause-of-wanting-to-learn-039</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Tue, 09 Jun 2026 07:15:42 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/211561076/38e6e8b11b552cd98ca479800435aa43.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In this episode of Root Cause we sit down with Ia Mg - seasoned engineer, former CS and digital literacy teacher at the Free University of Tbilisi, and the author of the blog Bits Complicated - to get to the root cause of learning itself, and whether the machines we've built are about to make us better at it or worse.</p><p>We dig into why everyone should understand technology even if they never write code, why domain knowledge has always mattered more than programmers wanted to admit, and what happens to learning when the answer is always one prompt away. Along the way: tech debt as a tax instead of a failure ("legacy as a service"), the "learning debt" that builds every time you accept a ready-made answer, why conversation-based coding is a process problem and not just an output problem, and why learning might be the most rebellious thing you can still do for yourself.</p><h2>Chapters and Topics</h2><p>00:00 Guest intro and episode goal</p><p>02:45 Teaching Programming to Non-Coders</p><p>04:13 The Importance of Technology Literacy</p><p>09:41 AI and the Future of Programming</p><p>16:10 AI as a Teacher of Programming</p><p>22:16 Evaluating AI Responses in Learning</p><p>26:49 Concerns About the Next Generation</p><p>30:08 AI as an Abstraction in Programming</p><p>33:40 Conversational Development vs. Traditional Coding</p><p>37:34 Understanding Tech Debt</p><p>42:09 Learning Debt in the Age of AI</p><p>45:06 AI is the next social network?</p><p>46:47 Embracing the Chaos of Innovation</p><p>47:59 The Joy of Coding vs. AI</p><p>53:22 Navigating the Job Market in Tech</p><p>57:30 Book Recommendations</p><p>01:02:08 Summary of the Discussion</p><p>01:02:41 Learning as a Rebellious Act</p><p>01:04:09 Practical Recommendation on using AI consciously</p><p>01:06:21 Engineering is more than coding</p><p>Find Ia at:&nbsp;</p><ul><li><p>Blog: <a href="https://iyamg.com/bitscomplicated/">https://iyamg.com/bitscomplicated/</a></p></li><li><p>LinkedIn: <a href="https://www.linkedin.com/in/ia-mgvdliashvili-0b459768/">https://www.linkedin.com/in/ia-mgvdliashvili-0b459768/</a>&nbsp;</p></li></ul><p><br>Find me (Nune) at:</p><ul><li><p>Blog: <a href="https://www.thoughtfultechnologist.com/">https://www.thoughtfultechnologist.com/</a>&nbsp;</p></li><li><p>LinkedIn: <a href="https://www.linkedin.com/in/nisabek/">https://www.linkedin.com/in/nisabek/</a>&nbsp;</p></li></ul>]]></content:encoded></item><item><title><![CDATA[The Root Cause of Never Learning]]></title><description><![CDATA[Watch now (78 mins) | In this episode of Root Cause we sit down with Adrian Hornsby &#8212; former AWS Principal Engineer, founder of Resilium Labs, and author of Why We Still Suck at Resilience &#8212; to get to the root cause of what's quietly breaking inside engineering organizations as AI absorbs more of the thinking.]]></description><link>https://www.thoughtfultechnologist.com/p/the-root-cause-of-never-learning-ad6</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/the-root-cause-of-never-learning-ad6</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Tue, 26 May 2026 07:08:32 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/211561077/b50a95ab20e74aa3e45fa52db4aa4903.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In this episode of Root Cause we sit down with Adrian Hornsby &#8212; former AWS Principal Engineer, founder of Resilium Labs, and author of <em>Why We Still Suck at Resilience</em> &#8212; to get to the root cause of what's quietly breaking inside engineering organizations as AI absorbs more of the thinking. We dig into the gap between how we imagine our systems work and how they actually work, why that gap is where all the real learning lives, and what happens to a team when the thinking itself gets delegated to something that sounds confident but doesn't know which walls are load-bearing.&nbsp;</p><h2>Chapters and topics</h2><p>00:00 Pre-show Banter and the Dog</p><p>01:08 Introduction of the Episode and the Guest</p><p>05:00 What's Wrong with the Name of the Show</p><p>07:35 The Importance of Learning from Successes</p><p>09:53 Defining Work as Imagined and Work as Done</p><p>13:43 Leading vs Being Hands-On</p><p>28:49 Learning From the Gap</p><p>30:39 Chaos Engineering</p><p>31:31 Load Testing</p><p>32:50 Game Days</p><p>34:00 ORRs - Operational Readiness reviews</p><p>34:41 Learning From the Incident</p><p>36:25 How AI has Affected the Gap</p><p>41:57 Navigating the Complexity of AI Delegation</p><p>43:45 Skill Atrophy and the New Generation of Engineers</p><p>47:12 Building Tools That Keep You Smart</p><p>52:18 We Need a Crisis to Slow Down</p><p>58:30 Building Intuition in AI-Driven Systems</p><p>01:03:17 The Human Touch in Technology</p><p>01:07:32 Facing Fears and Embracing Change</p><p>01:16:28 Question for the Next Guest and Closing</p><p>Adrian has generously decided to run a discount with the promocode &#8220;rootcausebynune&#8221; - for the first 30 copies you can buy his book for as low as 14.99 - that&#8217;s over 70% discount over the suggested price!</p><p><a href="https://leanpub.com/whywestillsuckatresilience/c/rootcausebynune">https://leanpub.com/whywestillsuckatresilience/c/rootcausebynune</a>&nbsp;</p><p>Find Adrian at:</p><ul><li><p><strong>Resilium Labs:</strong> <a href="http://resiliumlabs.com">resiliumlabs.com</a></p></li><li><p><strong>LinkedIn:</strong> <a href="https://www.linkedin.com/in/adhorn/">https://www.linkedin.com/in/adhorn/</a>&nbsp;</p></li><li><p><strong>Substack:</strong> <a href="https://newsletter.resiliumlabs.com/">https://newsletter.resiliumlabs.com/</a></p></li></ul><p>Find me (Nune) at:</p><ul><li><p><strong>LinkedIn:</strong> <a href="https://www.linkedin.com/in/nisabek/">https://www.linkedin.com/in/nisabek/</a>&nbsp;</p></li><li><p><strong>Substack:</strong> <a href="https://www.thoughtfultechnologist.com/">https://www.thoughtfultechnologist.com/</a>&nbsp;</p></li></ul>]]></content:encoded></item><item><title><![CDATA[Who's Speaking for the Experts?]]></title><description><![CDATA[Watch now (63 mins) | In this very first episode of Root Cause we sit down with Marc Babin - an award-winning digital marketing professional and creator of over a dozen of podcasts - to get to the root cause of personal branding - why it matters more than ever and how a busy professional who doesn't like the empty talks can survive the content noise and still make themselves visible.]]></description><link>https://www.thoughtfultechnologist.com/p/whos-speaking-for-the-experts-e6a</link><guid isPermaLink="false">https://www.thoughtfultechnologist.com/p/whos-speaking-for-the-experts-e6a</guid><dc:creator><![CDATA[Nune Isabekyan]]></dc:creator><pubDate>Mon, 11 May 2026 13:37:45 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/211561078/0548bf274cce5cff1a15399bcea5574a.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In this very first episode of Root Cause we sit down with Marc Babin - an award-winning digital marketing professional and creator of over a dozen of podcasts - to get to the root cause of personal branding - why it matters more than ever and how a busy professional who doesn't like the empty talks can survive the content noise and still make themselves visible.</p><h2>Chapters and topics</h2><p>00:00 Show and Guest Introduction<br>02:54 The Value of Authentic Content in a Noisy World<br>06:18 AI and Content: Good Authentic Content is King<br>09:47 Reel-Thinking vs Podcast Creation<br>13:57 Creating Engaging Content in Niche Markets<br>18:14 Sales vs. Marketing: Building Trust Through Content<br>22:02 The Long Game in Content Creation<br>25:48 Personal Branding in the Digital Age<br>28:28 Setting Up for Success in Content Creation<br>33:05 Overcoming Perfectionism in Content Creation<br>38:27 Embracing the Silence of Early Content<br>43:29 Navigating Privacy and Online Presence<br>48:36 The Discomfort of Starting<br>53:14 The Root Causes of Expert Silence<br>57:53 How to Start Creating Content<br>01:00:30 Question for the Next Guest and Closing<br><br><strong>Follow Marc Babin:</strong><br>LinkedIn - <a href="https://www.linkedin.com/in/babinmarc/">https://www.linkedin.com/in/babinmarc/</a><br>The Podcast Blueprint Website - <a href="https://www.yourpodcastblueprint.com/">https://www.yourpodcastblueprint.com/</a><br>The Podcast Blueprint LinkedIn Page - <a href="https://www.linkedin.com/company/podcast-blueprint/">https://www.linkedin.com/company/podcast-blueprint/</a><br><br><strong>Additional Material mentioned in the episode:</strong><br>The Podcast Consumer 2025 report from Edison Research - <a href="https://www.edisonresearch.com/wp-content/uploads/2025/07/The-Podcast-Consumer-2025-revised-FINAL.pdf">https://www.edisonresearch.com/wp-content/uploads/2025/07/The-Podcast-Consumer-2025-revised-FINAL.pdf</a><br>Read People Like a Book: How to Analyze, Understand, and Predict People&#8217;s Emotions, Thoughts, Intentions, and Behaviors By Patrick King - <a href="https://www.goodreads.com/en/book/show/56199402-read-people-like-a-book">https://www.goodreads.com/en/book/show/56199402-read-people-like-a-book</a></p>]]></content:encoded></item></channel></rss>