ggordan

I've been working on a platform to help teams deal with their deadletter queues. It's very much a scratch my own itch project as it's solving a problem that I've faced while at my day job.

This is the one I wanted to suggest too. It's a great book, don't be put off by the "enterprise" in the name.

I've been working on an event orchestration platform[1] with the initial use case being "surface your deadletter queue, and resolve problems" mostly to scratch an itch. In other words, what happens when you can't process an event and you want a human to investigate the why and perform some kind of action to resolve the issue.

[1] anketta.com

I think "based on" is more like implemented on top of, similar to timescaledb

it looks like the generated code of a protobuf enum

Great to see. I've definitely missed it coming from circleci where you have contexts where you can define secrets that you can share across multiple repos

Environment variables being exposed to the client is great assuming this means they can be configured at runtime and available on the client

I tried out Apple Music and really wanted to like it, but I came back to Spotify mostly because the apps (desktop and mobile) that apple were offering were just completely unusable.

If you are both using tabs, for him everything is going to be indented with "2 space tabs" including your edits, and for you it is going to be indented with "eight space tabs", including his edits.

Just wondering how you deal with all the extra noise in the diff. What happens when multiple people are working on the project, are you not constantly having to deal with merge conflicts? I feel like checking in the build directory makes the diffs pretty much useless.

This is great, I've been considering writing something similar for London taking account cycling distance/time.