Saying ‘I don’t know’ might be one of the hardest things in our industry, but a wrong answer costs far more than silence. Why embracing uncertainty makes you a better engineer and a more trustworthy colleague.
The power of ‘I don’t know’
The myth of technical complexity at scale
Developers at large companies often believe they’re solving harder technical problems than their startup counterparts. The reality? The technical challenges are often similar, it’s the politics and disengagement that make things complicated.
Don’t be that person: the dogmatic latecomer
Best practices don’t age well. They emerge to solve specific problems, and when those problems fade, so should the dogma. So why do so many developers adopt techniques without asking what problem they were solving in the first place?
You don’t need Kafka: building a simple yet distributed scheduler in Go
Building a distributed job scheduler doesn’t require Kafka, Redis, or complex coordination protocols. For small-to-medium scale SaaS products, your database can handle the coordination. Here’s how to build one in Go.
Don’t be that person: learn first, blog later
A clickbait blog post claimed errors.Is() slows code by 3000%. The real lesson? The author misused sentinel errors for a non-error condition.