clockworksoul

22 ms·

241.
Why do programmers start counting at zero? (2013)(exple.tive.org)
2 points by clockworksoul 7y ago|0 comments
242.
Decider: Distributed Feature Flags(github.com)
2 points by clockworksoul 7y ago|0 comments
243.
by clockworksoul 8y ago
Who's voting this up?
244.
Docker Zen: Achieving true minimalism with “distroless” images(very-serio.us)
3 points by clockworksoul 9y ago|0 comments
245.
Applying Conway’s Law (2013)(haacked.com)
2 points by clockworksoul 9y ago|0 comments
246.
Running JVMs in Kubernetes(very-serio.us)
3 points by clockworksoul 9y ago|0 comments
247.
Researchers find an enzyme that harvests light to make hydrocarbons(arstechnica.com)
3 points by clockworksoul 9y ago|0 comments
248.
by clockworksoul 10y ago
Author here. A pleasure to meet you. I'm a big fan of Hashicorp. Truth be told, when I started this project I wasn't aware of memberlist, though I was by the time I finished. I was building something beautiful and I didn't wa
249.
by clockworksoul 10y ago
I think you may be misreading the section regarding projects that you develop on your own time with your own equipment (unless I'm misreading it, which is also very possible): > "Any provision in this Agreement requiring Employ
250.
by clockworksoul 10y ago
Note that this is my first real project in Go, and that this will essentially be the first time that it's been looked at by eyes besides mine. It may have holes; possibly glaring ones. Please be gentle. :)
251.
Smudge: A lightweight Go implementation of the SWIM epidemic protocol(github.com)
4 points by clockworksoul 10y ago|1 comments