Wow, that's really very cool!!

Nice, I saw a lot of blurred buildings and I was wondering why.

I think it's one of the best things you could do in your free time

I used AI for only grammar correction since English is not my first language; other than that, my ideas, my thinking, and my way of writing are mine.

You've erased your own voice and evidence of thinking and writing.

I started my blog to document my thoughts over time, and my second reason is to write as much as I can without relying on AI tools. As I said, I didn't use AI for any sentences; all the thinking was mine. I only used it for grammar checks, which helped me avoid mistakes and improve my writing skills. Even if you still think it's bad, at least I'm trying to improve. The article touched a lot of people and made it to the Hacker News front page, so I think the idea itself is fine, and thanks for your feedback.

I've started to really appreciate posts / articles with grammatical errors. I used to dislike those, but now they've become a proof of a human having written it.

Someone asked me on reddit a few days ago for recommendations on places to eat in the town I live in, said they were going to be traveling here soon and wanted some ideas. So I took 30min out of my day to give some good thoughtful suggestions, clicked submit, and _then_ decided to go check out their post/comment history. It was all perfect grammar and oddly short and specific statements.

Now I'm just annoyed and slightly embarrassed

What do you think happened? AI training strategy?

Honestly, the AI tone makes me wonder if there's any truth behind the story or its just a hallucination. You'd probably be better off making grammar errors, or simply asking AI to list your errors and explain to you why they are wrong.

What a nice moment!

Opposite for me. I'm reading & understanding more because I know most people will depend on it 100% without understanding. That gap feels like leverage.

+1 for git log -S. Two I use daily: rg --hidden -g '!*.lock' to skip noise, and python3 -m json.tool to pretty-print API responses.

I wrote this about git log -S and other Git tools for code archaeology and debugging: https://lucasoshiro.github.io/posts-en/2023-02-13-git-debug/

You can see the discussion about it here: https://news.ycombinator.com/item?id=39877637

The replay simulator from history for off-policy eval is clever - avoids expensive rollouts. Curious how they prevent the policy from overfitting to already-discovered branches and going stale as the search space expands?

Great work!

Thanks, I really appreciate it! Hope others will feel the same. The frontend community needs and deserves simple tools:)

This makes me think of a version of that comic where in the last pane, you get thrown out the window for suggesting such a sensible thing.

Hahaha! Exactly

Website is down I think..