Frankly speaking ...

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 (...

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...