Go Time: Golang, Software Engineering
Technology:Software How-To
Many Gophers build projects as a team of one. Sometimes these are side projects, other times they are projects used by millions of people but who are still maintained by a single individual. In this episode, the panel discusses techniques for developing and maintaining Go projects as a solo developer.
Leave us a comment
Changelog++ members save 2 minutes on this episode because they made the ads disappear. Join today!
Sponsors:
Featuring:
Show Notes:
Something missing or broken? PRs welcome!
Timestamps:
(00:00) - It's Go Time!
(00:44) - Ben Johnson
(01:17) - Solo vs side projects
(05:00) - Does size matter?
(05:47) - How long was BoltDB a side project?
(07:55) - Tips for solo projects in Go
(11:45) - Open vs closed source
(17:59) - Taking contributions
(21:12) - Bringing more people in
(22:59) - Sponsor: Changelog News
(24:33) - How Ian brings others in
(26:43) - How did BoltDB handle support?
(32:25) - Pitfalls of being a solo dev
(38:09) - Feedback templates?
(39:50) - Go specifically
(43:10) - Advice for the newbie
(44:20) - Unpopular opinions!
(44:44) - Ben's unpop
(46:42) - Ian's unpop
(48:37) - Kris' unpop
(51:13) - Bonus unpop
(55:34) - Goodbye!
(55:56) - Outro (Changelog & Friends)
Create your
podcast in
minutes
It is Free