<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Georgi Kalchev</title>
    <description>The latest articles on DEV Community by Georgi Kalchev (@georgi_kalchev_85d01f7368).</description>
    <link>https://dev.to/georgi_kalchev_85d01f7368</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4161990%2Fb9b4d48e-f16e-4c72-ab10-9fd628a87528.jpg</url>
      <title>DEV Community: Georgi Kalchev</title>
      <link>https://dev.to/georgi_kalchev_85d01f7368</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/georgi_kalchev_85d01f7368"/>
    <language>en</language>
    <item>
      <title>A test that can never fail measures nothing</title>
      <dc:creator>Georgi Kalchev</dc:creator>
      <pubDate>Mon, 16 Nov 2026 15:00:52 +0000</pubDate>
      <link>https://dev.to/georgi_kalchev_85d01f7368/a-test-that-can-never-fail-measures-nothing-1f9h</link>
      <guid>https://dev.to/georgi_kalchev_85d01f7368/a-test-that-can-never-fail-measures-nothing-1f9h</guid>
      <description>&lt;p&gt;A green check only counts if it would turn red when the thing it guards breaks. Here are common ways a test cannot fail, and how to prove yours can.&lt;/p&gt;

&lt;p&gt;A test is a question you put to your code, and the only useful question is one whose answer could be no. If a check stays green whether the code works or not, it tells you nothing, and it does something worse than nothing: it ends the search. When something is wrong in production and the tests are green, people stop looking at the code that the tests claim to cover. Checks like that are easy to write by accident, so below are the usual ways a check ends up in that state, followed by a plain method for proving that yours is not.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the full report on AISkills402:&lt;/strong&gt; &lt;a href="https://aiskills402.com/blog/test-that-never-fails?utm_source=devto&amp;amp;utm_medium=social" rel="noopener noreferrer"&gt;https://aiskills402.com/blog/test-that-never-fails?utm_source=devto&amp;amp;utm_medium=social&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>debugging</category>
    </item>
    <item>
      <title>Terraform plan: what to read before you press apply</title>
      <dc:creator>Georgi Kalchev</dc:creator>
      <pubDate>Mon, 16 Nov 2026 07:00:52 +0000</pubDate>
      <link>https://dev.to/georgi_kalchev_85d01f7368/terraform-plan-what-to-read-before-you-press-apply-2iba</link>
      <guid>https://dev.to/georgi_kalchev_85d01f7368/terraform-plan-what-to-read-before-you-press-apply-2iba</guid>
      <description>&lt;p&gt;A plan is a preview of what will be destroyed, replaced or opened. Read the action symbols, the replacement reasons and the firewall lines before you approve.&lt;/p&gt;

&lt;p&gt;Most of a terraform plan is routine: tags change, a size is raised, a new rule appears. A few lines are different, because applying them removes data that cannot be rebuilt or opens a service to the whole internet. This guide shows where those lines hide in the output, what each marker means, and a fixed order of reading that takes a couple of minutes. The short answer to the question in the title: read the action on every resource that holds data, read the reason behind every replacement, and read the source address of every firewall rule that was added or changed. The summary count at the bottom tells you how much to read, not whether it is safe.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the full report on AISkills402:&lt;/strong&gt; &lt;a href="https://aiskills402.com/blog/terraform-plan-read-before-apply?utm_source=devto&amp;amp;utm_medium=social" rel="noopener noreferrer"&gt;https://aiskills402.com/blog/terraform-plan-read-before-apply?utm_source=devto&amp;amp;utm_medium=social&lt;/a&gt;&lt;/p&gt;

</description>
      <category>debugging</category>
      <category>testing</category>
    </item>
    <item>
      <title>Survey questions that push people toward an answer</title>
      <dc:creator>Georgi Kalchev</dc:creator>
      <pubDate>Sun, 15 Nov 2026 15:00:51 +0000</pubDate>
      <link>https://dev.to/georgi_kalchev_85d01f7368/survey-questions-that-push-people-toward-an-answer-13ag</link>
      <guid>https://dev.to/georgi_kalchev_85d01f7368/survey-questions-that-push-people-toward-an-answer-13ag</guid>
      <description>&lt;p&gt;Leading stems, fused questions, charged words, absolute wording and lopsided scales change what respondents say. Here is how to spot each one and reword it.&lt;/p&gt;

&lt;p&gt;A survey question is a measuring instrument, and wording can bend it. The same issue, asked two slightly different ways, can produce quite different answers, so a questionnaire with careless wording reports the writer's opinion back to the writer. Five habits do most of the damage: a stem that hints at the right answer, two questions glued into one, a word that already passes judgement, an absolute word that nobody can honestly agree with, and a rating scale tilted to one side. This guide describes each, shows a neutral rewrite, and ends with a routine for proofing a draft, by hand or with a model, before it goes out.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the full report on AISkills402:&lt;/strong&gt; &lt;a href="https://aiskills402.com/blog/survey-question-bias-wording?utm_source=devto&amp;amp;utm_medium=social" rel="noopener noreferrer"&gt;https://aiskills402.com/blog/survey-question-bias-wording?utm_source=devto&amp;amp;utm_medium=social&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>debugging</category>
    </item>
    <item>
      <title>Stripe webhook mistakes that lose or repeat payments</title>
      <dc:creator>Georgi Kalchev</dc:creator>
      <pubDate>Sun, 15 Nov 2026 07:00:51 +0000</pubDate>
      <link>https://dev.to/georgi_kalchev_85d01f7368/stripe-webhook-mistakes-that-lose-or-repeat-payments-3167</link>
      <guid>https://dev.to/georgi_kalchev_85d01f7368/stripe-webhook-mistakes-that-lose-or-repeat-payments-3167</guid>
      <description>&lt;p&gt;A Stripe webhook endpoint is a public URL that moves money and access. Five coding mistakes let a forged request or a plain retry do the wrong thing.&lt;/p&gt;

&lt;p&gt;A Stripe webhook endpoint is an ordinary web address that Stripe calls when something happens in your account: a payment succeeds, a subscription renews, a dispute opens. Whatever your handler does next, such as shipping a product, switching on a plan or crediting a balance, is real. That makes the endpoint a target for two kinds of trouble. Someone outside Stripe can post a made-up event to it, and Stripe itself can legitimately deliver the same event more than once. Many webhook bugs that cost money come from five habits in the handler code: parsing the body too early, skipping the signature check, turning off the age check, ignoring event ids, and doing slow work before answering. This…&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the full report on AISkills402:&lt;/strong&gt; &lt;a href="https://aiskills402.com/blog/stripe-webhook-mistakes?utm_source=devto&amp;amp;utm_medium=social" rel="noopener noreferrer"&gt;https://aiskills402.com/blog/stripe-webhook-mistakes?utm_source=devto&amp;amp;utm_medium=social&lt;/a&gt;&lt;/p&gt;

</description>
      <category>debugging</category>
      <category>testing</category>
    </item>
    <item>
      <title>Spending ceilings that really stop the spending</title>
      <dc:creator>Georgi Kalchev</dc:creator>
      <pubDate>Sat, 14 Nov 2026 15:00:58 +0000</pubDate>
      <link>https://dev.to/georgi_kalchev_85d01f7368/spending-ceilings-that-really-stop-the-spending-5hni</link>
      <guid>https://dev.to/georgi_kalchev_85d01f7368/spending-ceilings-that-really-stop-the-spending-5hni</guid>
      <description>&lt;p&gt;A budget alert tells you about spend after it happens. A ceiling only counts if the paid call has to pass it. Here is how to test which one you have.&lt;/p&gt;

&lt;p&gt;Most teams that pay per call to a model, a data provider or a cloud service have a limit somewhere. The useful question is not whether a limit exists but whether the money has to get past it. A spending ceiling that sits beside the road, rather than on it, looks identical in a dashboard and does nothing on the day a loop goes wrong. This guide gives you three kinds of protection, a short list of ways a ceiling quietly fails to bind, and a test you can run before a paid job goes live. What you are after is not a bill of nothing; it is a bill with no surprises in it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the full report on AISkills402:&lt;/strong&gt; &lt;a href="https://aiskills402.com/blog/spend-ceilings-that-actually-stop?utm_source=devto&amp;amp;utm_medium=social" rel="noopener noreferrer"&gt;https://aiskills402.com/blog/spend-ceilings-that-actually-stop?utm_source=devto&amp;amp;utm_medium=social&lt;/a&gt;&lt;/p&gt;

</description>
      <category>debugging</category>
      <category>testing</category>
    </item>
    <item>
      <title>A handoff note between agent sessions: what must survive</title>
      <dc:creator>Georgi Kalchev</dc:creator>
      <pubDate>Sat, 14 Nov 2026 07:00:58 +0000</pubDate>
      <link>https://dev.to/georgi_kalchev_85d01f7368/a-handoff-note-between-agent-sessions-what-must-survive-34f9</link>
      <guid>https://dev.to/georgi_kalchev_85d01f7368/a-handoff-note-between-agent-sessions-what-must-survive-34f9</guid>
      <description>&lt;p&gt;A new agent session starts blind. What a handoff note has to carry, what to leave out, and a test that shows whether yours lets the next session trust it.&lt;/p&gt;

&lt;p&gt;A handoff note is the only thing that crosses the gap between two agent sessions, so it has to answer one question for the next session: what is actually finished, what is not, and where do I start? Everything else is detail. The failure to avoid is a note that sounds confident and is wrong, because the next session will believe it and build on it. This guide lists what a note must carry, what it should refuse to carry, and a simple way to test a note before you rely on it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the full report on AISkills402:&lt;/strong&gt; &lt;a href="https://aiskills402.com/blog/session-handoff-note-for-agents?utm_source=devto&amp;amp;utm_medium=social" rel="noopener noreferrer"&gt;https://aiskills402.com/blog/session-handoff-note-for-agents?utm_source=devto&amp;amp;utm_medium=social&lt;/a&gt;&lt;/p&gt;

</description>
      <category>claudecode</category>
      <category>testing</category>
    </item>
    <item>
      <title>ReDoS: the regex that locks your server</title>
      <dc:creator>Georgi Kalchev</dc:creator>
      <pubDate>Fri, 13 Nov 2026 15:00:51 +0000</pubDate>
      <link>https://dev.to/georgi_kalchev_85d01f7368/redos-the-regex-that-locks-your-server-92h</link>
      <guid>https://dev.to/georgi_kalchev_85d01f7368/redos-the-regex-that-locks-your-server-92h</guid>
      <description>&lt;p&gt;A single pattern in a validator can pin a Node process when the input is crafted to fail. Here is why it happens, how to spot it, and how to fix it.&lt;/p&gt;

&lt;p&gt;A regular expression that works on every normal input can still take a server down, because the damage depends on the shape of the pattern and on one kind of hostile input, not on traffic. The engine in Node and in browsers tries alternatives one after another, and for some patterns the number of alternatives doubles with every extra character. A text that fails to match is the worst case, since the engine will not give up until it has explored every way of splitting the text. A visitor who sends one long, almost-valid string can keep a process busy for minutes. Below you will find the mechanism, the pattern shapes that cause trouble, rewrites that leave the accepted set untouched, and a…&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the full report on AISkills402:&lt;/strong&gt; &lt;a href="https://aiskills402.com/blog/redos-regex-locks-server?utm_source=devto&amp;amp;utm_medium=social" rel="noopener noreferrer"&gt;https://aiskills402.com/blog/redos-regex-locks-server?utm_source=devto&amp;amp;utm_medium=social&lt;/a&gt;&lt;/p&gt;

</description>
      <category>debugging</category>
      <category>testing</category>
    </item>
    <item>
      <title>Why your prompt cache never hits, and what it saves</title>
      <dc:creator>Georgi Kalchev</dc:creator>
      <pubDate>Fri, 13 Nov 2026 07:00:51 +0000</pubDate>
      <link>https://dev.to/georgi_kalchev_85d01f7368/why-your-prompt-cache-never-hits-and-what-it-saves-33ok</link>
      <guid>https://dev.to/georgi_kalchev_85d01f7368/why-your-prompt-cache-never-hits-and-what-it-saves-33ok</guid>
      <description>&lt;p&gt;A prompt cache pays only when the start of every request is identical and calls come often enough. The usual reasons it misses, and a way to check.&lt;/p&gt;

&lt;p&gt;A prompt cache lets the API remember the beginning of a request, so the next request that starts with exactly the same text does not pay full price to process it again. When it works, repeated calls get cheaper and start answering sooner. When it does not, you pay for the marks you added and get nothing back, and no error tells you so. The only sign is a usage counter that stays at zero. This guide explains what has to be true for a hit, the five ordinary reasons for a miss, and a short routine for finding out which one applies to you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the full report on AISkills402:&lt;/strong&gt; &lt;a href="https://aiskills402.com/blog/prompt-caching-misses?utm_source=devto&amp;amp;utm_medium=social" rel="noopener noreferrer"&gt;https://aiskills402.com/blog/prompt-caching-misses?utm_source=devto&amp;amp;utm_medium=social&lt;/a&gt;&lt;/p&gt;

</description>
      <category>debugging</category>
      <category>testing</category>
    </item>
    <item>
      <title>From Postgres or MySQL to SQLite and D1: what breaks</title>
      <dc:creator>Georgi Kalchev</dc:creator>
      <pubDate>Thu, 12 Nov 2026 15:00:53 +0000</pubDate>
      <link>https://dev.to/georgi_kalchev_85d01f7368/from-postgres-or-mysql-to-sqlite-and-d1-what-breaks-47a1</link>
      <guid>https://dev.to/georgi_kalchev_85d01f7368/from-postgres-or-mysql-to-sqlite-and-d1-what-breaks-47a1</guid>
      <description>&lt;p&gt;Moving SQL from Postgres or MySQL to SQLite and D1 mostly parses fine and then misbehaves. Keys, enums, dates, division, upserts and D1 limits explained.&lt;/p&gt;

&lt;p&gt;Most SQL written for Postgres or MySQL gets through the SQLite parser without complaint, and that is exactly the danger. SQLite is lenient about type names and about words it does not recognise in a column definition, so a dump from another engine often creates every table and then quietly stores, checks or calculates something different from the original. The statements that fail loudly are the lucky ones. This guide lists the conversions that succeed and still go wrong, why each happens according to the engines' own documentation, and what to write instead for SQLite and Cloudflare D1, which runs SQLite underneath.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the full report on AISkills402:&lt;/strong&gt; &lt;a href="https://aiskills402.com/blog/postgres-mysql-to-sqlite-d1-breakage?utm_source=devto&amp;amp;utm_medium=social" rel="noopener noreferrer"&gt;https://aiskills402.com/blog/postgres-mysql-to-sqlite-d1-breakage?utm_source=devto&amp;amp;utm_medium=social&lt;/a&gt;&lt;/p&gt;

</description>
      <category>sqlite</category>
      <category>cloudflare</category>
      <category>debugging</category>
    </item>
    <item>
      <title>What counts as a breaking change in an OpenAPI spec</title>
      <dc:creator>Georgi Kalchev</dc:creator>
      <pubDate>Thu, 12 Nov 2026 07:00:56 +0000</pubDate>
      <link>https://dev.to/georgi_kalchev_85d01f7368/what-counts-as-a-breaking-change-in-an-openapi-spec-1d63</link>
      <guid>https://dev.to/georgi_kalchev_85d01f7368/what-counts-as-a-breaking-change-in-an-openapi-spec-1d63</guid>
      <description>&lt;p&gt;A breaking change depends on which way the data flows. Requests may loosen and responses may tighten; the reverse breaks clients. A field guide with examples.&lt;/p&gt;

&lt;p&gt;A breaking change is any edit to an API description after which a client written against the old description stops working against the new one. Every other edit is safe. That sounds obvious, but in practice people sort changes by how big they look: a removed endpoint feels dangerous, a new enum value feels harmless. The better question is which way the data travels. A client sends requests and reads responses, so the same edit can be safe on one side and harmful on the other. Below you will find the direction rule, the edits that are most often misjudged, and a short routine for reviewing pull requests.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the full report on AISkills402:&lt;/strong&gt; &lt;a href="https://aiskills402.com/blog/openapi-breaking-changes?utm_source=devto&amp;amp;utm_medium=social" rel="noopener noreferrer"&gt;https://aiskills402.com/blog/openapi-breaking-changes?utm_source=devto&amp;amp;utm_medium=social&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>json</category>
    </item>
    <item>
      <title>Next.js caching: ISR, cache tags and redirects</title>
      <dc:creator>Georgi Kalchev</dc:creator>
      <pubDate>Wed, 11 Nov 2026 15:00:56 +0000</pubDate>
      <link>https://dev.to/georgi_kalchev_85d01f7368/nextjs-caching-isr-cache-tags-and-redirects-3oaj</link>
      <guid>https://dev.to/georgi_kalchev_85d01f7368/nextjs-caching-isr-cache-tags-and-redirects-3oaj</guid>
      <description>&lt;p&gt;Five caching mistakes in a Next.js project that pass every local run: ISR that never starts, a stale cache key, tag storms and redirects over cached 404s.&lt;/p&gt;

&lt;p&gt;Caching bugs in a Next.js project rarely show up on a developer's laptop. The local server rebuilds often, the cache starts empty, nobody has visited the old address, and the database is small. The same code in production then serves an old answer, or reads the database far more often than anyone planned. This guide covers five places where that gap opens: incremental static regeneration that never starts, a cache key that outlives the data shape it guards, tag invalidation fired on every write, redirects laid over cached error pages, and middleware that skips the files crawlers ask for first. Each section says what to look at and how to check it on a deployed address.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the full report on AISkills402:&lt;/strong&gt; &lt;a href="https://aiskills402.com/blog/nextjs-cache-isr-tags-redirects?utm_source=devto&amp;amp;utm_medium=social" rel="noopener noreferrer"&gt;https://aiskills402.com/blog/nextjs-cache-isr-tags-redirects?utm_source=devto&amp;amp;utm_medium=social&lt;/a&gt;&lt;/p&gt;

</description>
      <category>opennext</category>
      <category>debugging</category>
      <category>cloudflare</category>
    </item>
    <item>
      <title>server.json fields that get an MCP listing refused</title>
      <dc:creator>Georgi Kalchev</dc:creator>
      <pubDate>Wed, 11 Nov 2026 07:00:54 +0000</pubDate>
      <link>https://dev.to/georgi_kalchev_85d01f7368/serverjson-fields-that-get-an-mcp-listing-refused-2k33</link>
      <guid>https://dev.to/georgi_kalchev_85d01f7368/serverjson-fields-that-get-an-mcp-listing-refused-2k33</guid>
      <description>&lt;p&gt;The MCP registry checks a server.json against a schema and against proof of ownership. Name, version, description and package proof cause most refusals.&lt;/p&gt;

&lt;p&gt;A server.json file is refused by the official MCP registry for two different kinds of reason. Some fields fail the published JSON Schema: a description that is too long, a version written as a range, a name with the wrong shape. Others pass the schema and then fail a check the registry runs at publish time, which asks whether the person publishing really controls the name and the package. The first kind can be caught with a validator. The second kind needs a look at the package itself, and it is where most of the confusion lives. This guide goes through both, field by field, so a file can be checked before the publish command is run.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Read the full report on AISkills402:&lt;/strong&gt; &lt;a href="https://aiskills402.com/blog/mcp-registry-server-json-fields?utm_source=devto&amp;amp;utm_medium=social" rel="noopener noreferrer"&gt;https://aiskills402.com/blog/mcp-registry-server-json-fields?utm_source=devto&amp;amp;utm_medium=social&lt;/a&gt;&lt;/p&gt;

</description>
      <category>mcp</category>
      <category>json</category>
      <category>debugging</category>
    </item>
  </channel>
</rss>
