> Help people when they explicitly ask for help. When someone asks, the cause and effect reverse. You’re no longer imposing your judgment on someone who never wanted it.
Maybe this is why pull request reviews can become contentious. The reviewer thinks the author is open for feedback while in fact it’s just the widely accepted practice and team/company enfored that you are supposed to give feedback.
I don’t understand this take. In my company a lot of the Claude Coders seem to be very uninterested or unaware of the code they are producing, while I in Cursor usually click ”Keep”/”Undo” on specific code blocks (with little edits) or sometimes the whole file at once if it’s a low risk part of the codebase. I fail to see how this workflow produces inferior code vs shooting in the blind and maybe skimming a huge diff in one go.
I've found most hackathons not personally fulfilling because you can only get small stuff done and finalize maybe a happy path or two, accompanied by some rushed slides, before you run out of time. The AI really changes this and you can actually deeply exhaust an idea.
Just spotted this from Hank's channel [1] on YouTube. I love that I can look at all the crew photos while also knowing where in the flight path these were taken, this is great!
I personally prefer to view it in the same orientation the photographer saw it in their viewfinder. Makes me feel more like I’m inside the vessle looking at the planet.
I'd bet it can be quite a sticky product, if you moved to it from VS Code and don't want to switch around all the time – especially if the enterprise license been approved in your company ().
Maybe this is why pull request reviews can become contentious. The reviewer thinks the author is open for feedback while in fact it’s just the widely accepted practice and team/company enfored that you are supposed to give feedback.