mhlakhani

I believe you can just hit /cost within a session for this

This was me for a long time and it got even worse especially with Humble Bundles — I often ended up buying games on say PS5 though I had them on steam.

Ended up building a side project for myself which would yell at me for trying to buy something I already had.

But that’s ok, sometimes the collection is half the fun

Thanks for writing this up! I learnt a bunch from it. I noticed this didn’t discuss additional layers of caching - I can see how it would fit in, but is prompt caching out of the scope of this system?

Case in point: 2 years ago i interviewed at a number of places with mind boggling valuations and most of the places I got offers from either no longer exist or laid off half their staff. It’s a lottery

They moved to Hack many years ago, at some point the languages diverged too much

As a sibling commenter said, it helps brand and recruiting - which meta cares about

I don’t know if that would have helped here, if memory serves me right:

1. The copy was needed initially 2. This structure wasn’t as heavy back then

… over time the code evolved so it became heavy and the copy became unnecessary. That’s harder to find without profiling to guide things

That one diff blew my mind when I saw it. It’s a prime example of that story about “you paid me a lot of money to know where to fix that pipe”

This echoes well. The most popular posts on my blog are things where I wrote things for myself (e.g. reflections on my career), rather than trying to orient them for an audience or maximum clicks.

I have been using the product for a while and I’m a huge fan. At least for solo/side projects it helps me get reviews in an easy manner similar to what I’m used to at $dayjob and the SNR was good enough that I find myself reaching for it regularly.

It also did find bugs in code I shipped professionally (I back tested on my public commits) and also OSS code shipped by meta (which I found surprising at first)

Hoping to see this and similar tools develop further.

(Disclaimer; I know one of the founders well, though they didn’t ask me to comment here)

> Please explain exactly how you managed to put together a test suite that costs up to 50€ to run.

I'm not OP but have worked with them: have you considered a repo that might have tents of thousands of committers over decades? It's very easy to just have an insane amount of tests.

In large mono-repos, like this one is presumably targeting, running all tests in the repo for a given PR would take years (maybe even decades/centuries) of compute time. You have to do some level of test selection, and there are full time engineers who just work on optimizing this.

The test runtime argument is the main one IMO.

(source: while I did not work on this at a prior job, I worked closely with the team that did this work).

I built the same for my browser extension (effectively dead product) -- would love to see if this pattern has a name so I can share it more widely!

I was at meta. What do you mean? It’s how we used to define staff in our cross company leveling docs.