CLI is great for most things. Some times, when I am reviewing a PR, I just tell Codex to do a diff between source and target branches in PR, and generate a HTML report. Then I read that, and also review relevant pieces of code in Zed.
I tried using Cursor, many of my colleagues use it, but stopped using it due to clunkiness. And of late, even in there, many of my colleagues use agentic coding. Instead, I prefer the snapiness of CLI (Codex coded in rust, takes less memory per session) and Zed (also coded in rust,) and blazingly fast. Zed is the new Sublime Text if you will.
I just retried Zed and yeah, it's much much better than last time I gave it a shot!!!
I turned on the review stuff, and yeah I can do more or less what I could in Cursor. Check something. Do a quick inline promtp for the three lines I dislike and move on.
And of course the editor is so much nimbler/nicer.
No plan mode, but for big edits I'd probably use codex or something just like you. If you have any advice for integrating for that flow, I'll take them.
I guess whatever advantage cursor has, it will die once "Sol" is no longer integrated, as it was my favorite heavy work model. But I sure will miss the snappy auto/composer stack of Cursor.
> “There was never a $BETR without @vishal_better. That demands respect.”
and
> “(Lewis’) thoughts about cost savings were good. His ideas about innovation were not,” Garg argued. “It’s so much easier when we’re this close for someone to come in and say that they could have done better.”
The user of better for Better, had me chuckling in these parts.
Overall, I think, we can safely say that Better has definitely seen some better times.
Most of my time these days is learning about domains, not technical skills. I keep programming books around for references, but the books I read most are books that go deep into some domain, either technical like operating systems or network, or soft skills like planning, design and communication.
It’s kinda the old saying about $900/hr expert that only taps with an hammer. The price is not about tapping, it’s about knowing where to tap.
Thanks for your explanation. I did not get it in the first read, and was too lazy to think, until saw your comment.
Just want to point out, that one is actually doing the experiment with a biased coin, then one must ignore all pairs.
e.g in case a coin which is heavily biased, say .9 H and .1 T. One should start with ignoring all the HH pairs, and start only at odd index. Lest, one picks a value like HHHHT (in the case the 2nd HH pair was not skipped, instead they greedily picked up the first HT, which will make the experiment HT biased).
Yep. I too felt that. The insights seem genuine. But probably fell into the temptation to use LLM to structure. I feel increased cognitive load with numbered lists, thanks to LLM.
Well its easy to cause damage by messing up the `rm` command, esp with `-fr` options. So don't take it as a proxy for some great skill which is required to cause damage.
You could easily cause great damage to your Cloudflare setup, but CF has measures to prevent random customers deleting stuff from taking down the entire service globally. Unless you have admin access to the entire CF system, you can't really cause much damage with rm.
I use Zed to review the code.
CLI is great for most things. Some times, when I am reviewing a PR, I just tell Codex to do a diff between source and target branches in PR, and generate a HTML report. Then I read that, and also review relevant pieces of code in Zed.
I tried using Cursor, many of my colleagues use it, but stopped using it due to clunkiness. And of late, even in there, many of my colleagues use agentic coding. Instead, I prefer the snapiness of CLI (Codex coded in rust, takes less memory per session) and Zed (also coded in rust,) and blazingly fast. Zed is the new Sublime Text if you will.
reply