Techielass - A blog by Sarah Lean

July 14, 2026 has come and gone.

If you're an infrastructure engineer, you've probably lived this scenario more than once: you clone a repo, try to run it, and immediately hit a wall.

"We want our Development, Test, QA, Pre-Production, and Production environments to be identical."

If, like me, you've been using Terraform for a while, you've probably deployed resources into a single Azure subscription.

If you’re new to Terraform you’ll quickly come across these two commands: terraform plan terraform apply At first glance, they can feel confusing.

There is a wealth of AI tools available to use nowadays.

Have you ever needed to send an email to a large group of customers, whether they’re long-standing clients or new contacts you’re hoping to engage, only to find your message held up by email filters because it contains attachments?

As another year comes to a close, I’ve found myself pausing to reflect on what 2025 has meant for me, creatively, professionally, and within the communities I’m part of.

If you’ve been exploring the world of AI tools, you may have already discovered how powerful language models can be when woven into your everyday workflows.

When you’re a pre-sales technical engineer who joins meetings with customers, you're often there to demo a product, answer technical questions, or validate that a proposed solution is the right fit.

In any type of code, there are moments when comments are useful for adding context or clarification.

A question I am often asked is: “If our Microsoft Entra tenant was ever deleted — could we recover it?”

When you are using Terraform, one of the key principles is that you can write reusable and scalable code that can be used in multiple environments without you having to rewrite or duplicate it.

High availability is a consideration that every Architect needs to think about when building cloud infrastructure.

Technology has come a long way, but no system is ever completely safe from failure.