Automatically migrate your on-call setup to Signals
A couple of my teammates wrote a really great migration tool that’ll take your on-call setup in PagerDuty/OpsGenie/etc. and use it to generate Terraform configuration for the closest equivalent in our own alerting/on-call product, Signals. And it’s open source! 🤩
Automatically migrate your on-call setup to Signals
We are making it easier than ever to move off PagerDuty, Opsgenie, or VictorOps and get started on Signals. And it’s open source.
Matthew Lyon (@[email protected])
100% agree with this (although i do get around that last bit by just writing perfect code with zero bugs 😌)
Matthew Lyon (@[email protected])
I probably don’t want to know about what’s new with your app I definitely don’t want you to pop up a modal dialog I can’t dismiss with multiple animated steps describing what’s new honestly I’d prefer it if you didn’t add anything new – I want you to fix bugs
Hubble Network makes Bluetooth connection with a satellite for the first time | TechCrunch
the bluetooth device is connected uh successfully

Hubble Network makes Bluetooth connection with a satellite for the first time | TechCrunch
Hubble Network has become the first company in history to establish a Bluetooth connection directly to a satellite — a critical technology validation for
How an empty S3 bucket can make your AWS bill explode
Lesson 1: Anyone who knows the name of any of your S3 buckets can ramp up your AWS bill as they like.
Other than deleting the bucket, there’s nothing you can do to prevent it. Standard S3 PUT requests are priced at just $0.005 per 1,000 requests, but a single machine can easily execute thousands of such requests per second.
I’m absolutely flabbergasted that this is okay. How is this okay???

How an empty S3 bucket can make your AWS bill explode
Imagine you create an empty, private AWS S3 bucket in a region of your preference. What will your AWS bill be the next morning?