Viewing profile — akshayshah

Huh - are you sure? I was pretty sure that the original implementation came from the Android & iOS repos.

I'm surprised (without any particular positive/negative valence) that the article doesn't mention using AI to write the port - especially since both CEL and protovalidate have fair…

Very fair point that protovalidate comes from Buf, not Google. But it's worth noting that protovalidate can also work with plain gRPC - it's an independent library, and anyone can …

I'm not sure how to think about what you mean by "almost never." If most commercial software is web frontend + monolithic app code + relational DB, then you may very well be right.…

It's strange to see this project on Github: the repository is basically just a README and Github sponsors config, without any source code I can see. Does the Polyform Shield licens…

These days, he’s also working on Hegel - bringing test case reduction and PBT to more languages. https://hegel.dev

This is very cool! I’m most interested in the protobuf runtime - Rust has historically used Prost, which doesn’t pass the protobuf compliance test suite and isn’t Google-maintained…

And https://arxiv.org/pdf/2310.10688 if you want the full paper.

Whoops, bad link formatting: https://x.com/patrickc/status/2015562569105465347

To be fair, the name was a joking response to https://x.com/patrickc/status/2015562569105465347…and then the temporary skunkworks name stuck, as it always does.

There’s a whole section on this on TFA: https://celbyexample.com/execution-cost/

I’d be surprised by this: GitHub pretty famously used Vitess, and I’d be surprised if each shard were too big for modern hardware. Based on previous reporting [0], they’re running …

In broad strokes, I think this is similar to Bitdrift ( https://bitdrift.io ) - though they’re focused on mobile observability.

Alas! Once again, I’ve learned what happens when I assume.

Totally fair. At least in part, I blame the choice of and : it's really not clear what the hierarchy between them is, so I just think of them as the online versions of italic and b…

I like Markdown, and generally agree that it strikes a nice balance between correctness and usability... ...but it's delicious that this blog post also demonstrates an ambiguity in…

At least per the Redis docs, clusters acknowledge writes before they're replicated: https://redis.io/docs/latest/operate/oss_and_stack/managemen... The docs explicitly state that c…

No. Redpanda has made a lot of noise about this over the years [0], and Confluent's Jack Vanlightly has responded in a fair bit of detail [1]. [0]: https://www.redpanda.com/blog/wh…

Rapid is excellent. It also integrates with the standard library's fuzz testing, which is handy to persist a high-priority corpus of inputs that have caused bugs in the past. Testi…

Sibling comments have already mentioned some common strategies - but if you have half an hour to spare, the property-based testing series on the F# for Fun and Profit blog is well …

Sometimes, sure - but sometimes, passing around a fat wrapper around a DB cursor is worse, and the code would be better off paginating and materializing each page of data in memory…

Very cool! Using “object storage for primary durability” seems difficult for any OLTP workload that’s latency-sensitive - there’s a fundamental tradeoff between larger batch sizes …