News for hackers. Stuff that matters.
Re:Chain of Thought for Humans by swiftcoder on Thursday October 22, 2026 @04:27AM (#50192735)
> on the basis that I don't work that well on a team

I think you are likely to find that "working well on a team" is the number #1 thing tech firms are screening for. Technical skills are all well and good, but communicating/collaborating are half the job in a big company.

Re:Chain of Thought for Humans by adrian_b on Thursday October 22, 2026 @06:01AM (#50193355)
"Working well on a team" is something completely uncorrelated with the ability of explaining your thinking during the time when you are solving a problem.

All the teams in which I have ever worked have greatly appreciated my contribution precisely because I was always willing to spend a lot of my time explaining to other colleagues, in a differentiated way appropriate for the understanding abilities of each of them, how I had solved my problems or how they should solve their problems.

On the other hand, I am also completely unable to explain my thinking while it is in progress, because reformulating it to become intelligible to the interlocutor would slow me down far too much.

Explaining on-line my thinking would require even a kind of language translation, because when I am speaking to myself I use a special language with precise non-ambiguous words, whose meanings correspond in many cases with old meanings of those words, because in the modern language a very large number of words have vague meanings, which have become very diluted due to the frequent use of those words in inappropriate contexts.

So when I describe some technical solution to others, I typically do not use the words with which I think about it, but whatever words are more fashionable today, so I expect familiarity with them, even when I think that those are not the right words.

Doing such a translation while I think is too difficult, and I do not attempt to think with whatever words become fashionable from time to time, without any good reasons, because in my opinion using the right names for concepts is very important for understanding and using them properly.

Re:Chain of Thought for Humans by noduerme on Saturday October 24, 2026 @03:11AM (#50218940)
I understand what you mean. I don't even use words while I'm solving the problem; internally, I suppose I visualize something like a flowchart of logic, where I can see the holes that edge cases could slip through. Later, after I've tested all the edge cases, I'll spend an hour laboring to wrap it up into a neat non-technical explanation of what needed to he done and why.

That's also why I have trouble working on teams. I tend to evolve a complete picture of how I'm going to approach a large problem in code at the same time as I'm thinking through the business logic. It's mostly written in my head before I sit down to write it, and I'm thinking through the sharp edges as I go along.

It's also why prompting an LLM is often more tedious, frustrating or imprecise than writing the code myself. The code is not the thing, the logic is the thing.

Re:Chain of Thought for Humans by noduerme on Thursday October 22, 2026 @04:34AM (#50192775)
I mean, communicating/collaborating with upper management and turning their requests into solid code? That's what I get paid to do. Communicating/collaborating with other coders? Not so much. Note that I specifically said I don't work for tech firms.
Re:Chain of Thought for Humans by swiftcoder on Thursday October 22, 2026 @08:34AM (#50194456)
Right, I'm saying that if you were to transition out of contracting in the future, this would likely be a bigger issue. In-house dev teams are expected to be highly collaborative, and the interview process attempts to screen out "lone wolf" engineers (insofar as it is possible to do so)