With my Synology NAS already handling Docker workloads, I’m looking to expand its capabilities with some new containers. These will enhance monitoring, automation, note-taking, development, and network management. Here’s what’s on my list:
As my self-hosted network grows, keeping an eye on my Raspberry Pis is becoming more important. With multiple Pi-hole, Home Assistant, and testing boards, I need a way to track their CPU usage, temperature, storage, and overall health—ideally from a single dashboard that also monitors other key devices.
Living in rural Lancashire with no close neighbours has its perks—peace, privacy, and the freedom to build a powerful self-hosted home network without worrying about ISP restrictions or poor infrastructure. My setup is built around Synology, Raspberry Pi, and Docker-powered services, giving me complete control over my network, automation, and devices. Here’s what I have running today and what I’m planning next.
For a private home network using a Synology NAS, Synology Router, and Raspberry Pis
*.home.example) to access internal services.For this setup, we assume the following hardware:
In the world of software development, interruptions—both planned (like meetings) and unplanned (like Slack messages, calls, or ad-hoc requests)—are productivity killers. Anyone who's spent time coding knows the frustration of losing their train of thought due to an ill-timed question or a looming meeting. But beyond the anecdotal frustrations, how much do interruptions actually cost in terms of productivity?
Bringing a new developer onto a project—especially something as complex as an embedded C application—is always a balance. You want to get them up to speed quickly and ensure they learn the right way to do things. But how long should it actually take before they can fix bugs, add features, and contribute effectively? And if it’s taking months, what does that say about the project?
This isn’t another "Git basics" article listing commands you already use daily. Instead, this post covers lesser-known Git commands and configurations that can dramatically improve your workflow. These are the hidden gems I wish I knew when I first started using Git. Every time I show someone one of these tricks, I get a "🤯 why did no one tell me this sooner?" reaction.
There’s a persistent belief in many organisations that standardising tools and processes across all software teams is a good idea. The logic goes something like this: if everyone is using the same set of tools, collaboration becomes easier, onboarding new engineers is smoother, and there’s less administrative overhead.
Markdown is a lightweight markup language that makes formatting text simple, readable, and easy to write. It was created by John Gruber in 2004 as a cleaner alternative to HTML.
In the fast-paced world of software development, silos between disciplines—architecture, product management, development, and project management—often lead to misalignment, inefficiencies, and slower delivery. A Software Guild offers a lightweight, collaborative way to bridge these gaps. It helps teams work together effectively while sharing best practices, making informed decisions, and driving technical and product excellence.