Icathian

We use it a ton at my shop for internal things like release rollouts. Fairly big tech company, and same experience. It's an excellent product.

Do you also get mad at companies that make locks when people install them on their front doors?

I only looked at the linked file, so I'm not going to speak to the rest of the code and don't really have a good grasp of the architecture here.

This seems mostly ok. The only thing that (imo) wouldn't pass code review is that big honking loop at https://github.com/achristmascarl/rainfrog/blob/main/src/app.... That thing needs to be refactored down to be readable, with individual logic chunks being put into their own functions and tidied up a bit.

That's not really Rust-specific, obviously, but all the `match` and `if let` and whatever other Rust stuff looks fine, so it's what I've got.

I agree with absolutely everything you wrote. And so I don't complain about hiring loops, and instead just prep for interviews. It's absolutely worth the tradeoff.

You can't really be making this comparison, though? Getting an MD and residency and rotations means you're in your thirties before you get your first real job. At least in the US. It's wildly more difficult.

So the obvious question is, which big shops were using the Core version that ended up prompting this change? I know of one or two but I'm curious if there are some obvious big fish.

I worked in this space as a statistician. You are completely correct. The environment is so incredibly target rich and resources are so limited that only the biggest and most obviously winnable cases are pursued.

I've always enjoyed their content, and appreciated the excellent mix of technical depth and clarity.

I don't follow the Nix community closely enough to have any idea what happened here, but running off one of their most publicly recognizable members is probably not a _good_ sign.

This is a really nice part 1. I think a series building from this up to what would be considered "secure" in modern day, with the other topics already mentioned in comments here and on the article, would be awesome. I could easily see it becoming a very popular resource among students or new devs who are solving these problems for the first time themselves. The writing is very clear and concise.

Frankly, it sounds like you know what is needed but don't like it. If you could blast through coding and system design rounds, would you have already found a next role? It seems clear that you think so, and I personally agree.

You can think whatever you want of leetcode, and algorithm interviews, but that's the front door into tech jobs. If you don't have a back door available to you I think you probably have to bite the bullet and deal with them.

Netrw is quite good. Oil.nvim is by far the best if you're willing to monkey with a plugin.

A big part of my thirties has been making peace with the reality that I'm not that guy, and trying to balance that with still wanting to excel in the ways I can.

I don't have a better answer for you than the ones already posted here, but I am genuinely curious to read the responses to this.

That is a very reasonable criticism, and I personally agree. My politics differ from his a fair bit on that point.

Risky Biz (and really anything Patrick Gray touches) is awesome. Would recommend.

It just slays me that Andres Freund, absolute bastion of database goodness, is now just "the guy who found the xz bug". Funny old world.

Just as a note, Postgres also has pluggable storage engine, using their tableam API.

I'm definitely in the latter bucket, though I've been here a long time now. I found HN as technical subreddits started to no longer satisfy my curiosity about tech, and fell in love. I originally learned about the startup ecosystem from lurking around here.

I particularly enjoy the irony of this stance being taken by someone with the username "datavirtue".

The challenge being, who else could possibly handle Cloudflare's requirements? I imagine the next step is to build their own, and that's obviously not an easy pill to swallow.

Yeah. The name always makes me chuckle

I have worked on internals of databases for a few years. WLB is just fine, we have oncall rotations same as everyone else. They are deep and complex systems, but mostly what that means is just that average tenure is very high as it takes forever to get up to speed and people generally don't get bored and leave, unless you give them good reasons to.

Overall I enjoy it a lot and would generally recommend it as a good field to get into if you want to tackle hard problems.

Edit: people seem to be conflating DBAs with engineers working on database internals. Those are very different jobs and I'm only talking about the second one.

Paying for a service someone is providing and appeasing ransacking murderers doesn't really seem equivalent to me.

Each year I do it until it no longer sparks joy, and then stop. I usually make it about 2 weeks. I don't see anything wrong with that.

I'm using this year's to dust off my Rust skills in advance of a new job using that language, so that's nice too.

Neat, thanks for sharing.

1. Posting some methodology in the README might be good, such as any filtering you did or didn't do.

2. You do have some obvious duplicates on there, e.g. `cit` and `citadel`, `jane` and `jane-street`. It's probably not worth the effort to manually clean that up, but I figured I'd mention.

On the occasions I'm using MacOS, this is what I reach for too. It works quite well, I agree.

Can't speak for OP, but I use telescope for neovim and I don't think I could use (neo)vim without it.

I got an offer letter, but I've already got an offer elsewhere and will be leaving shortly. I'm not interested in picking up the pieces of the mess they've made. It just makes me very sad, my team was amazing and deserved better.

I can't speak for the whole org, but my small corner of VMware got cut far more than was reasonable. We already ran very lean, and with the losses there will be no new features on our product for a very long time, if ever. Best we can hope for is maintenance unless they're planning to staff back up down the line (they're not).

Echoing the other commenter, I'd be very interested but I can't find an email address to ping you.

I'm a database geek and would happily rep your stuff!

Man I love HN.

Also, thanks for making this. It looks amazing.

This entire merger has been an absolute tire fire, and I sincerely hope it smooths out going forward.

Not holding my breath, though.