https://z-lab.ai/projects/dflash/

And DDTree?

https://liranringel.github.io/ddtree/

The best thing they did was that they bought an amazing domain name.

The syncopath style is clearly categorized as more liberal (do what you feel is good).

I think OpenAI tried to diversify at least the location of the raters somewhat, but it's hard to diversify on every level.

What's much worse is that Tesla is hiding the reasons for the crashes in the crash reports (the only company with FSD).

Some people in Europe were not that happy when Biden told on public television that the Nord Stream pipeline will be blown up somehow, but luckily the media was good in not talking too much about it and later he listened to his own advisors better about how to communicate.

Whenever I you tried to develop using guardrails with LLMs, I found out that they are much better at ,,cheating'' than a human: getting around the guardrails by creating the ugliest hacks around them.

There are ways to report if a man has been sexual with a woman, but they somehow just don't get kicked out of the driver network.

Also just a simple example: Uber engineering blog is full of examples of how they rewrote their app in native Android then web then native again, but nothing about how to solve the real problems humans experience when driving with them.

It just feels that they view Uber as a simple logistic problem where drivers / riders are interchangeable and less like Tinder that tries to match people with similar scores abd kicks out the worst.

I remember adding lifetimes in some structs and then wanted to use generics and self pointing with lifetimes because that made sense, and then it didn't work because the composition of some features was not yet part of Rust.

Another thing: there are annotations for lifetimes in function signatures, but not inside the functions where there is a lot of magic happening that makes understanding them and working with them really hard: after finally the borrow checking gave me errors, that's when I just started to getting lots of lifetime errors, which were not shown before.

Rust should add these features but take out the old ones with guaranteed automatic update path.

The best engineer I know who can work with huge complex systems in a big company usually starts with a complex solution then after he understands what he wants to achieve thinks backwards and reimplements it in the fewest possible lines of code change with the already complex system.

For coding I love codex-5.3-xhigh, but for non-coding prompts I still far prefer o3 even if it's considered a legacy model.

I can imagine that its higher tool use is too expensive to serve, but as a pro user I would love it to come back.