3 ms·
> For example, SoundCloud maintains one monolithic $GOPATH > in a single git repository that they can then > selectively update. No, we tell develop
by sagichmal 12y ago
> For example, SoundCloud maintains one monolithic $GOPATH
> in a single git repository that they can then
> selectively update.
No, we tell developers to use a single $GOPATH on their machine, and check out/edit code directly in the canonical location, e.g. $GOPATH/src/github.com/soundcloud/foosvc
- emeraldd 12y agoHow do you handle a single developer working on multiple features/branches/issues at the same time?
- NateDad 12y agoThis is what source control is for. You switch to the branch and hack on it. In the rare case you need different versions of dependencies, you use a tool like godep (but if you have to resort to that, you're doing something wrong, your dependencies should have stable APIs). Don't use multiple spots on your hard drive for code in source control. Use source control for what it's made for.
- sagichmal 12y agoWhat NateDad said: > This is what source control is for. You switch to the > branch and hack on it. We're also running a microservice (SOA) architecture; each repo represents one service, with one (hopefully) tightly-constrained purpose. It's very rare that we're doing more than 1 or 2 feature branches in a repo at one time.