News for hackers. Stuff that matters.
Re:How to Think in Writing by astrobe_ on Sunday July 07, 2024 @03:56AM (#40895943)
> If you have a crowd of followers

That's a big if, and that's the problem with relying on feedback. The more specific the topic, the less people you'll find that can give relevant feedback. Even within a team (less people but more specialized in your problem domain), it can be difficult to get relevant feedback.

It still works because it is a form of "rubber-ducking". But the less involved in your topic the "crowd" is, the less efficient it is.

Moreover feedback has the same problem as tests (and code reviews): it can show the existence of an inconsistency or a blind spot, but positive feedback doesn't prove that you are entirely correct.

Re:How to Think in Writing by setopt on Sunday July 07, 2024 @04:10AM (#40895997)
> positive feedback doesn't prove that you are entirely correct

You often don’t need to be 100% sure that everything is correct before you move from “writing notes” to “doing something”. At that point, I find that note-taking becomes counter-productive because of the time it requires.

I say this as an avid note taker myself: I’ve often caught myself procrastinating by polishing my notes 100%, instead of moving on and getting things done.

Re:How to Think in Writing by mistermann on Sunday July 07, 2024 @11:36AM (#40898375)
> It still works because it is a form of "rubber-ducking". But the less involved in your topic the "crowd" is, the less efficient it is.

Might this be based on some unsound assumptions?

We might have accidentally stumbled into a real-world test of the proposition here. :)