<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Api-Design on The Coders Blog</title><link>https://thecodersblog.com/tag/api-design/</link><description>Recent content in Api-Design on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 01 May 2026 21:06:31 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/api-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Lib0xc: Microsoft's Bid to Make C Systems Programming Safer in 2026</title><link>https://thecodersblog.com/lib0xc-microsoft-s-c-apis-for-safer-systems-programming-2026/</link><pubDate>Fri, 01 May 2026 21:06:31 +0000</pubDate><guid>https://thecodersblog.com/lib0xc-microsoft-s-c-apis-for-safer-systems-programming-2026/</guid><description>&lt;p&gt;Memory corruption bugs continue to plague critical C systems, driving many to declare the language fundamentally broken for modern use. But what if the answer isn&amp;rsquo;t always a wholesale rewrite in Rust, but a smarter, more disciplined approach to C itself?&lt;/p&gt;
&lt;h2 id="the-enduring-paradox-why-c-persists-and-persists-with-risk"&gt;The Enduring Paradox: Why C Persists (and Persists with Risk)&lt;/h2&gt;
&lt;p&gt;The pervasive reality of systems programming highlights C&amp;rsquo;s unparalleled performance, direct hardware access, and minimal runtime overhead. These attributes remain indispensable for operating systems, embedded systems, and high-performance computing, where every byte and cycle counts. C isn&amp;rsquo;t going anywhere, and senior C/C++ developers know this intimately.&lt;/p&gt;</description></item><item><title>Custom Header Naming Convention in HTTP: Best Practices and Conventions</title><link>https://thecodersblog.com/custom-header-naming-convention-http-practices-conventions/</link><pubDate>Tue, 06 Jun 2023 05:25:02 +0000</pubDate><guid>https://thecodersblog.com/custom-header-naming-convention-http-practices-conventions/</guid><description>&lt;p&gt;HTTP headers are the unsung heroes of web communication, carrying crucial metadata that powers everything from authentication to caching. While standard headers like &lt;code&gt;Content-Type&lt;/code&gt; and &lt;code&gt;Authorization&lt;/code&gt; are well-established, modern applications often require custom headers to transmit application-specific data. But here&amp;rsquo;s the challenge: &lt;strong&gt;poor header naming can break APIs, confuse developers, and create security vulnerabilities&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;In 2025, with the rise of microservices, GraphQL, and edge computing, proper header naming has become more critical than ever. This comprehensive guide explores modern HTTP header naming conventions, the evolution beyond the deprecated &amp;ldquo;X-&amp;rdquo; prefix, and battle-tested practices from leading tech companies.&lt;/p&gt;</description></item></channel></rss>