Newsletter 57 – 11/2024

Featured

7 simple habits of the best engineers I know – World class post. All habits described in this post are simple and effective and its a common pattern on amazing engineers that I know too. A must read post for career growth.

A career ending mistake – Another amazing post about career growth and decisions that we need to take during our journey. This post explains briefly the three more common career paths for tech workers.

How I ship projects at big tech companies“Shipping is a social construct within a company. Concretely, that means that a project is shipped when the important people at your company believe it is shipped.”

Australia/Lord_Howe is the weirdest timezone – There are some weird timezones around, and this post show some curious things about some of them.

MISC

Netflix’s Distributed Counter Abstraction – Count things in distributed systems is hard, count in distributed systems with massive load is even harder. This post from Netflix talks about how they solve this problem.

How to get more headcount. – Get headcount is a not so funny task that every team/manager faces, this post give some tips about how to get it.

Everything I’ve learned so far about running local LLMs – Running LLMs locally can be fun (and useful), and you don’t need a heavy machine to start doing it.

Blog Writing for Developers – Write is not easy, and write a blog for developers is even harder, decisions about clarity, voice, and style need to be made. This post brings nice insights about writing.

Writing secure Go code – Few tips about how to improve the Go code security.

Building thread-safe abstractions in Java versus Go – One of the main points of selling Go is how it is easier to build concurrent applications easily, this post compares the same concurrent code in Go and Java.

A brief summary of language model finetuning – Before this post I didn’t know nothing about how language models are finetunned or even that there are more than one way. Very simple and informative post.

Hyrum’s Law in Golang – A simple code law/principle to avoid problems while maintaining code that many places depends on, especially useful for libraries.