Tag: api
Future of staff-level engineering, MCP auth, CLI dev, new GraphQL tagline, governance by default, API vs. Tool design
Week of 2026-08-10 roundup
Updated my 13 year old API mashup, Monarch Migration Explorer, to use Leaflet & OpenStreetMap instead of Google Maps. Take a look at where Monarch butterflies have been spotted over the last several years at https://monarchs.johnbeales.com
Announcing API v3
We are happy to announce API v3, which will allow you to save and share multi-wheels! You can reach the documentation from https://wheelofnames.com/api-doc.
APIクライアントTUIのPostingが良さげかも
ターミナル上でAPIの開発・テストができるクライアントPostingの紹介です。
Accepted proposal: range over all command-line flags
The flag package is getting a range-friendly iterator and a direct way to tell whether a flag was set successfully.
Accepted proposal: Go examples with any signature
Go examples with parameters or results can appear in documentation without becoming tests.
AT Protocol MCP Server: API Expansion Phase 1
AT Protocol MCP Server: API Expansion Phase 1
ターミナルで使えるAPIクライアントRestermが良さげかも
複数プロトコルに対応したAPIクライアントTUIのRestermの紹介です。
Type-safe slogging
The default slog API is loose enough that a careless line ships broken JSON to production. Pin it down with Attr constructors, LogAttrs, a context-borne logger, and sloglint.
Hoisting wire plumbing out of your Go handlers
Four of the five steps in every unary RPC handler are wire plumbing. Pin the service function signature and they fit in one generic adapter per transport.
Accepted proposal: UUID in the Go standard library
Notes on Go's newly accepted uuid proposal and the tradeoffs behind the API.
API Versioning is a Contract Commitment, not a Technical Choice
What's the ideal dispatch mechanism?
Switch, map of functions, and interface registry for dispatching in Go.
Observability as a design requirement
Observability is a design decision, not an afterthought. From the platform team to API consumers to AI agents, knowing what is happening across your API — and building that in from the start — is what gives you confidence when things go wrong in production.
Is passing user ID through context an antipattern?
Why the middleware-to-handler boundary is a special case for context values.
What belongs in Go's context values?
A simple litmus test for when to use context values in Go.
Wrapping a gRPC client in Go
How to wrap a generated gRPC client behind a clean Go API so users never have to touch protobuf types or connection management directly.
Designing for Multi-Region API Deployments
A practical guide to designing multi-region API deployments - covering data consistency, auth dependencies, traffic routing, and failure modes, with real-world lessons from IBM API Connect SaaS.
Mutate your locked state inside a closure
Why your mutex wrapper should accept a closure for mutation instead of a plain value, with examples from the standard library and Tailscale.
Your Go tests probably don't need a mocking library
Practical patterns for mocking in Go without external libraries. Learn to mock functions, methods, interfaces, HTTP calls, and time using only the standard library
Programmatically Setting GitHub Issue Types
A quick guide on how to programmatically set the GitHub issue type with the GitHub CLI, even if built-in functionality for this doesn't quite exist.
Verifying Clerk JWTs in Cloudflare Workers
Authentication typically happens in one of two places: the frontend checks if a user is logged in before showing protected UI, and the backend validates tokens before processing requests. There's a third option—verifying JWTs at the edge, in a Cloudflare Worker, before requests reach your backend infrastructure. This approach rejects unauthenticated requests at the edge, preventing them from consuming backend resources. It keeps your authentication provider's secrets out of your backend infras
Securing API Keys with AWS Secrets Manager and Cloudflare Workers
API keys for backend authentication create a fundamental challenge in web applications: the credentials need to authenticate requests but cannot be exposed to clients. Hardcoding keys in frontend bundles or environment variables leaves them visible in browser developer tools. Anyone who opens the network tab can extract the key and make unauthorized requests. Static configuration files require manual rotation and create operational risk—when a key needs to change, someone has to remember to upda
Community
Dev Log 38: 2025-12-18
Revisiting interface segregation in Go
Apply SOLID's Interface Segregation Principle in Go with consumer-defined contracts. Learn why small interfaces and implicit implementation matter.
Avoiding collisions in Go context keys
Master Go context keys with custom types, avoid collisions using empty structs, and learn accessor patterns for safe request-scoped values.
Lifecycle management in Go tests
Master Go test lifecycle with t.Cleanup(), subtests, and TestMain. Learn per-test, grouped, and package-wide setup patterns effectively.
Deploying AWS Applications with Cloudflare Workers and Cloud Connector
A comprehensive guide on using Cloudflare as a security and CDN layer for AWS-hosted applications, with edge-level API key injection
Stop Guessing: MCP Elicitations Come To Visual Studio Code
VS Code now supports MCP elicitations from the 2025-06-18 spec, letting servers prompt users with structured native dialogs instead of guessing at parameters.
Please Don't Write Your Own MCP Authorization Code
Why most teams should let an API gateway handle the new MCP Protected Resource Metadata flow instead of hand-rolling OAuth in their own server code.
Confused Deputy Attacks In MCP, Solved With Azure APIM
Mitigating confused deputy attacks in remote MCP servers by enforcing per-client consent prompts and proxying Dynamic Client Registration through Azure APIM.
You probably don't need a DI framework
Dependency injection in Go doesn't need Dig or Wire. Learn why manual wiring beats reflection magic and how Go's design makes DI frameworks overkill.
Secure S3 Image Uploads and Viewing with Presigned URLs and Cognito
A deep dive into securely managing user-specific image uploads to S3 using presigned URLs and authorizing access for viewing with AWS Cognito.
Building Personal APIs
In which the author steals his data back from various tools and APIs and uses them to build his own panopticon-for-one
Deferred teardown closure in Go testing
Return teardown closures from test helpers to manage cleanup elegantly. Learn patterns for temp files, mock servers, and t.Cleanup() usage.
Stacked middleware vs embedded delegation in Go
Compare middleware stacking with embedded delegation in Go HTTP servers. Learn when to override ServeHTTP for simpler request handling.
Using GitHub Copilot From Inside GitHub Actions
Call the undocumented GitHub Copilot REST API from inside a GitHub Actions workflow to extract structured data from issue bodies without manual parsing.
無料の翻訳API、みんなの自動翻訳を使ってみた
Artem Zakharchenko - Mock Service Worker
Artem Zakharchenko explains Mock Service Worker's network request mocking capabilities, technical evolution, and future automation features.
Deleting All Workflow Runs In GitHub Repository With PowerShell
A PowerShell script that paginates the GitHub REST API to bulk-delete every workflow run in a repository, with rate-limit handling and dry-run support.
Securing API Gateway with Lambda@Edge
A detailed guide on implementing secure API Gateway endpoints using Lambda@Edge for request verification and API key management
Function types and single-method interfaces in Go
Implement single-method interfaces with function types instead of structs. Master http.HandlerFunc patterns for middlewares, mocks, and adapters.