We Ditched Terraform 1.10 for CloudFormation: Reducing IaC Complexity for Our Small AWS Team We’re a 4-person engineering team managing 32 AWS resources across dev, staging, and production environments for a B2B SaaS product. For 18 months, we relied on Terraform 1.10 to manage our infrastructure as code (IaC). But by Q3 2024, the overhead of maintaining Terraform outweighed its benefits for our
Tbh I had no idea this was even a thing until recently. I've been working with Rails for a while now and somehow never came across it. So let me explain it the way I understood it. You know how we normally do associations in Rails, User has many Posts, Post belongs to User. Two different models, two different tables. Simple. But what if a model needs to reference itself? Like same table, same mode
Most cloud sustainability tools are built for sustainability officers. They pull three-month-old billing data, run it through a proprietary model, and produce a PDF that engineers never see. By the time you know your us-east-1 cluster emits twice as much as us-west-2 would have, it's been running for a quarter. The architecture is locked in. The carbon is already burnt. The only moment you can act
El problema real Cuando trabajas en DevOps, inevitablemente enfrentas el caos de gestionar infraestructura manualmente. Cambios undocumentados, configuraciones inconsistentes entre ambientes y actualizaciones que rompen lo que funcionaba. Terraform resuelve esto con un workflow estructurado que convierte tu infraestructura en código versionable y reproducible. El workflow de Terraform es el cicl
El Problema Real Cuando comenzamos a usar Terraform, muchos nos hacemos la misma pregunta: ¿cómo sabe Terraform qué recursos ya existen en la nube? La respuesta está en el state file, un archivo que frecuentemente causa dolores de cabeza innecesarios cuando no se entiende bien. El state file es un archivo JSON que Terraform mantiene como fuente única de verdad sobre tu infraestructura. Contiene
Purpose of Variables in Terraform Variables prevent repetitive hardcoding of values in Terraform configuration files. They reduce errors due to inconsistent value entries across multiple resources. Simplify updating environment-specific configurations (e.g., changing from dev to stage). Types of Variables Based on Purpose Input Variables: Accept values from users or other sources. Output Variables
Comments
Why I built another Ruby test runner inspired by Playwright Test Ruby already has great testing tools. If you are building Rails applications today, you probably use one of these combinations: RSpec + Capybara Minitest + Capybara Rails system tests Maybe Selenium, Cuprite, Ferrum, or Playwright through Ruby bindings These tools are mature, battle-tested, and widely used. So the natural question