Latest

One of the common challenges developers face when using the React Context API involves juggling with numerous Context Providers, sometimes leading to a "Provider Chaos, but this can be easily solved with composition."

It's probably been three years since I discovered the Nim programming language. Back then, it had not yet reached version 1.0 despite having been in development for almost a decade. I was intrigued by it's claims and features but didn't take a deep dive.

SSH includes an awesome feature called ProxyJump that allows an SSH connection to used as a proxy for a subsequent SSH connection. In cases where you want every connection you make to a server to be routed via a jump host or many jump hosts, you can permanently configure behaviour for a server in ~/.ssh/config. Jump hosts are an incredibly powerful feature of SSH and are so easy to configure that you can often set it and forget it. You can combine this features with SSH port forwarding, X11 session forwarding, or SSH agent forwarding and navigate any number of restricted or complicated network setups.

I've mostly skimmed the Wireguard articles and blog posts I've come across without ever actually taking it for a spin. However, I've recently deployed an entire stack of self-hosted services on Digital Ocean and at the same time have been building up the services I have running on my home server for serving media and handling home automation. For management and backup purposes I decided it would be beneficial for both of these hosts to share a private network so that they could connect to each other as if they were both on my home lan. In the past I would have created an IPSec tunnel between the hosts and given them a route to each other using that tunnel. But, not today! Wireguard!

Applications are getting larger and harder to manage but we've also developed excellent tooling to manage the growth. Gone are the days of running web and database servers directly on your workstation only to find out after you've pushed your code to master and the production server is running a different version of PHP or a very different web server configuration. Docker and Compose have solved this problem for us.