Bazel

This is part of the series Startup that Failed . Infrastructure as Code: Why It’s Non-Negotiable Start with this rule: If you’re touching AWS console to create resources, you’re doing it wrong. Every resource goes through Terraform. IAM roles, security groups, RDS instances, S3 buckets, EKS clusters - everything. No exceptions. This isn’t about following best practices. It’s about three concrete problems: 1. Reproducibility. You will need to rebuild your infrastructure. Whether it’s disaster recovery, creating new environments, or (in my case) rebranding, you’ll need to recreate everything. With Terraform, it’s terraform apply. Without it, you’re clicking through AWS console trying to remember what you configured six months ago. ...

Life Happens Almost two full years have passed since the point when I had “the energy” to write content. And, as most podcasts fail after just a few episodes, I’ve been unable to keep up with the writing. It was a genuine surprise to see how much effort goes into even the simplest of articles. This, in turn, generated a significant inspirational backlog for potential content shortly. Looking back on those two years, I’m happy with the outcome, and I don’t feel much regret for not writing. As the internet doesn’t forget, this might serve mostly as a reminder to myself when I look back on this point a few years down the road. Just writing my own timeline took some time, as each week was packed with more work than I wanted it to be! Work-life balance?! ...