Always wanted your terminal to look and function like that of a professional developer? This post is my attempt at providing a concise guide to setting up a modern terminal, while explaining essential terminology and decisions made along the way.

To make for a truly slick experience, I have considered different terminals, shells, prompts and hotkeys, as well as command-line tools and plugins, including typeahead and fuzzy search.

I've built a server that's both powerful and quite energy efficient. It has modern hardware running on less than 10 Watts!

While ordering parts for my new energy efficient server, I ended up buying a second hand I7 9700K processor.

When the piece had arrived, I was surprised to see a chunk of dirt that was burnt in, seemingly connecting some contact points together. I was worried that this would cause a short circuit and damage the CPU.

The other day I got into an interesting conversation with someone (random) from Brazil after discussing some game design aspects inside the #feedback channel on a closed beta of a new game. I'll refer to them as Raiane for this short story.

For some developers choosing the right stack for an application may seem like a trivial task; simply follow best practices and choose the most modern well-supported tools out there.

While this approach will usually lead to a successful outcome, I've found that spending just enough time up-front has led me to create working products much faster and with less effort.