Menu

Teams Need Protocols Too: Lessons from Building Go Backends Together
📰

Teams Need Protocols Too: Lessons from Building Go Backends Together

DEV Community: go·Jeff Ronnie·about 14 hours ago
#vC8OvfHk
#devtogo#devto#dev#code#frontend
Reading 0:00
15s threshold

Building a Go backend alone is one kind of difficulty. Building one with three or four other people, each owning a slice of it, is a different kind entirely.

At Zone01 Kisumu I've now done this twice: first a web forum , then a Facebook-style social network with a Go backend and a Next.js frontend. The code in both projects was the easy part. What caught me out was the space between people's code: assumptions that never got written down, names that didn't match, functions one person thought another had written.

This article is about those gaps, and the habits I've adopted to close them. It's written from a beginner's perspective, but I think the lessons hold up.

Project one: the forum

The forum was a team project in Go with SQLite, session authentication, Go template rendering, routing and Docker containerisation.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.