trb

Considering other metrics then p99 for user impact is unwise. All users will at some point experience a <1% request, it's not like half of all users will only send requests what will be under your median latency, some of their requests will hit your worst-case.

By focusing on the tail and optimizing worst cases you help users more than by improving your median latency.

  L icon Grok 4.1 Fast won 13 of 30 games at $0.97 per win

  The next-best winner was A icon Claude Sonnet 4.6 with 5 wins, at $26.78 per win. That’s a 27x difference. The model that isn’t on most top-model lists beat the model that is, on the thing a routing customer actually cares about.

  The model with the most kills did not win

  H icon GPT 5.4 killed 38 agents across 30 games. More than anyone else. It came in second on the leaderboard with 2 wins. 

If grok-4.1-fast was the top-winning model, and Claude 4.6 Sonnet the second, how did Gpt-5.4 come in second on the leaderboard? Which one is second, Claude 4.6 Sonnet or Gpt-5.4?

  There were 11 games between “best at killing” and “best at winning”.

What does that mean? How are there 11 games between "best a killing" and "best at winning"?

It's fascinating to see all these bugs in Claude Code - HERMES.md, this OpenClaw issue, the recent thinking-message pruning and cache-skipping bugs.

They seem like the class of bugs I see in my vibe-coding experiments, and I think the Claude Code lead has said many times that he/his team don't read the code for Claude Code themselves, that it's basically vibe-coded.

If Anthropic itself can't make vibe coding work, who can?

Finding microphones that look nice, can pick up voice at high enough quality to extract commands and that cover an entire room is surprisingly hard.

If this device delivers on audio quality it's totally worth it at $59.

For me, I think it has to do with ..just having done more, experienced more.

When I built blanket forts as a child it was something new, my first attempt at building something. It was exiting to figure out how to do it, and enjoy the end product. After a few of those it became a bit more usual, and I started doing other things - play with model cars, build lego sets, etc.

I recently tried welding and I felt that same tinge of excitement - I'm gluing metal together! It's basically magic, I'm taking separate parts and turning them into one. I'm not welding purposefully or to build something, I just really like the act of welding.

Welding was new to me, I never experienced it. I think as a child I everything was new to me, the way welding is. I approached the world with a curiosity that drove me to play with it, to figure it out.

But now I've figured a lot of it out. It's not as fun to play with anymore, because I've exhausted all the angles of play I could come up with (and I did that a long time ago).

I still find that curiosity that drives me to play with something, to figure it out - but I have to look for it, find aspects of life I haven't experienced yet.

Same here, I was curious about Kagis low ranking, and couldn't replicate the search results. Also saw ublock Origin on #3, good results for tires, transitors and snow, etc. I've never used any of the Kagi search result weighing features.

Ctrl+F on the page for "System prompt" doesn't show any hits. Given how important those are for ChatGPT (another thought - was the author testing GPT3.5 or 4?) I'm not sure how much weight to put into the ChatGPT results either.

Not sure how much I can take away from this comparison.

I've experienced both, and I prefer the mono repo.

Our challenges with multiple repos mostly revolved around builds and orchestration. We had to apply all build/deploy changes to all repos, and that increased the chance of doing some small thing wrong. Finding what exactly is wrong with one repo that should be the same as all the others was like one of those "find the differences" pictures. Really annoying.

This is more microservices than multi repo related, but making sure all the different services are released in sync was hard and annoying and often caused issues. Eg a specific API was updated and released but the for a consumer had to be rolled back and the rolled back version wasn't compatible with the new API. So current version and roll back wasnt an option. Rolling back the API would require rolling back all consumers but crap, one of the consumers applied a big migration to our core database and rolling that bank would take forever. And so on.

Just tons of little edge cases that went wrong at the worst time because it was so hard to foresee all the issues.

Monorepo and monolith is so comfy. Want to share code? Move it up one or two directories and import from there. No issues with two bundled react versions in two builds. Easy to refer to code from other teams, never an issue that someone forgot to add you to that one repo almost no one uses but that you need to commit to during firefighting.

I'm not saying multi repos/micro services can't work, but it's hard - you need strong processes that prevent people from being lazy, you need monitoring and management well defined, you need extra tooling that's aware of the repo structure, you need a strong story around migrations, and so much more.

I currently work with a mono repo monolith that over a thousand devs contribute to daily and it's Cindy comfy. It feels much easier to fix too many devs in one repo (primarily via strong compartmentalization) than to fix too many repos/services

fdsafdsafdsa

React is a view library that doesn't even provide a way to do XHR requests. Angular is a complete framework. They are very much hammer and screwdriver, completely different and incomparable tools.

There seem to be a lot of people thinking front-end is just a mess of different options all doing the same thing. And the same people show little understanding of the complexities and nuances of front-end solutions.

Hi there,

I'm happy to answer any questions you have, salary too, if you send me an email. Sadly I can't publicly disclose our salary range, so if you're willing to bear with me and jump through the emailing-hoop I'd appreciate it.

- Thomas

This happened to me. I worked on a side project in high school that grew into a company after about eight years of work. Three years and a pivot later we gave up due to decreasing traction, and returned whatever funds were left to the investors.

I moved back to my parents for about a year to work on other side projects, but ended up looking for a job and found an awesome small company that I'm very happy working for. I'm still working on market-focused side projects and without the stress of having to make money/gain traction it's a lot more fun. I really prefer this setup, especially since a small company allows me to scratch most product-development itches I have since there's not a lot of bureaucracy.

A lesson I've learned: Quit early. If you feel bad about the project right now, end it as soon as possible As in, tomrrow. Don't stick around waiting for the big break. I've done exactly that, and while we actually ended up with some paying customers after our pivot, we would've had to achieve an insane growth to be worth anything to my co-founder and me due to the dilution of our shares. It's not worth basically building a new company for the smaller fraction of shares you have after taking an investment.

So..I wipe, touch the door handle and then wash my hands?

Twitter bootstrap makes prototypes usable. It does not replace good design on a product, and no one claims that.

If you are developer, please use it on your next prototype instead of throwing together some html and css.