Frankly speaking ...

For a consultant, the most valuable asset isn’t the hardware or certifications —it’s the knowledge. Too often, that knowledge is left behind when you move between clients. You hand back the hardware, lose access to the Jira tickets, and the internal documentation you wrote becomes a ghost in someone else's machine. Years ago I adopted a private DokuWiki that travelled with me through firewalls, tech changes, and career moves. Here is why, even in the age of LLMs, it remains an important tool. The Consultant’s Dilemma: Firewalls and "Fading" Skills Consulting is a nomadic life. You spend months deep in a client’s infrastructure, often behind restrictive firewalls where online resources are a luxury, not a guarantee. I realised early on that I couldn't rely on the client’s internal systems to store my personal breakthroughs. I needed a knowledge base that moved with me. Whether I was troubleshooting a niche Git conflict or configuring a Linux environment on a lock...

Building a specialised tool such as a word-puzzle solver needs more than automated builds. The real value is letting users run the solver from their browser—enter letters, press a button, and get results without a command line. For example, given letters like "mitncao", users should find every valid word without leaving the UI. That requires a simple run method: press a button, type the letters, and receive results quickly. By implementing this on both GitHub and GitLab I learned how each platform compares in setup effort, input sanitisation, and user experience. Takeaway 1: GitHub is Fast and Simple An Easy Start: GitHub's Straightforward Setup For those who want to move from an idea to a working tool in minutes, GitHub is a strong choice. Setting up a manual start button for the solver was straightforward, largely due to the integration between the platform and AI tools like GitHub Copilot. Instead of digging through manuals, I could describe the required inputs (...

COVID-19 Hospitalisations COVID-19 hospitalisation data are openly reported but the information provided is being misrepresented. Take, for example, the following Facebook post: Facebook 24 Jan 2022 While accurate with regard to the numbers, Peter is implying that vaccination does not work as more vaccinated people are in hospital than unvaccinated people. This is a misrepresentation because the emphasis Peter makes is on the absolute number rather than the rate of hospitalisations among vaccinated versus unvaccinated individuals. For example, let’s use data approximately based on the figures available from the same source as Peter’s, namely NSW Health data. # Population data (per 1,000 people for rate calculation) total_population <- 1000 vaccination_rate <- 0.929 # 92.9% vaccination rate in NSW, Jan 2022 vaccinated_population <- vaccination_rate * total_population unvaccinated_population <- (1 - vaccination_rate) * total_population # Hospitalisation numbers fr...

This article is a companion piece to From Code to Content: Automating Your Blogger Workflow with GitHub which focused on the Blogger API and The Art of the Repeatable Post: Why Structure Matters , which focuses on the importance of structure for a consistent and high-quality blogging workflow. This article ties together the concepts of automation and structure, showing how to build a CI/CD pipeline for your technical blog using GitHub Actions and Docker. The Hook: Escaping the Manual Blogging Loop For the modern developer, the desire to share technical insights is often hindered by administrative overhead. We spend our professional lives in code editors and terminal sessions, yet sharing those insights on platforms like Blogger often requires a return to manual labour. We find ourselves copy-pasting HTML, struggling with clunky web-based editors, and manually managing assets. This friction discourages regular contributions, often leading to stale repositories and abandoned drafts....

In my previous article , I explored the technical "plumbing" required to connect GitHub to Blogger.  It is  a powerful setup - especially once the heavy lifting is automated. But  automation can’t fix disorder.  If every blog post starts as a chaotic scramble of files and mismatched formats, you are still working harder than you should. The real magic happens when you move beyond just "automation" and start embracing a consistent project structure . Consistency is a Writer's Best Friend When you use a standardised repository structure—like the one found in the article-markdown repository—you are not just organising files; you are creating a mental shortcut. Because every post has the same folder layout, you never have to wonder where your images go or how to name your source files. Professional Rigour for Every Paragraph We often hear that we should treat "content as code". In practice, this means your blog benefits from the same discipline as a...

For the modern developer, the desire to share technical insights is often hindered by the "toil" of the publishing process. We live in our code editors and terminal sessions, yet sharing those insights on platforms like  Blogger  often means reverting to manual labour: copy-pasting HTML, wrestling with web-based WYSIWYG editors, and manually managing assets. This discourages regular contribution, often resulting in stale repositories and abandoned drafts. By adopting a "Blogging as Code" approach, you can replace manual copy-pasting with an automated CI/CD pipeline. By leveraging the  Blogger REST API v3  and  GitHub Actions , you can treat your blog with the same engineering rigour as your production software. 1. The API as Your Deployment Interface The core shift in this methodology is viewing Blogger not as a website, but as a deployment target. The Blogger REST API allows developers to bypass the browser entirely, enabling programmatic creation and updates o...