Skip to main content

Posts

Using Bicep Modules to Build Enterprise-Grade Azure Infrastructure 

Infrastructure as code (IaC) is no longer optional in modern Azure environments. Teams need repeatable deployments, secure defaults, predictable architecture and strong governance. Azure Bicep has become the preferred IaC language for Azure because it’s declarative, simple, modular and deeply integrated with the Azure platform.   This article breaks down  how to design Bicep modules the right way  for enterprise deployments. These patterns come from real-world use cases such as banking, fintech, multitenant SaaS and regulated workloads.   Why Bicep is the Standard for Azure IaC   Teams that move from ARM and Terraform to Bicep typically do so because Bicep offers:   Cleaner Syntax: No more massive JSON ARM templates.   Native Azure Integration   IntelliSense   Type-checking   Automatic API version updates   First-Class Modularity: Modules can describe reusable components like:   App Services   AKS clusters   Front Door Premium   Key Vault   VNet + su...
Recent posts

Shift Left to the Developer’s Machine: Building Local Git Security Gates 

A developer pushes one file. It contains an AWS access key left in a configuration block. Five minutes later, CI catches it. By then, the secret is in the remote repository, cached by mirrors and potentially forked. The developer rotates the key, scrubs the commit history and spends the rest of the afternoon on incident response. The real question isn’t how to clean up faster — it’s why the secret left the developer’s machine in the first place.   The Five-Minute Gap   Most engineering teams have invested in CI-based secret scanning . Tools such as GitHub Advanced Security, GitGuardian and TruffleHog’s CI integration catch leaked credentials in pull requests and pushed branches. This is good, but it’s also too late.   The GitGuardian 2026 State of Secrets Sprawl report found that 29 million secrets were detected on GitHub in 2025 alone — a 34% year-over-year increase and the largest single-year jump ever recorded. Worse, 64% of secrets leaked back in 202...

Anthropic Reverses Course on Hidden AI Restrictions Following Developer Backlash

Anthropic has abruptly walked back a controversial, unannounced policy that degraded the performance of its latest model, Claude Fable 5. The reversal follows intense backlash from the machine learning community, which criticized the company for a lack of transparency and anti-competitive behavior, according to a Wired report. The controversy began earlier this week with the release of Claude Fable 5, a version of Anthropic’s highly sophisticated Mythos system equipped with specialized national security guardrails. While the company openly said it would reroute hazardous prompts regarding cybersecurity, biology, and chemistry to less advanced models, it did not disclose a separate restriction: silently throttling requests tied to frontier LLM development. AI researchers quickly noticed that when Fable 5 was tasked with training competing LLMs, debugging AI code, or optimizing neural architecture, the model would covertly fail or degrade its output without notifying the user. This hi...

npm v12 Is Coming in July — Here’s What Developers Need to Do Now

For years, running npm install meant trusting that whatever code got pulled in would behave itself. That trust was often misplaced. Starting in July 2026, npm v12 changes the rules. Install scripts won’t run automatically anymore. Neither will dependencies be pulled from Git repos or remote URLs. All of it becomes opt-in. This is a direct response to a wave of supply chain attacks that have hammered the JavaScript ecosystem over the past year. In September 2025, attackers hijacked 18 popular npm packages — including debug and chalk — libraries found in virtually every Node.js project. With combined downloads exceeding 2.6 billion per week, it was one of the largest npm attacks in history. In 2025 alone, attackers published nearly 455,000 malicious npm packages. The attacks haven’t slowed down — the March 2026 Axios compromise weaponized one of npm’s most-downloaded packages through credential theft. The ecosystem needed a structural fix, not just better scanning t...

CDEvents Simplifies AI-Ready Developer Platforms

Internal developer platforms have become a tangled web of orchestration tools, CI runners and deployment systems that rarely speak the same language. Every new integration adds another translation layer, and as AI-driven automation starts to plug into those pipelines, the lack of a shared vocabulary for what is actually happening across the software delivery lifecycle becomes a real bottleneck. Without a consistent way to describe build, test and deploy events, both humans and agents are left stitching together logs and webhooks from systems that were never designed to interoperate. Dadisi Sanyika of the Continuous Delivery Foundation sat down with Mike Vizard to walk through how CDEvents is tackling that fragmentation. CDEvents defines a common event specification — essentially a standardized set of receipts that tools like Jenkins, Tekton and other delivery systems can emit as work moves through the pipeline. That shared semantic layer gives platform teams a reliable way to wire h...

Still Using API Keys for Your AI Agent? Here’s When it’s Time to Upgrade 

Imagine handing the same master key to every contractor who works on your building. No names, no records, no way to know who came and went. If the key gets copied, passed around or lost, you’d have no idea. You’d only find out something went wrong after the damage had been done.   That’s essentially what API keys do for your AI agents , and for prototypes, that’s fine.    However, the moment your agent moves into production, accessing real data, taking real actions and operating inside real systems, that master key becomes a liability you can’t afford.   The Risks and Benefits of API Keys   Developers are under a huge amount of pressure to build faster. Every organization wants to benefit from agentic AI, and devs play an integral role in making that happen.   Given this, it’s easy to see the appeal of API keys: They’re simple to use and can get you to a proof of concept almost instantly. The problem is that they’re severely lacking from a security standpoint.   API keys work by ...