Readit NewsOmarShehata commented on We can’t circumvent the work needed to train our minds zettelkasten.de/posts/the... · Posted by u/maksimur
That's very hard to know without being in an FMRI machine while reading, which I wasn't, sadly.
Just functionally, it seems reasonable that something happened before that bad feeling to trigger it, e.g. "trying to fit this with already known things, and finding it doesn't".
this isn't a "it depends on what computation happens in this specific case" question, this is a "how does human cognition work".
Every website you visit has the payload delivered over the network before any JS is parsed. It has to, there's no other way. Same with intuition followed by rational thought
OmarShehata commented on We can’t circumvent the work needed to train our minds zettelkasten.de/posts/the... · Posted by u/maksimur
> The reduced engagement with the material reduces the emotional weight of the whole line of action. You mind is an engine that is fuelled by emotion. Without any emotion, you don’t think. Rather, you try to imitate thinking efficiently.
This doesn't sound true and they don't seem to offer any support for the claim.
There's a whole host of emotion-driven cognitive biases, where an effective counter is to reduce the emotional weight of the whole line of action.
Of course, to their credit, it's only by remembering those biases that I could see their error
The first thing that happened in your mind when you read that sentence is (1) a bad feeling. That then triggered (2) a rational, conscious thought that interpreted that bad feeling: "this feels bad because it's not true, here are the reasons why it is not true.
There is ALWAYS an "emotional/intuitive" response that precedes the rational, conscious thought. There's a ton of research on this (see system 1 vs system 2 thinking etc).
There is no way to stop the emotional "thought" from happening before the "rational thought". What you can do is build a loop that self reflects to understand why that emotion was triggered (sometimes, instead of "this feels bad because it's wrong", it's "this feels bad because it points to an inconvenient truth" or "I am hungry and everything I am reading feels bad")
OmarShehata commented on If you're remote, ramble stephango.com/ramblings... · Posted by u/lawgimenez
I'm with the other commenters who agree in spirit, but would hate the details in the post. Assigned channels where you are expected to post your random thoughts feels utterly dystopian to me.
In my experience, "rambling" channels build up organically... as you have a thought, you share it with someone relevant, not just drop it into a channel and see who reads it. Over time, small group chats evolve naturally, and assuming everyone has communications skills, topics that become relevant to the whole team are then shared with the whole team.
I agree that such discussions are healthy, maybe even required, for a functional remote team. But let people organize themselves - don't prescribe specific methods that teams must follow. The last thing we need is a formal framework of how to have organic discussions.
> The last thing we need is a formal framework of how to have organic discussions.
this is no different from best practices for programming though. People take a rule that generally works well, but a manager who doesn't understand it tries to enforce it blindly ("more unit tests!!") and it stops working
computer engineering & social engineering share a lot of the same failure modes (which is good news, if you are very good at debugging computers, but find people & politics confusing, you can unlock the latter once you see in what ways your insight in one domain can transfer to the other)
Issue trackers should be used exclusively for earmarking and tracking the progress of actionable items. This is somewhat similar to the integration between email clients and task managers, like how it's done in Gmail, Zoho, etc. You read the message first. If it requires an action from your side, create a task from it and link them.
There are other projects that do this too. A good example is the 'mise' project. Sourcehut projects use this workflow almost exclusively since it's the default by design. I think sourcehut had if before github did. What I would like to see is better integration between discussions/messages and task/issue lists on all these platforms.