4 ms·

This needs a prefatory "Tools for a Culture of Reading". How many colleagues will do a literature review before starting something? How many will take notes an

by patrck 4y ago

This needs a prefatory "Tools for a Culture of Reading". How many colleagues will do a literature review before starting something? How many will take notes and try to understand the history of how everything got to be the way things are? RFCs and docs are great; it just seems like they're usually secondary to the functional docs of throwing code over the progressively higher walls of git-hooks, build tests, and ops monitoring.

deleted 4y ago
[deleted]
nonrandomstring 4y ago
Or maybe "tools for promoting a culture of writing". Increasingly I find I may be in a "minority of writers" in org teams who are primarily visual, memetic, kinetic and leave only fragmented records in mixed medias. I've also encountered younger engineers/programmers who pretty much cannot type! (only thumbs on a phone screen) - not even hunt and peck... just staring at the keyboard like it's an alien technology. I actually understand this way of being. Using a visual programming language like PureData/LabView (dragging cords) and interacting via sliders, visual indicators/meters all day long I've inhabited the zone where I have been solving hard DSP problems in a visual-kinetic way, and hardly "thought in language" for hours on end. If someone comes into the workshop and asks me a verbal question it takes a few seconds to reboot that part of my head in order to speak. But what I notice is that this mode of being in the world (Dasein?), is becoming dominant as people wander around all day, smartphones in hand (I don't use them), and so there's fewer moments when people process what they are doing/thinking qua language. So for example; As desktop person who spends a good deal of the day interfacing to the world through a full keyboard and screen my fingers and textual brain are engaged, but some colleagues may do things like send a photo of a schematic taken on their phone, no accompanying text or explanation, not even a relevant subject line. So I get that they are not "thinking" in language. I wonder if I am part of a shrinking/dying culture of symbolic communicators.
- nottorp 4y ago
  I've worked with a guy who simply could not understand what he had to do if told in writing... email, IM whatever. When you told him in conversation he got it and did decent (not brilliant) work. He was a programmer. You'd think writing code all day would allow you to understand writing...
  - gen_greyface 4y ago
    could it be an issue of confidence? i know people who trust the spoken word over the written.
  - crabl 4y ago
    I worked with a similar guy: he would not do anything without first having a conversation about it. According to him, the act of writing notes based on a conversation helped concepts stick in his mind more durably than simply reading what others had written. While I'm sure there's some truth to that, it's absolutely possible to synthesize written thoughts in one's own words without directly interrogating the author. I suspect that the skill of "critical reading" is the missing link here.
    - nonrandomstring 4y ago
      I wonder if you and I and the sibling commenter are talking about dyslexia without realising it? I don't know much about it. A friend of mine has a similarly wired brain. Definitely there's a spectrum from very language orientated minds to those who greatly prefer picture, sound and face to face spoken communications. I wonder if smartphones and iconic interaction are making us all more dyslexic?
      - webmaven 4y ago
        > I wonder if smartphones and iconic interaction are making us all more dyslexic? No. Dyslexia is an actual learning disability, it isn't a lack of skill, aversion, or a missing habit. Dyslexia causes the reader to have difficulty recognizing words by, for example, scrambling letter order, and making it harder to distinguish similar letters (eg. confusing the mirror image letters b and d, or p and q), and similar visual confusion. It has very little to do with an inability to comprehend sentences. Smartphones have actually increased the amount of text people read and write, but it is true that for most people little of that time is spent on text in longform formats rather than texts, tweets, memes, and shorter blog posts. Certainly people who don't read and write longer essays and similar documents habitually are less likely to reach for that sort of reading and writing as tools for thought, and may not be as skilled in their use when they do, but that can generally be remedied with practice. But none of that means that people are 'more dyslexic'. There are other mental configurations (like ADHD) that make digesting longform text more difficult; those can sometimes be accommodated by using different (generally more atomized) documentation formats instead of continuous longform prose. Atomized formats will generally also help non-habitual readers, non-native speakers, the young, non-experts, and so on. Of the four documentation types (tutorials, how-tos, explanations, and reference), only one (explanation) will tend to be expressed as longform text, but it doesn't have to be. Shorter explanations, or breaking the document up into shorter passages, is often well worth doing. There is no downside from making documents easier to digest. For the other documentation types, longer passages are a bit of a "smell" that should be eliminated if possible. As in other contexts, accommodating a broad range of ability in people produces benefits for everyone, including for those who are more able.

by patrck 4y ago

deleted 4y ago

[deleted]

nonrandomstring 4y ago

Or maybe "tools for promoting a culture of writing". Increasingly I find I may be in a "minority of writers" in org teams who are primarily visual, memetic, kinetic and leave only fragmented records in mixed medias. I've also encountered younger engineers/programmers who pretty much cannot type! (only thumbs on a phone screen) - not even hunt and peck... just staring at the keyboard like it's an alien technology. I actually understand this way of being. Using a visual programming language like PureData/LabView (dragging cords) and interacting via sliders, visual indicators/meters all day long I've inhabited the zone where I have been solving hard DSP problems in a visual-kinetic way, and hardly "thought in language" for hours on end. If someone comes into the workshop and asks me a verbal question it takes a few seconds to reboot that part of my head in order to speak. But what I notice is that this mode of being in the world (Dasein?), is becoming dominant as people wander around all day, smartphones in hand (I don't use them), and so there's fewer moments when people process what they are doing/thinking qua language. So for example; As desktop person who spends a good deal of the day interfacing to the world through a full keyboard and screen my fingers and textual brain are engaged, but some colleagues may do things like send a photo of a schematic taken on their phone, no accompanying text or explanation, not even a relevant subject line. So I get that they are not "thinking" in language. I wonder if I am part of a shrinking/dying culture of symbolic communicators.

nottorp 4y ago
I've worked with a guy who simply could not understand what he had to do if told in writing... email, IM whatever. When you told him in conversation he got it and did decent (not brilliant) work. He was a programmer. You'd think writing code all day would allow you to understand writing...
- gen_greyface 4y ago
  could it be an issue of confidence? i know people who trust the spoken word over the written.
- crabl 4y ago
  I worked with a similar guy: he would not do anything without first having a conversation about it. According to him, the act of writing notes based on a conversation helped concepts stick in his mind more durably than simply reading what others had written. While I'm sure there's some truth to that, it's absolutely possible to synthesize written thoughts in one's own words without directly interrogating the author. I suspect that the skill of "critical reading" is the missing link here.
  - nonrandomstring 4y ago
    I wonder if you and I and the sibling commenter are talking about dyslexia without realising it? I don't know much about it. A friend of mine has a similarly wired brain. Definitely there's a spectrum from very language orientated minds to those who greatly prefer picture, sound and face to face spoken communications. I wonder if smartphones and iconic interaction are making us all more dyslexic?
    - webmaven 4y ago
      > I wonder if smartphones and iconic interaction are making us all more dyslexic? No. Dyslexia is an actual learning disability, it isn't a lack of skill, aversion, or a missing habit. Dyslexia causes the reader to have difficulty recognizing words by, for example, scrambling letter order, and making it harder to distinguish similar letters (eg. confusing the mirror image letters b and d, or p and q), and similar visual confusion. It has very little to do with an inability to comprehend sentences. Smartphones have actually increased the amount of text people read and write, but it is true that for most people little of that time is spent on text in longform formats rather than texts, tweets, memes, and shorter blog posts. Certainly people who don't read and write longer essays and similar documents habitually are less likely to reach for that sort of reading and writing as tools for thought, and may not be as skilled in their use when they do, but that can generally be remedied with practice. But none of that means that people are 'more dyslexic'. There are other mental configurations (like ADHD) that make digesting longform text more difficult; those can sometimes be accommodated by using different (generally more atomized) documentation formats instead of continuous longform prose. Atomized formats will generally also help non-habitual readers, non-native speakers, the young, non-experts, and so on. Of the four documentation types (tutorials, how-tos, explanations, and reference), only one (explanation) will tend to be expressed as longform text, but it doesn't have to be. Shorter explanations, or breaking the document up into shorter passages, is often well worth doing. There is no downside from making documents easier to digest. For the other documentation types, longer passages are a bit of a "smell" that should be eliminated if possible. As in other contexts, accommodating a broad range of ability in people produces benefits for everyone, including for those who are more able.