In my previous article about treating architecture documentation as a first-class asset, I had a great discussion in the comments about enforcing architectural rules. I promised to share materials from my recent Google Developer Groups workshop. The workshop is now finished! Here is the story of how I built an AI Quality Gate, how it helped me solve the internal "CEO, CTO, CFO, CISO" conflict, and
I've been shipping software internationally for 5 years, and I've seen localization bugs tank launches in ways that make deployment failures look quaint. Currency displays in the wrong locale. Dates that make Japanese users think the app was built in 1970. Phone numbers that break form validation in Brazil. Last week, I decided to actually test TestSprite on a real project instead of adding it to
description: "Critical issues blocking TestSprite adoption in Indonesia, Malaysia, Philippines. Production fixes included." tags: testsprite, testing, devops, indonesia, localization cover_image: "https://dev-to-uploads.s3.amazonaws.com/uploads/articles/testsprite_mcp_review.png" canonical_url: "" published: false Code Review: Why TestSprite's MCP Failed in Southeast Asia (And How to Fix It) TL;DR
TestSprite adalah platform testing yang fokus pada quality assurance untuk aplikasi modern. Setelah menggunakan TestSprite dalam satu proyek production-grade di berbagai device dan region, saya ingin share pengalaman mendalam tentang bagaimana tool ini menangani localization dan timezone handling — aspek yang sering diabaikan tapi krusial untuk aplikasi global. TestSprite memungkinkan developer un
description: "Real-world TestSprite evaluation testing Indonesian e-commerce with IDR currency, timezone handling, and 3 locales. Grade A review with technical findings." https://images.unsplash.com/photo-1516321318423-f06f70a504f0?w=1200&h=600&fit=crop" TL;DR: TestSprite is 80% faster than manual visual regression testing. Grade A for multi-locale apps. Grade B+ for logic testing. Real findings:
In my previous article, I documented how I installed Terraform on macOS using Homebrew and fixed a Zsh autocomplete issue. In this article, I am going to be using terraform to provision, update, and destroy a simple set of infrastructure using the sample configuration provided by hashicorp The goal is to understand the basic Terraform workflow: Write configuration Authenticate to Google Cloud Ini
On April 30th I got an email from Google about something called GEAR, their new program for building AI agents using ADK, the Agent Development Kit. I signed up, watched the intro video, and had a strange feeling of recognition. The pattern was familiar. Define tools. Write descriptions. Connect an AI model to those tools. Let the model decide which tool to call based on what the user asks. I buil
VotePath -- an AI-powered multilingual voting guide for first-time voters. The Problem: Why Don't People Vote? What is VotePath? 🤖 Gemini-Powered AI Assistant: A conversational AI built with the Google Gemini API that answers specific election queries in real-time. 🛠️ The Tech Stack Building the UI components and wiring up the Gemini SDK went smoothly using an intent-driven development approach.