Chaining should be an operator in the language itself
What is chaining?
Happy 100th birthday, Finland!
Perkele! Finland just turned 100 years.
- Why Slack is inappropriate for open source communications
- A Keepass-like project I’m working on
- My woodworking hero Matthias Wandel made me have an epiphany: how CPU works on the lowest of levels. Addition is basically just chained XOR gates, and a XOR gate is basically just transistors anyway. All this can be explained with wood and marbles! And in the end all higher constructs like 2D, 3D graphics, audio, video can be explained with just simple maths, so basically you now understand all that the CPU does and that it’s not magic. All other complex things like video and audio compression codecs/algorithms are just necessary optimizations on top of simple math.
- I’m loving this series: Stuff The Internet Says On Scalability For May 26th, 2017
- Understand Go pointers in less than 800 words or your money back
- Great summary of ACID: Log-structured storage
- Like many other things, cross compilation is pleasantly easy in Go: Cross compilation with Go 1.5
- A few things I’ve learned about Kubernetes
- Extracting .tar.gz files in Golang
Implementing your hiring process with C trivia
I got a newsletter from Toggl (a time-tracking app) that they are hiring and that they had a coding quiz. I decided to take the quiz just for shits and giggles.
Concurrency in Golang and the importance of using locks
Have this innocent looking code in Golang:
Problems with Microsoft Azure´s networking
The problem with "cute coding"
For lack of a better term, I call this “cute coding”:
Stop using protocol-relative URLs
I still see this confusingly often, even with Twitter’s timeline embedding feature. Protocol relative URLs look like this: