Degorath

I sort of agree. Any benchmark that shows gpt-6 sol as better than gpt-5.6 sol is incredibly suspect.

Or I'm wrong and working with a model has an aspect to it that is not captured by any benchmark.

That's quite surprising, of the set {Claude Code, Codex, Pi, OMP} I must say I find CC to be the worst.

They all have some annoying downsides and I use CC the most, but it's gotten to the point where I'm for sure actively shopping around for better harnesses.

There's high level boss encounters and such, they're quite difficult and fun.

As a vaguely related example I can recommend Settled's "Nightmare mode" player-invented game mode. I don't want to spoil it ahead of time, but he fights some cool endgame content with the caveat that if he takes even a single point of damage, his account is automatically deleted.

Well, stacking is one thing, doing it well is another (see github) ;)

But that's good to hear.

As someone trying to compete in this space: will ERSC make the change/commit their unit of code review? It's one of the pet peeves I have with GitHub et al.

Thought I saw that announcement on LinkedIn a few weeks back already!

Unfortunately I wouldn't know how to do that.

But just saying that I would probably argue against any new forge at my workplace if it didn't adopt the jujutsu model for changes. While agents can wrangle git better than 90% of developers, jujutsu just works much better for both.

Does it support jujutsu natively?

There's simply a ton of teams that also never updated. My previous team was not using RTK and our redux setup was extremely confusing to me (a backend engineer).

Ah, that's a shame to hear. I would only like to add that at least for Android apps that I've been "hanging around" (my team never really worked on them), the teaching materials that are provided have generally made them a lot more pleasant compared to the RN stuff.

While all of the points you brought up are valid, I've hated every react native app I've ever had to work on. Not because of react native itself, but because they usually take random react developers to work on these apps and the structure they create is absolutely horrible to work with (compared to, for example, native apps).

What was your experience on that aspect with Flutter?

Bit late to the thread, but I'm building a EU native jujutsu forge that optimises for productivity and ability to deliver your features faster.

I saw that tons of companies are still on GitHub, using their unproductive tools that have no vision to how they work together and I want to do something about it.

The landing page will be up soon, but for now I am actually looking for a cofounder with a technical product management or engineering management background (the multitasker hustlers that know tech), so do reach out if that sounds interesting to you!

That's really cool! I tried getting on board with ERSC, but the timezone difference proved too much :(. At least it gave me the kick to try and build my own company, though!

Already working on that!

My experience is that in companies that rely on this flow, these assumptions are generally hashed out during design doc review/discussions. I have never had it happen to me that I need to discard the rest of the stack for an assumption that did not hold. From another angle, if I fear that this might be the case, I hold off on sending parts of the stack to review until I am sure of the assumption holding OR I instead have a "workspace ball of mud" from which I can `split` out well-formed commits. I found this to be an incredibly productive workflow.