in #go Category, blogger, organizer of a meetup
@CracowGo, speaker, and trainer. I teach Go for business development.
| blog | https://developer20.com/ |
| github | https://github.com/bkielbasa |
| blog | https://developer20.com/ |
| github | https://github.com/bkielbasa |
There is a big mistake that we still keep making - big bang deployments.
I’ve seen many project that failed or partially failed because the tried to make too big change at a time.
I'm extending my #homelab. I have a k8s with master (rpi4) and a worker (old laptop). I've just bought a minipc and installed proxmox there. The plan is to run 2-3 k8s workers on it.
Keep fingers crossed!
I saw a discussion about ? operator in #golang regarding error handling https://github.com/golang/go/discussions/71460
Personally, it looks a bit weird for me. WDYT?
If you want to know how frameworks work - write your own.
If you want to know how a databases work - write your own.
If you want to know how XYZ work - write your own.
There's a difference between reading about/using something and developing it yourself. I better understood how a game engine works when I was implementing my own.
Even if there's a tons of things you're reimplementing, things you'll learn are precious.