Language:
Backend
Guessing at performance problems wastes days. Go includes a profiler that shows where CPU time and memory actually go. This walkthrough covers collecting CPU, heap, and allocation profiles, reading flame graphs, and fixing the problems they reveal most often.
Sep 24, 2026·5 min read
Go's explicit errors and flat packages feel easy early on and cause friction at 50,000 lines. This article covers the conventions that keep a growing Go service readable: wrapping errors with context, sentinel and typed errors, and a package layout organized around behavior.
Showing 64-65 of 65 articles
Tell us about your project — we'll help you get there.
By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyse site usage, and assist in our marketing efforts.
Choose which cookies we may use. Strictly necessary cookies keep the site working and are always on.