<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on Murat Eksi</title><link>https://murateksi.com/posts/</link><description>Recent content in Writing on Murat Eksi</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 08 Apr 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://murateksi.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>The Technical Seller Advantage: Why Engineers Who Can Sell Win</title><link>https://murateksi.com/posts/technical-seller-advantage/</link><pubDate>Wed, 08 Apr 2026 09:00:00 +0200</pubDate><guid>https://murateksi.com/posts/technical-seller-advantage/</guid><description>There&amp;rsquo;s a persistent divide in enterprise technology between &amp;ldquo;the people who build&amp;rdquo; and &amp;ldquo;the people who sell.&amp;rdquo; Engineers look at salespeople with suspicion. Salespeople look at engineers as resources to be deployed on calls. Both sides lose.
The professionals who create the most value, and build the most durable careers, are the ones who bridge this gap.
Why technical depth changes the sales conversation A traditional salesperson can present capabilities. A technical seller can diagnose problems.</description></item><item><title>Your Architecture Isn't AI-Ready. Here's What to Fix First.</title><link>https://murateksi.com/posts/building-ai-ready-architecture/</link><pubDate>Thu, 05 Mar 2026 09:00:00 +0100</pubDate><guid>https://murateksi.com/posts/building-ai-ready-architecture/</guid><description>Every week I talk to engineering leaders who want to &amp;ldquo;add AI&amp;rdquo; to their platform. They&amp;rsquo;re thinking about models, frameworks, and which LLM provider to use. Those are all valid questions. But they&amp;rsquo;re the wrong first questions.
The first question is: can your current architecture support AI workloads at all?
The data layer problem AI models need data. Not just any data. They need consistent, well-structured, accessible data with clear lineage and governance.</description></item><item><title>How to Sell Cloud Transformation to Executives Who Have Been Burned Before</title><link>https://murateksi.com/posts/selling-cloud-transformation-to-executives/</link><pubDate>Thu, 22 Jan 2026 09:00:00 +0100</pubDate><guid>https://murateksi.com/posts/selling-cloud-transformation-to-executives/</guid><description>Every enterprise executive has a cloud horror story. The migration that went 3x over budget. The lift-and-shift that lifted costs without shifting outcomes. The &amp;ldquo;cloud-native rewrite&amp;rdquo; that took two years and still isn&amp;rsquo;t done.
When you walk into a room to propose a cloud transformation, you&amp;rsquo;re not starting from zero. You&amp;rsquo;re starting from negative trust. Here&amp;rsquo;s how to navigate that.
Stop leading with technology Nobody in the C-suite cares about Kubernetes.</description></item><item><title>Enterprise AI Adoption: The Gap Between Demo and Production</title><link>https://murateksi.com/posts/enterprise-ai-adoption-reality/</link><pubDate>Thu, 18 Dec 2025 09:00:00 +0100</pubDate><guid>https://murateksi.com/posts/enterprise-ai-adoption-reality/</guid><description>I&amp;rsquo;ve watched dozens of enterprise AI initiatives launch with excitement and stall within six months. The pattern is remarkably consistent. A compelling demo gets executive buy-in. A team gets funded. Then reality sets in.
The model works on clean data. Production data isn&amp;rsquo;t clean.
The data problem nobody wants to talk about Every AI conversation starts with &amp;ldquo;what model should we use?&amp;rdquo; The right first question is &amp;ldquo;what does our data actually look like?</description></item><item><title>What Running Serverless at Scale Actually Teaches You</title><link>https://murateksi.com/posts/serverless-at-scale-lessons/</link><pubDate>Wed, 12 Nov 2025 09:00:00 +0100</pubDate><guid>https://murateksi.com/posts/serverless-at-scale-lessons/</guid><description>Most serverless content focuses on the first deployment. The &amp;ldquo;Hello World&amp;rdquo; moment. But the interesting part starts when your platform handles 200K messages per second and your on-call engineer gets paged at 3 AM because a downstream service changed its payload format.
Here&amp;rsquo;s what I&amp;rsquo;ve learned building serverless systems at enterprise scale.
Cold starts are not your biggest problem Everyone asks about cold starts. Almost nobody asks about observability. In a distributed serverless architecture, your biggest operational challenge is understanding what happened when something goes wrong.</description></item><item><title>Why Cloud Architecture Decisions Are Business Decisions</title><link>https://murateksi.com/posts/cloud-architecture-business-decisions/</link><pubDate>Wed, 10 Jul 2024 10:00:00 +0200</pubDate><guid>https://murateksi.com/posts/cloud-architecture-business-decisions/</guid><description>There&amp;rsquo;s a persistent myth in technology organizations that architecture is a purely technical discipline, that decisions about service boundaries, data stores, and deployment strategies belong exclusively to engineers. In reality, every architectural choice is a business decision in disguise.
The Cost of Abstraction When a team chooses between a managed service and a self-hosted alternative, they&amp;rsquo;re not just evaluating technical trade-offs. They&amp;rsquo;re making a statement about where the organization wants to invest its engineering hours.</description></item></channel></rss>