whiskey-one

This is really cool! Once you’ve gone to the trouble to be in k8s universe, might as well get some higher-layer primitives for the business logic as well.

The only weird part is the need to stand up a cluster to test individual trigger/flows function.

Any tips / online resources how to best utilize for defensive reviews?

Indeed, the user is the hardest part of the program to secure.

Very cool

In theory, yes you could iterate on architecture and potentially even come up with better one with agile approach.

In practice, so many aspects follow from it that it’s not practical to iterate with today’s tools.

Subsequently in PoI we see two imperfect super-intelligent AIs let loose in the real world fight each other for domination and their objectives.

For me, it’s a question of when, not if this happens in real life.

It is indeed painful to figure out all the Stripe events one needs to handle. However, for me it’s worth it to do it once, and then be able to handle the interactions between my app and Stripe directly, instead of adding more layers.

A reminder associated with the birthday can and should be changed if I change time zones. But the birthday date didn’t change so it shouldn’t move to a different day.

The concept is interesting but without charging it’s a non-starter for me. Also it’s a bit awkward and I’d prefer to use my phone or watch instead of adding a ring.

Is there a write up on the security of actions or equivalent that explains how they are secure both with direct and transitive dependencies? If this applies to Depot.

I left a large software corp last year to co-found a startup, launching myself in the world of OSS. I couldn't be more grateful to the HN community for introducing me to great concepts and tools!

Having to figure out which of the 100s of Stripe event types we need to handle and which ones overlap was the most stressful part of adopting their system. Simplification here is welcomed.

Can you elaborate on the fault tolerance advantage of micro services?

For context, my current project is a monolith web app with services being part of the monolith and called with try/catch. I can understand perhaps faster, independent, less risky recovery in the micro services case but don’t quite understand the fault tolerance gain.