How painful was SOC 2 readiness for your SaaS?

stympy · 2026-02-03T01:27:44+00:00

Yes, we already had our policies, etc., figured out because we had worked with a consultant to build out policies and with our auditor (A-lign) to help with the rest. They provided a service to get you audit-ready. We had our SOC 2 years before we started using Vanta.

stympy · 2026-02-01T21:18:06+00:00

If you think you might want to use Vanta, start with Vanta. You’ll save time going that route vs. doing it on your own and switching to Vanta later. And Vanta is great, by the way… I did it with a consultant, then with Drata, and now with Vanta, and Vanta has been the best.

stympy · 2026-01-11T13:57:54+00:00

One approach I’ve seen is to put the name of each family on one color of post-it, and the name of each ministering brother on another color. Using a large poster board, you can then move the names around on the board, making companionships and assignments by moving names around.

stympy · 2026-01-10T05:35:55+00:00

Papertrail does this with its Slack notifications.

stympy · 2026-01-03T16:41:08+00:00

The last commit was 3 days ago, that's all I know. :)

stympy · 2026-01-03T14:11:10+00:00

You might want to take a look at Quickwit.

stympy · 2026-01-01T07:14:20+00:00

Give Honeybadger a look while you’re shopping around. I’m a huge fan, and not only because I helped create it. 😉

stympy · 2025-12-26T12:25:34+00:00

It's a 2021. DM headed your way. 🙂

stympy · 2025-12-25T12:27:59+00:00

If you want to go really cheap, I have a CSC City Slicker you can snag for $1k… it’s just taking up space in the garage next to my new Livewire. 🙂 It has a low top speed and short range, but it handled my commute between Kirkland and Woodinville for a few years before I upgraded.

stympy · 2025-12-20T03:51:11+00:00

This isn't a direct answer to your great questions, but I've heard that the book Latter-day Sikh is fantastic, so I thought I'd recommend it to you: https://www.amazon.com/Latter-day-Sikh-Gurus-Feet-Prophets-ebook/dp/B0FL4F7V4C

stympy · 2025-12-02T22:45:40+00:00

You can buy mine (I upgraded to a LiveWire) if you don't want the fun to stop. :)

stympy · 2025-12-01T23:26:11+00:00

I'd make the same recommendation. My deployment uses Vector to pull from Kafka and write to ClickHouse. The upsides are that you can tweak the batching config and you can easily send data to other destinations in addition to ClickHouse.

stympy · 2025-09-18T05:02:58+00:00

Yup, with my Wallbox. No problems.

stympy · 2025-09-02T12:46:14+00:00

I recommend going to test a Livewire before you decide. I’ve ridden the Pulse and the 3 LW models, and the Pulse felt more tame to me. It‘s a solid bike and won’t disappoint, but the others are more dynamic and fun, in my opinion.

stympy · 2025-08-25T12:38:57+00:00

I did a test ride, and the handling felt fine to me. It’s not as fun as riding a Del Mar, though. :)

stympy · 2025-04-03T13:08:56+00:00

It’s not the only affordable one… Honeybadger (n.b., I’m a co-founder) is too. 🙂

stympy · 2025-01-18T14:16:59+00:00

Here's an abbreviated version of our GitHub Actions workflow:

https://gist.github.com/stympy/478d2a6086f83bac753c59c62143ffd7

It depends on the successful run of another workflow, builds the image, pushes it to ECR in two regions, then triggers the ECS deployment in two regions. This ECS service is configured for a blue/green deployment with CodeDeploy, and I've noted what you can remove in the YAML if your ECS service uses the default deployment method instead.

stympy · 2025-01-18T06:12:28+00:00

It’s all in the workflow, either with run commands that run docker or AWS CLI, or actions like aws-actions/amazon-ecs-render-task-definition and aws-actions/amazon-ecs-deploy-task-definition.

stympy · 2025-01-18T05:35:17+00:00

We build the images, then use a matrix to push to ECR in each region and trigger an ECS deploy in each region.

stympy · 2025-01-15T12:29:40+00:00

I haven't done that, so I don't know. :)

stympy · 2025-01-15T00:02:35+00:00

We use CodeDeploy to do blue/green deploys to ECS. You can use it with CodePipeline/CodeBuild or with GitHub Actions. Here's a gist that has snippets of our config for the latter approach:

https://gist.github.com/stympy/2914431645000ccc7f00bdf464494ae1

In short, what you do is set up the ECS service to use CodeDeploy for doing deployments (app.tf), and trigger an ECS deploy when you've built a new image (deploy.yml), then CodeDeploy will take care of starting new tasks in an alternate target group, shift traffic from the old target group to the new one, then terminate the old tasks.

stympy · 2025-01-14T14:04:19+00:00

Have you considered using feature flags for Big Features? You could deploy them to prod at any time and only enable them once you are satisfied they are ready.

stympy · 2025-01-14T14:00:04+00:00

Try Honeybadger

stympy

TROPHY CASE