Bartłomiej Klimczak

@bklimczak
1 Followers
14 Following
32 Posts
Go Software Engineer, @GoogleDevExpert
in #go Category, blogger, organizer of a meetup
@CracowGo, speaker, and trainer. I teach Go for business development.
bloghttps://developer20.com/
githubhttps://github.com/bkielbasa
Get up to speed with profiling your Go applications 🚀! Dive into Part 1 of my pprof Quick Start series and learn how to enhance your code’s performance in just 10 minutes! 📷 Read now: https://developer20.com/pprof-part1-quick-start/ #GoLang #Profiling #DevTools #PerformanceTuning
Part 1: pprof Quick Start - Get Profiling in 10 Minutes

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!

Microsoft wants to disable the option to have a local account. The fact they serve ads on the start menu forced me to never install windows on any pc anymore
Unpopular opinion: Table tests are overused in #golang and shouldn't be used in testing business logic.
observability tip: First start logging and later transfer your logs into meaningful metrics. Thanks to that you'll and up in a set of metrics that you really care about and limited number of logs that are hard to search.
In #golang,structs are just a container for data. Nothing more and nothing less. Don't try to use them as classes in other languages.

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?

discussion: spec: reduce error handling boilerplate using ? · golang go · Discussion #71460

This is a discussion about a new syntax that may be used to handle errors. This is issue #71203 converted into a discussion. I've written a tool that converts ordinary Go code into code that uses t...

GitHub

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.

I noticed that the most misused thing in #golang are interfaces. We use them as we do in Java/PHP/C#, etc