<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>letscode.hu Blog</title>
    <link>https://letscode.hu/en/blog</link>
    <description>Software architecture, AI engineering, and delivery — from letscode.hu.</description>
    <language>en</language>
    <atom:link xmlns:atom="http://www.w3.org/2005/Atom" href="https://letscode.hu/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>You Don&apos;t Need an Agent for That</title>
      <link>https://letscode.hu/en/blog/p/you-dont-need-an-agent-for-that</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/you-dont-need-an-agent-for-that</guid>
      <pubDate>Tue, 11 Aug 2026 00:00:00 GMT</pubDate>
      <description>A team spent three weeks building an agent to triage support tickets, then replaced it with a text classifier - faster, cheaper, more predictable. Most agent-shaped ideas are tasks with a mapping already sitting in the data, waiting to be learned instead of reasoned about turn by turn.</description>
    </item>
    <item>
      <title>AI Didn&apos;t Make You 5x Faster. It Moved the Bottleneck.</title>
      <link>https://letscode.hu/en/blog/p/ai-didnt-make-you-5x-faster</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/ai-didnt-make-you-5x-faster</guid>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <description>An agent generated a feature in minutes, then sat idle waiting for CI runners. AI made writing code cheap, but that was never the same as making software cheap - and the gap is where the promised 5x disappears.</description>
    </item>
    <item>
      <title>The Architect Won&apos;t Be Here When the Bill Comes Due</title>
      <link>https://letscode.hu/en/blog/p/architect-wont-be-here-when-bill-comes-due</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/architect-wont-be-here-when-bill-comes-due</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <description>The person who mandates &quot;everything serverless&quot; is systematically the one least exposed to the consequences. The decision outlives the decider, and the misalignment between who decides and who pays is the real defect - not the tech.</description>
    </item>
    <item>
      <title>Your Best Engineer Barely Writes Code Anymore</title>
      <link>https://letscode.hu/en/blog/p/best-engineer-barely-writes-code</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/best-engineer-barely-writes-code</guid>
      <pubDate>Sat, 20 Jun 2026 00:00:00 GMT</pubDate>
      <description>A team lead almost put his best engineer on a performance plan for low output - until his manager asked one question. When generating code is nearly free, output stops measuring value, and judgment becomes the work no dashboard can see.</description>
    </item>
    <item>
      <title>Your Model Can Disappear Overnight</title>
      <link>https://letscode.hu/en/blog/p/ai-model-independence</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/ai-model-independence</guid>
      <pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate>
      <description>An export-control order disabled a frontier model for everyone - even the US customers it never targeted. The fix is not a model from the right country, but an architecture that can swap models without a rewrite.</description>
    </item>
    <item>
      <title>Spec-Driven Development and the Waterfall Trap</title>
      <link>https://letscode.hu/en/blog/p/spec-driven-development-waterfall-trap</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/spec-driven-development-waterfall-trap</guid>
      <pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate>
      <description>Spec-driven development solves real problems with vibe coding, but writing a long, confident spec up front quietly brings back the waterfall assumption. The fix is to iterate the spec, not just the code.</description>
    </item>
    <item>
      <title>Do Not Let AI Write Your ADRs</title>
      <link>https://letscode.hu/en/blog/p/ai-generated-adrs</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/ai-generated-adrs</guid>
      <pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate>
      <description>AI can produce polished ADR-shaped text, but it cannot weigh your real decision drivers. Use it to expose assumptions and blind spots before the team owns the choice.</description>
    </item>
    <item>
      <title>Tests Have Always Been Neglected. AI Made It Worse.</title>
      <link>https://letscode.hu/en/blog/p/testing-in-ai-age</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/testing-in-ai-age</guid>
      <pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate>
      <description>AI can generate tests fast, but speed often amplifies brittle, implementation-focused test suites. The real gain comes from behavior-focused tests that survive refactors.</description>
    </item>
    <item>
      <title>You Are Not Building Airplanes</title>
      <link>https://letscode.hu/en/blog/p/you-are-not-building-airplanes</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/you-are-not-building-airplanes</guid>
      <pubDate>Tue, 05 May 2026 00:00:00 GMT</pubDate>
      <description>Reliability does not improve by writing fallbacks for every uncertain state. Critical points need redundancy; everywhere else needs simplicity.</description>
    </item>
    <item>
      <title>Overengineering vs. underengineering: a compliance near-miss</title>
      <link>https://letscode.hu/en/blog/p/overengineering-vs-underengineering-compliance-nightmare</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/overengineering-vs-underengineering-compliance-nightmare</guid>
      <pubDate>Sun, 26 Apr 2026 00:00:00 GMT</pubDate>
      <description>A tenant deletion endpoint looked like five lines, but multi-region data, retention rules, and auditability turned it into a business-critical workflow design problem.</description>
    </item>
    <item>
      <title>Before You Choose Architecture, Answer This One Question</title>
      <link>https://letscode.hu/en/blog/p/worth-solving-before-architecture</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/worth-solving-before-architecture</guid>
      <pubDate>Mon, 20 Apr 2026 00:00:00 GMT</pubDate>
      <description>Teams often start with stack and architecture decisions too early. First validate whether the problem is worth solving now, then design the smallest system that proves value.</description>
    </item>
    <item>
      <title>Not All Tech Debt Is Equal</title>
      <link>https://letscode.hu/en/blog/p/not-all-tech-debt-is-equal</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/not-all-tech-debt-is-equal</guid>
      <pubDate>Tue, 31 Mar 2026 00:00:00 GMT</pubDate>
      <description>Treating all tech debt the same creates false progress. Strategic, accidental, and architectural debt need different decisions and different responses.</description>
    </item>
    <item>
      <title>Your CI/CD Pipeline Is Slower Than Your Developers</title>
      <link>https://letscode.hu/en/blog/p/ci-cd-pipeline-slower-than-your-developers</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/ci-cd-pipeline-slower-than-your-developers</guid>
      <pubDate>Fri, 20 Mar 2026 00:00:00 GMT</pubDate>
      <description>Developers ship fast; production does not. The bottleneck is not people—it is your pipeline, process, and architecture of delivery.</description>
    </item>
    <item>
      <title>ADRs Are Useful Only If They Shape the Decision</title>
      <link>https://letscode.hu/en/blog/p/adrs-are-useful-only-if-they-shape-the-decision</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/adrs-are-useful-only-if-they-shape-the-decision</guid>
      <pubDate>Sun, 08 Mar 2026 00:00:00 GMT</pubDate>
      <description>ADRs fail when they become passive documentation. Their real value is the thinking and discussion before the decision is finalized.</description>
    </item>
    <item>
      <title>Your Scaling Problem Might Be Architecture, Not Kubernetes</title>
      <link>https://letscode.hu/en/blog/p/your-scaling-problem-might-be-architecture-not-kubernetes</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/your-scaling-problem-might-be-architecture-not-kubernetes</guid>
      <pubDate>Wed, 04 Mar 2026 00:00:00 GMT</pubDate>
      <description>Before moving to Kubernetes, verify what actually breaks first. Many scaling problems come from architecture and unclear boundaries, not missing clusters.</description>
    </item>
    <item>
      <title>Context Engineering in Practice: Building Agents That Remember Just Enough</title>
      <link>https://letscode.hu/en/blog/p/context-engineering-in-practice</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/context-engineering-in-practice</guid>
      <pubDate>Wed, 03 Dec 2025 00:00:00 GMT</pubDate>
      <description>Most failing agents aren&apos;t held back by a weak model - they&apos;re drowning in tool results that quietly re-inject the same 2,500-word document into every turn. The fix isn&apos;t a bigger context window; it&apos;s giving the model exactly what it needs for the current step, and nothing else.</description>
    </item>
    <item>
      <title>Structured Output Without Asking Nicely</title>
      <link>https://letscode.hu/en/blog/p/structured-output-without-asking-nicely</link>
      <guid isPermaLink="true">https://letscode.hu/en/blog/p/structured-output-without-asking-nicely</guid>
      <pubDate>Tue, 21 Oct 2025 00:00:00 GMT</pubDate>
      <description>Asking an LLM nicely for a specific output shape works until it doesn&apos;t - a few calls out of a hundred drift out of format and break a parser. Constraining the token generation itself, through tool calling or schema enforcement, is what actually makes the shape non-negotiable.</description>
    </item>
  </channel>
</rss>
