Top all-time · #2070
Peter Bourgon
Personal blog · peter.bourgon.orgprogrammingsystems
Peter Bourgon's personal blog at peter.bourgon.org covers programming and systems. Since 2014, 38 different Hacker News readers have linked it 52 times, most often “Go for Industrial Programming”. No feed was found, so read it on the site itself.
Peter Bourgon has a web site, and this is that web site.
Most-linked posts?
- Go for Industrial Programming7 people · 7 mentions · first linked 2018-06-02
- Observability Signals3 people · 3 mentions · first linked 2018-08-22
- Go: Best Practices for Production Enviroments2 people · 2 mentions · first linked 2014-04-27
- Semantic Import Versioning is unsound2 people · 2 mentions · first linked 2020-09-14
- A case for microservices2 people · 2 mentions · first linked 2015-11-17
- A response about dep and vgo2 people · 2 mentions · first linked 2018-07-27
- Observability: the hard parts2 people · 2 mentions · first linked 2018-06-17
- OK Log2 people · 2 mentions · first linked 2017-01-17
- Don't use build tags for integration tests2 people · 2 mentions · first linked 2021-04-03
- Go best practices, six years in2 people · 2 mentions · first linked 2016-05-01
What Hacker News says?
I don't know the real relationship between Google and Go, but Go is very much a product of its current core team, who are (AFAIK) all veterans of Bell Labs (Robert Griesemer?) and all have the same Bell Labs approach. Bell Labs invented Not Invented Here syndrome. You can know this to be true because there is no way this group of people could have the syndrome so bad any other way. The other side of the coin is that…
Comment linking /blog/2018/07/27/a-response-about-dep-and-vgo.html.[%5E1][%5E2]
on “Go is Google's language, not ours”Submitted Go best practices, six years in as a story · 440 points
HN discussionGo modules is exactly the reference case, but let me expand on that a smidge, because that was when this become crystal-clear to me. There's one exchange in a blog post linked from the article[1] about dep/modules that I think is illustrative of the entire issue (double >> are quotes in the article from Google/go, single > are commentary from the linked blog author): >>Although it was a successful experiment, Dep is…
Comment linking /blog/2018/07/27/a-response-about-dep-and-vgo.html
on “Go is Google's language, not ours”Submitted Go best practices, six years in (2016) as a story · 274 points
HN discussionThis is fun. Here's mine: - Brad fitzpatrick -- http://bradfitz.com/ - Julia Evans -- https://jvns.ca - Raymond Hettinger -- https://rhettinger.wordpress.com/ - Rich Hickey -- https://changelog.com/posts/rich-hickeys-greatest-hits - Peter Bourgon -- https://peter.bourgon.org/ - Rebecca Murphey -- https://rmurphey.com/ - Daniel Greenfield -- https://www.twoscoopspress.com/
Comment linking /
on “Ask HN: Which developers do you closely follow?”Submitted Go: Best Practices for Production Enviroments as a story · 222 points
HN discussionI'm assuming they are the ones listed here: https://peter.bourgon.org/talks/
Comment linking /talks/
on “Go best practices, six years in”Submitted A response about dep and vgo as a story · 149 points
HN discussionYup. Somewhat formalized: https://peter.bourgon.org/blog/2018/08/22/observability-sign...
Comment linking /blog/2018/08/22/observability-signals.html
on “Log by time, not by count”Submitted Go kit: Go in the modern enterprise as a story · 140 points
HN discussionSee the "Managing Dependencies" section, and comments: https://www.digitalocean.com/company/blog/get-your-developme... Also: http://peter.bourgon.org/go-in-production/#dependency-manage... More discussion: https://news.ycombinator.com/item?id=7971354
Comment linking /go-in-production/
on “The March Towards Go”Submitted A theory of modern Golang as a story · 130 points
HN discussion> [go get] Only works for source code packages, not > binary dependencies. There's no such thing as a binary dependency in the Go ecosystem. (At least, not without stretching some definitions.) It's one of Go's greatest strengths, actually. > There isn't a way to specific source code versions/tags > in a portable way. Well, the best practice is to vendor[0], and there are plenty of third-party tools like godep[1] th…
Comment linking /go-in-production/
on “GopherCon 2014 Videos”Submitted The nihilist and optimist programmers (2015) as a story · 114 points
HN discussionHere's the blog post describing the system https://peter.bourgon.org/ok-log/ And the original HN post https://news.ycombinator.com/item?id=13418125
Comment linking /ok-log/
on “A distributed and coordination-free log management system”Submitted Logging vs. instrumentation as a story · 72 points
HN discussionHere's a question from someone who is recently out of school and somewhat new to Go. Is it OK to use Context for request-scoped values? i.e. passing data between middleware? I have started doing this, but is there a better alternative? Peter Bourgon's blog post[0] about context made me think it is fine. After reading the comments here, I am not so sure. Especially since his post was roughly 4 years ago. 0: https://p…
Comment linking /blog/2016/07/11/context.html
on “An interesting mistake with Go's context package”Submitted OK Log as a story · 44 points
HN discussionGood addition! Here are some more: https://ferd.ca https://blog.filippo.io https://lethain.com http://movingpackets.net https://www.integralist.co.uk https://peter.bourgon.org/blog https://engineering.linkedin.com/blog https://begriffs.com https://mijailovic.net http://tatiyants.com http://blog.pentestbegins.com (seems down right now?) https://kalzumeus.com/archive http://blog.stephenwolfram.com https://paragonie.co…
Comment linking /blog
on “Ask HN: What are some of the tech blogs you follow regularly?”Submitted What's appropriate to put in a Go Context? as a story · 16 points
HN discussion> I'm an engineer too Yep! Point is, we all are, so we all have to worry about how things break in practice, not only about the theoretical model of compatibility. And it turns out we break each others' code lots of ways, sometimes even just changing behavior without touching the API. If I had a tool that detected certain build-time problems and worked around others, I could still end up upgrading to a new version o…
Comment linking /go-best-practices-2016/
on “Backwards compatibility in Go (2015)”Submitted A case for microservices as a story · 15 points
HN discussionMy first resources were the Go website, specifically the following pages/articles: How to Write go Code [1], Effective Go [2] and Frequently Asked Questions [3]. I also read Alan Donovan and Brian Kerninghan's book "The Go Programming Language" [4]. So mostly these four, and of course simply writing code (along with the standard library documentation [5]). Since then I've also gained a lot of info and insight from v…
Comment linking /articles/
on “Python, Go or Haskell?”Submitted Semantic Import Versioning is unsound as a story · 9 points
HN discussionI don't think it would be fair to say that the Go community optimizes for productivity over good software development practices. In fact, there's been a good push in the community lately to talk about application design and what it means for code to be good/not good. * https://github.com/marcusolsson/gouk16-slides/blob/master/bu... * https://peter.bourgon.org/go-best-practices-2016/ * http://dave.cheney.net/2016/08/…
Comment linking /go-best-practices-2016/
on “Test-Driven Development of Go Web Applications with Gin”Submitted Go: Best Practices for Production Environments as a story · 7 points
HN discussionPlease don't use build tags for integration tests: https://peter.bourgon.org/blog/2021/04/02/dont-use-build-tag... Along with the issues listed here you will run into issues with editors not building/linting your tests files because they have build tags that the editor is unaware of. You can also put the environment variable in a TestMain[1] to cover an entire package of integration tests: func TestMain(m *testing.M…
Comment linking /blog/2021/04/02/dont-use-build-tags-for-integration-tests.html
on “How to start a Go project in 2023”Submitted Go for Industrial Programming as a story · 5 points
HN discussionSubmitted Go for Industrial Programming as a story · 3 points
HN discussionSubmitted Go for Industrial Programming as a story · 3 points
HN discussion
