This is the third post in my Google Cloud Next '26 (Las Vegas) recap series. You can find the previous posts here 👇 Part 1: [Google Cloud Next '26 Recap #1] Hands-On with the Agentic Hack Zone Part 2: [Google Cloud Next '26 Recap #2] Three Unique Booths I Tried at the EXPO In Parts 1 and 2, I covered my experiences on the EXPO floor. This time, I'd like to switch gears and share one of the se
Most agency onboarding fails before the kickoff call happens. Not because the team isn't good. Not because the client is difficult. Because nobody collected the right context upfront, and the kickoff call becomes the place where everyone discovers what they don't know yet. The intake form is the fix. Not a 3-question "tell us about your project" form. A real one. Here's the framework we use — 27 q
An opinionated list of Python frameworks, libraries, tools, and resources
This article was originally published on https://forg.to/articles/how-to-stop-hitting-claude-usage-limits *You're Paying for Claude. You're Also Wasting Most of It. I used to hit my usage limit by 2pm every day. Not because I was doing too much work. Because I had no idea how Claude actually charges you. Once I understood the real mechanic, everything changed. I now hit my limit maybe once a mont
What is Azure Storage? Azure storage is Microsoft's cloud storage solution. It allows storage of unstructured data, pdfs, file shares etc. The following steps in this article outlines how I was able to create storage for the department's testing and training. In the Azure portal, search for and select Resource groups Select + Create Give your resource group a name. For example, storagerg
The Idea After deciding to build an iOS app using AI, the first thing I set out to create was a metronome app designed for dark stage environments. Back in college, I played drums — and while that was a while ago, there weren’t many metronome apps that felt both clean and professional. (Turns out, that’s still true today.) That’s what led me to the idea: a simple, black-and-white metronome where
If you've worked with Drupal long enough, you've faced this decision: Do I build a custom module for this or can ECA handle it? Use ECA When The logic is workflow-based Non-developers need to maintain it ECA workflows live in the admin UI. Your client or site admin can read, modify, and debug them without touching code. A custom module cannot offer that. Speed matters A workflow that would tak
TL;DR — Superpowers and Compound Engineering aren't competitors. They're optimised for different worlds. Superpowers is gold for mature codebases with established methodology (TDD shops, large legacy systems, teams enforcing standards). Compound Engineering is gold for early-stage products where one person owns a feature end-to-end. Pick by what your codebase looks like, not by which README sounds