| 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!
@cobratbq You can think about a struct as a container for ints/strings, floats that leave togther. The data are the important thing. When you write a method for your type, Go compiler just translates it to a regular function with where the first argument is the type. It's a syntactic sugar. Here's an example https://goplay.tools/snippet/VXtIVkZzhMB
Both `Say` functions will generate exactly the same binary code and, in fact, the method will be transformed into a regular function as shown in the second example
@thiht @nemith @cobratbq In Go, interfaces describe a behavior. It means, they don't say what it is but how a specific type can do without the knowlage about what, in fact, it is.
A good example is io.Reader that say we can read from in no matter if it is a file, in memory data or a network resource.