Early versions of touch screen devices had questionable utility. The Apple Newton and its handwriting recognition feature is probably the easiest of these to dunk on, as the Simpsons did.
For $900 in 1993 or about $1960 in 2024, you could own a note pad that sort of worked with a stylus and touch screen interface.
Of course, I dreamed of having one anyway. As a Star Trek The Next Generation fan, I wanted to walk around and work with a TNG like dataPADD.
In GitHub Actions, GitHub-hosted runners are a convenient resource for creating CI/CD pipelines, especially when a project has just started. Public repositories can use standard runners for free and private repositories have a certain amount of free minutes.
But if your project requires more resources for builds and you’re already paying for compute, for example, with AWS, a self-hosted runner allows access to larger compute resources and keeps the billing for compute in one place.
🚥 What is AWS App Runner? I discovered the relatively new App Runner service while testing deployments with AWS CDK. If App Runner is new to you, it’s possible to think of it as an AWS service abstraction level above ECS Fargate. It’s what AWS calls a fully managed service and will deploy your application as a container as well as handle auto scaling, SSL/TLS certificate management, CI/CD, and load balancing.
Let’s deploy (and destroy) When I decided to try out AWS CDK, I began with a goal to reproducibly deploy and destroy from a single repository using AWS CDK and GitHub Actions. Every environment may not have this workflow, but I made it a requirement for testing.
Easily spinning up and down infrastructure is useful for rapid development and testing. Prod-like but ephemeral environments provide a convenient way to expose and troubleshoot bugs that may not appear in local development environments.
