Introduction Preparing for Google Cloud certifications can feel overwhelming. Most resources focus heavily on theory, but when it comes to the actual exam, what really matters is how well you can apply concepts in real scenarios. While preparing myself, I realized there was a lack of free practice exams with clear explanations, so I built something to solve that. I created free GCP practice exam
I finished an English series on the way I think ordinary people can start using AI for real work. The point is not to become an AI expert first. The point is to have one place where you can say what you want, give the tool access to the right folder, and check the result. Anything important still needs a human pause: publishing, deleting, paying, or authorizing. My preferred starting point is simp
Imagine you have a Nodejs server with endpoint that performs heavy CPU operations. By default your server runs on a single thread. This means it will freeze depending on the CPU load. If your server has other asynchronous endpoints, for example, to execute database operations, those endpoints would become unresponsive while the heavy load endpoint is processing. Our first idea is to create more th
Every dev team has lost hours to .env problems. A missing variable breaks a deploy. I built Razify to make all of that stop happening. Razify is a single binary CLI tool for .env file management. No cloud account No tracking No Go installation required Works with Node.js, Python, Ruby, Laravel, Rails — anything that uses .env files. razify scan .env Detects leaked secrets using 80+ regex patte
In the previous post, I walked through the compensation logic in each service. The code looks clean on paper. But sagas have a lot of moving parts, and bugs tend to hide in the transitions between services, not inside a single service. This post covers how I test the saga system: unit tests for each service, orchestrator routing tests, and the edge cases that caught me off guard. The orchestrator'
I've been a frontend dev for a few years now, and there's a pattern I kept seeing across almost every small team I worked with. New feature ships. Everyone's happy. Then three days later something completely unrelated breaks and nobody caught it. The problem was always the same: automating that required Playwright or Selenium, and that was "a dev thing". And the devs were busy shipping the next fe
The Model Context Protocol (MCP) has become the default standard for connecting AI agents to external tools and APIs. Governed by the Linux Foundation since early 2025 and adopted by OpenAI, Anthropic, Microsoft, and Vercel, MCP is the USB-C port of the AI ecosystem — one protocol that lets any LLM application talk to any tool server. But there's a gap between reading the spec and building somethi
If you have spent any real time with Claude Code, you have probably noticed the same problem I did. You write the same instructions in the prompt every other day. "Use four-space indentation here." "Always run the linter after edits." "Format commit messages this way." After the third or fourth repeat, it stops feeling like a prompt and starts feeling like missing config. Skills are how Claude Cod