<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Career on ferkakta.dev</title><link>https://ferkakta.dev/tags/career/</link><description>Recent content in Career on ferkakta.dev</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright fizz.</copyright><lastBuildDate>Thu, 26 Mar 2026 18:00:00 -0500</lastBuildDate><atom:link href="https://ferkakta.dev/tags/career/index.xml" rel="self" type="application/rss+xml"/><item><title>Every tool I've ever used is a CloudFormation frontend</title><link>https://ferkakta.dev/cloudformation-frontends/</link><pubDate>Thu, 26 Mar 2026 18:00:00 -0500</pubDate><guid>https://ferkakta.dev/cloudformation-frontends/</guid><description>&lt;p&gt;I was reading a job description that wanted CloudFormation experience, and I had the thought that derails the actual task: I&amp;rsquo;ve spent my entire career using tools that compile down to CloudFormation and don&amp;rsquo;t mention it until something breaks. I&amp;rsquo;ve just never framed it that way.&lt;/p&gt;
&lt;p&gt;My career is a parade of progressively nicer frontends for the same underlying control plane — but one at a time.&lt;/p&gt;
&lt;p&gt;The first one was the AWS console. Click, wait, refresh, click. Then CloudFormation itself, which was an improvement in the way that a paper map is an improvement over asking for directions — technically correct, nearly unusable in practice. Then Serverless Framework, which promised to abstract the whole stack into a YAML file and a deploy command. Then Terraform, which promised cloud-agnostic infrastructure as code with a state model that actually worked.&lt;/p&gt;</description></item></channel></rss>