I mostly use DigitalOcean and their managed kubernetes service. My projects tend to be self-contained in a monorepo (where my k8s manifest also live) and I use Flux* to keep my cluster in sync. I'm quite happy with, took a bit of time to get it set up exactly how I wanted, but now it's no-effort to do releases.
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.
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.
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
I was in the same boat until I tried VScode. It's a really great editor, configurable, and performant enough that I don't miss Sublime. Also the Go support is pretty great.
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.
I often find that just getting out of the house (going through that process of showering, getting dress etc..) helps a lot. If 'walk around' implies just walking around your house, I'd suggest trying that.
I certainly did notice that my back hurt a lot less once I started weight training. And as an added benefit, people have commented that my posture has improved. So win-win!
We tried to approach collaboration in a very simple way that doesn't require accounts and heavy realtime Google Docs-style co-editing. Our collaboration relies on versions and links. Every refresh creates a new version, so as soon as you pass a link to someone, they create a new version automatically. This way you're never editing the same version, even though you're editing the same "document". So it definitely is based on passing links around but making sure there are no conflicts. We're definitely looking into simple ways to notify you that there's a new version created by someone else so it runs even smoother.
You can think of it a bit like a tree system, where you start on the stem and as you share it with others you build independent branches. Hope it makes sense, we're definitely going to work more on that part in the future.
Thanks for the feedback! We started with Dropbox because that is what we all use, but we do want to add support for other services. Your idea for GitHub integration is very interesting, and it's not something that previously occurred to us. It's something we'll definitely look into!