TypeScript is one of my favorite programming languages. It gave JavaScript developers a way to write statically typed code with compile time type checking which is both its best and, sometimes, not so great feature. But wouldn’t it be awesome if we could have types that are not only checked at compile time but also at runtime? Enter Zod. I also recommend this awesome extension for VSCode for TypeScript pretty-ts-errors

In this article, I’ll walk you through some of the coolest TypeScript features like conditional types, generic functions, and how to extract keys from arrays and enums. These techniques can really level up your code by making it more flexible and safer to use. You’ll see how TypeScript has your back with catching errors and adapting function inputs based on what you pass in. We’ll break it down with simple, practical examples, showing you how to avoid those pesky mistakes and write cleaner, more reliable code!

Building an EKS cluster and its components can be overwhelming, especially when dealing with various elements like VPCs, ALB Controllers, Karpenter Autoscalers, ArgoCD, and other commonly used add-ons. Wouldn’t it be nice to have a package that simplifies this process, helping you create a well-architected, guided, and consistent setup across AWS accounts? Enter, EKS Blueprint using CDK and EKS Blueprint using Terraform. I haven’t worked with the Terraform version, so we’ll be focusing solely on the CDK Blueprint.

AWS has pretty solid support for CDK with its resources, but there are still a few cases where CDK doesn’t provide constructs. Since I’ve been working with CDK for over a couple of years now, I wanted to share some use cases where we had to roll up our sleeves and write an AwsCustomResource.

Notifications are an integral part of numerous applications, serving a variety of purposes. Now, let’s delve into the diverse system designs available for implementing a robust notification system.