AWS Fargate is a tool that is very useful in certain situations while at the same time feeling profoundly weird to use. We’ve had an article about deploying Rails to it just last week – this week we’ll take a look at what it actually is. And much more.
To have a future, Ember must kill its past
By Andrew Callahan
Remember Ember? It’s that other front-end framework. It was created at a time when multiple frameworks were vying for the limelight, and ultimately lost. Can it be salvaged?
By Axel Svensson
If you’re anything like me, you’ve at some point in the past made a bash script work by progressively adding more \\\ before that “ until it finally worked. Escaping is hard – here’s a dive into the concept.
Minify your SVGs
By Victor Zhou
We know we’re supposed to minify our CSS, our JS, heck, even our HTML sometimes. But did you ever think about minifying SVGs? It’s not obvious by any stretch. Here’s a great writeup on the topic.
How to correct 32,000 incorrect CSV files in fewer than 32,000 steps
By Jeff Keen
CSVs are great at being inconsistent and unparseable at the best of times, and utterly baffling at others. Here’s a tale by Jeff, who had a large problem, found a clever Ruby solution, then rolled it into a gem.
How far out is AWS Fargate?
By Michael Lavers
We’ve successfully deployed a bunch of production workloads to Fargate at Codest, but it wasn’t the most straightforward tool to wrap our heads around. At first we didn’t even know what Fargate is actually supposed to be used for. I wish we had this writeup to help us along back when we started.
Bonus! We like our stuff neat over here. Here’s a little thing about formatting ESLint output. Neatly.