blintz
Joined 11 years ago
Joined 11 years ago
Some feedback:
- I definitely don't want three long new messages on every PR. Max 1, ideally none? Codex does a great job just using emoji.
- The replay is cool. I don't make a website, so maybe I'm not the target market, but I'd like QA for our backend.
- Honestly, I'd rather just run a massive QA run every day, and then have any failures bisected, rather than per-PR.
- I am worried that there's not a lot of value beyond the intelligence of the foundation models here.
> Your smartphone contains materials processed through semiconductor fabrication, chemical etching, metal anodizing, glass tempering, and electroplating — none of which you could start a new facility for in California without years of litigation.
I agree that we should make it easier to do things, specifically by decreasing the amount of litigation involved in doing stuff. But the risk of a bunch of litigation isn't a ban, right? I get that it's trying to be attention-grabbing, but calling it a ban when it's not just sort of confuses the issue.
Instead, I now swear by atuin.sh, which just remembers every command I've typed. It's sort of bad, since I never actually get nice scripts, just really long commands, but it gets you 50% of the way there with 0 effort. When leaving my last job, I even donated my (very long) atuin history to my successor, which I suspect was more useful than any document I wrote.
My only hot tip: atuin overrides the up-arrow by default, which is really annoying, so do `atuin init zsh --disable-up-arrow` to make it only run on Ctrl-R.
I wonder if for almost any bulk inference / generation task, it will generally be dramatically cheaper to (use fancy expensive model to generate examples, perhaps interactively with refinements) -> (fine tune smaller open-source model) -> (run bulk task).