madflojo
Show HN: Go Style Agent Skill – Opinionated Skill for Writing Golang
Generating code faster is only valuable if you can validate every change
Migrating the American Express Payment Network, Twice
Microblog: Performance Testing – Benchmarks vs. Endurance
Are Atomic Operations Better Than a Mutex? It Depends
Cell-Based Architecture Explained, with Zombies
Show HN: Dynamically generate self-signed certs for Go unit tests
Best practices for managing BASH scripts
Show HN: Encode/Decode Message Length Indicators for ISO8583 Based Messages
Efs2: Dead-simple config management powered by shell scripts (New Release)
How I Structure Go Packages
hoverfly looks a lot easier than most of the more popular solutions out there.
Show HN: MockItOut – A language agnostic HTTP mock server for quick stub testing
Show HN: Tasks – An easy to use in-process scheduler for recurring tasks in Go
I tried to insert some of the benefits we are seeing into the article in different pieces but now that we are several years later have it running in production. We are happy with the decision. In my opinion, there are even some newer things we didn't write in Go that I kind of wish we did.
The reasons we choose Go are holding true, and I can't say enough about how the performance and low GC times out of the box is something that is very beneficial. At least for my use cases.
Appreciate the read and questions though!
As far as dotNet Core, it is used at AXP but generally not in our high performance environments. Not saying it couldn't as I'd have to do a lot more research to say one way or another on that. But I'd say that's the primary reason it wasn't added to the list.