akshayshah

7 ms·

1.
by akshayshah 2mo ago
Huh - are you sure? I was pretty sure that the original implementation came from the Android & iOS repos.
2.
by akshayshah 2mo ago
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 fairly extensive conformance testing harnesses. T
3.
by akshayshah 2mo ago
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 write a gRPC interceptor that uses it. Here's
4.
by akshayshah 2mo ago
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. That doesn't quite match my professiona
5.
by akshayshah 4mo ago
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 license checked into the repository apply to the released art
6.
by akshayshah 4mo ago
These days, he’s also working on Hegel - bringing test case reduction and PBT to more languages. https://hegel.dev
7.
New Logic for Programmers (and the future of this newsletter)(buttondown.com)
2 points by akshayshah 5mo ago|0 comments
8.
by akshayshah 6mo ago
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. Google’s priority internally is cpp interop, so they use u
9.
by akshayshah 6mo ago
And https://arxiv.org/pdf/2310.10688 if you want the full paper.
10.
by akshayshah 7mo ago
Whoops, bad link formatting: https://x.com/patrickc/status/2015562569105465347
11.
by akshayshah 7mo ago
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.
12.
by akshayshah 8mo ago
There’s a whole section on this on TFA: https://celbyexample.com/execution-cost/
13.
by akshayshah 8mo ago
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 out of space in the main data center and new management is d
14.
Antithesis – The Deterministic Computer(mack.work)
10 points by akshayshah 9mo ago|0 comments
15.
by akshayshah 9mo ago
In broad strokes, I think this is similar to Bitdrift ( https://bitdrift.io ) - though they’re focused on mobile observability.
16.
by akshayshah 9mo ago
Alas! Once again, I’ve learned what happens when I assume.
17.
by akshayshah 9mo ago
Totally fair. At least in part, I blame the choice of <em> and <strong>: it's really not clear what the hierarchy between them is, so I just think of them as the online versions of italic and bold. <mild> and <stro
18.
by akshayshah 9mo ago
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 Markdown: how to handle intra-word emphasis. In the re
19.
by akshayshah 10mo ago
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 clusters do not pro
20.
by akshayshah 10mo ago
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/why-fsync-is-needed-for-data-s... [
21.
by akshayshah 11mo ago
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. Testing/quick is adequate for small things and doesn&#x
22.
by akshayshah 11mo ago
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 worth your time. The material isn’t really specific to F#.
23.
Catalog of reliability properties for blockchains (Antithesis)(antithesis.com)
1 points by akshayshah 11mo ago|0 comments
24.
by akshayshah 11mo ago
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. As usual, it depends.
25.
by akshayshah 1y ago
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 to control write costs and smaller batches to reduce latency
26.
by akshayshah 1y ago
I'm no expert in corporate finance, but whether or not OpenAI goes bankrupt feels like the wrong question to me (in thinking about this loan). Wouldn't a bank be more concerned with (1) the likelihood that OpenAI can raise another
27.
Keeping Master Green at Scale(dl.acm.org)
2 points by akshayshah 1y ago|0 comments
28.
Chroma Technical Report: Generative Benchmarking(research.trychroma.com)
3 points by akshayshah 1y ago|0 comments
29.
by akshayshah 1y ago
TFA goes into this in some depth: there's an option to subscribe for one month with a one-time payment. After the month is up, your account automatically reverts to the free plan and you get an email with your fonts attached.
30.
by akshayshah 1y ago
I’ve been exploring porcupine lately too - the visualizations are especially useful when debugging. It pairs exceptionally well with any DST setup. Thanks for the great tools, Anish!

More ›