<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Go on Severin Bucher | Blog</title><link>https://severinbucher.com/tags/go/</link><description>Recent content in Go on Severin Bucher | Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 24 Apr 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://severinbucher.com/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>Modern API Development with TypeSpec and OpenAPI</title><link>https://severinbucher.com/posts/modern-api-development-with-typespec-and-openapi/</link><pubDate>Thu, 24 Apr 2025 00:00:00 +0000</pubDate><guid>https://severinbucher.com/posts/modern-api-development-with-typespec-and-openapi/</guid><description>&lt;p>Designing clear, well-documented web APIs is a big part of building software. The most widely adopted standard for describing RESTful APIs is OpenAPI, a machine-readable format (usually JSON or YAML) that defines an API&amp;rsquo;s structure, endpoints, and request and response shapes. That schema becomes the single source of truth behind your interactive docs, client libraries, and server stubs.&lt;/p>
&lt;p>However, writing and maintaining OpenAPI specifications by hand can quickly become a chore. The syntax is verbose, and small mistakes in the structure can lead to frustrating bugs or inconsistencies across different parts of the system.&lt;/p></description></item></channel></rss>