A bot recently approved one of my Pull Requests (PRs) with the cleanest possible verdict: “No Issues Found — Recommendation: Merge.” The story did not end there. Weeks later, a maintainer finally reviewed the contribution. By then, the parts of the repository targeted by the localization work had been removed as the project evolved. The PR was closed, not because the translation was incorrect, but because the review arrived after the underlying code structure had changed. That outcome highlights a broader challenge in open source internationalization (i18n). The problem is often not translation quality. It is the absence of processes that allows language contributions to be evaluated, routed, and integrated before project evolution overtakes them. Translation is Not the Hard Part When people hear “i18n,” many maintainers think it means “drop a JSON file in.” That is not what it involves. Internationalisation is a system: stable keys, defined fallback behaviour, plural rules...
AI-generated infrastructure code is arriving faster than most organizations can absorb it. The organizations that invested in platform quality first are the ones pulling ahead. Every few years, someone declares that Infrastructure as Code is dead. The arguments tend to “sidecar” the hype cycle. First, complexity, then containers, then Kubernetes, then serverless. Now it’s AI’s turn; supposedly, generative AI tools will make declarative configuration files obsolete, and natural-language prompts will replace Terraform modules and policy-as-code guardrails. This latest narrative probably drives clicks and hallway conversations. But it’s wrong. What’s actually happening is more interesting and more consequential for infrastructure leaders: IaC is becoming the system of record inside a larger platform architecture, one that AI both depends on and generates code for. Enterprise infrastructure remains stubbornly hybrid, spanning on-prem and cloud, with GPU clusters emer...