
Do You Need a Go Web Framework or Just net http Alone
Write one small notes API twice, with net/http and with gin, and compare the code you write, where the behavior differs and what the framework really saved.
Everything you need to level up your coding skills.

Write one small notes API twice, with net/http and with gin, and compare the code you write, where the behavior differs and what the framework really saved.

How a Go API should wrap its JSON: bare resources, a data envelope for lists, empty arrays instead of null, optional totals, and why to skip a success flag.

Serve HTTPS from a Go program with autocert and Lets Encrypt, limit which hostnames may get certificates, persist the cache and handle port 80.

Generate a valid RSS 2.0 feed in Go with encoding/xml: required fields, stable GUIDs, RFC 1123 dates, absolute URLs, escaping and conditional GET.

Write JSON marshalers in Go for enums, dates, durations and Unix times: MarshalText versus MarshalJSON, clear errors, the pointer receiver trap and recursion.

Add strong ETags and If-None-Match handling to Go handlers, including weak comparison, lists of tags and a 304 that repeats the right headers.

Build a contacts directory with templ and HTMX: live search, endless scroll, click to edit with validation, delete with an out of band count and fragments.

Generate, store and rotate API keys in Go: a prefixed format with a checksum, SHA-256 storage, throttled last-used, overlap rotation and 85 ns rejection.

Test Go middleware one piece at a time with a spy handler, then test the whole chain for order, short circuits, panics, headers and context values.

A one page templ cheat sheet: component syntax, control flow, attributes, css and script components, children, fragments, helpers and commands in one program.

Build a server sent events endpoint in Go with flushing, event ids, Last-Event-ID resume, heartbeats and clean shutdown, and see the wire format it sends.

Build the sending side of webhooks in Go: signed deliveries, a retry schedule that honors Retry-After, permanent versus temporary failures and dead endpoints.
We send one email when a new article is published. No spam.