I Read It But Don’t Get It, or How to Tackle Technical Texts

Ruby Development

Steve Lynch

@stephen-andrew-lynch

#software-engineering

#ruby-development

#learning-techniques

I Read It But Don’t Get It, or How to Tackle Technical Texts

by Steve Lynch

Summary of the Video

In this engaging talk titled "I Read It But Don’t Get It, or How to Tackle Technical Texts", Steve Lynch, a software engineer and former English teacher, explores methods to effectively comprehend technical books, particularly for professionals in the software engineering field. Lynch emphasizes that while technical texts can often be intimidating, employing specific reading strategies can enhance understanding and engagement.

Key Points Discussed:

Definition of Technical Texts: Lynch elaborates on what constitutes a technical text, specifically focusing on books related to software development, coding practices, and system architectures.
Importance of Reading Technical Texts: He discusses the significance of these texts in providing comprehensive arguments and insights that differ from other media like tweets or blog posts.
Engagement in Reading: Lynch compares his own lack of engagement with technical books to a student's disengagement when reading fiction. He identifies several strategies to foster an active reading posture:
- Previewing the text before diving into the chapters.
- Making Connections throughout the reading, such as relating content to personal experiences or other texts.
- Questioning the material for clarity and deeper comprehension.
- Reviewing what has been read to reinforce learning.
- Applying insights gained to work or other contexts.
Practical Examples: Lynch shares his personal experiences and techniques, such as using index cards for capturing thoughts and specific focus questions while reading. He notes how writing down connections and questions helped him stay engaged and derive more from the text.
Challenges in Application: He addresses the struggle of directly applying learned concepts to real-world coding tasks, emphasizing that understanding evolves over time rather than instantly transforming one’s skills.

Conclusion and Takeaways:

Active Engagement is Key: Successful reading of technical texts requires intentional engagement through previewing, connecting, questioning, reviewing, and applying.
Capture Thinking: Making thoughts visible aids in comprehension and retention. Lynch encourages finding personal methods to track and reflect on reading experiences.
Patience is Essential: Gaining proficiency and confidence with technical material takes time. Readers should expect incremental learning and be gentle with themselves during the process.
Connection to the Work Environment: Lynch also poses questions on how to help bridge the gap between theoretical knowledge from books and practical applications in work settings.

Overall, Lynch's talk serves as a helpful guide for engineers and developers navigating the complexities of technical literature.

00:00:10.480 My name is Steve, and today's talk is called "I Read It But Don't Get It" or "Tackling Technical Texts." As I start off, I'd love to know how you guys are doing, so if I could get a visual thumbs up if you're feeling good, thumbs in the middle if you're okay, and thumbs down if you're having a terrible day.

00:00:17.359 I see almost all thumbs up, which is super impressive. It sounds like everybody's having a good morning.

00:00:22.800 To give a little bit of background on myself, I’m a software engineer, but I used to teach middle school and high school English for ten years. Like many of us, I transitioned into software engineering by going through a coding bootcamp. Even though I was told this many times, I'm shocked by how much of my personal experience as a teacher overlaps with my experience as a software engineer.

00:00:35.200 That's what I want to get into today. To be clear about what I want you to get out of this talk, I think there should be deliverables, or things you can do the next day as professionals. My goal is for you to leave today's talk with three more tools or questions—no more and no less. If you leave having three questions to ask yourself while reading a challenging text, then I will consider this a success for both myself and for you.

00:00:52.879 You might be wondering what I mean when I say a technical text. While this is not an actual definition, it’s one I made up that will be useful so we all have the same foundation for today's talk. When I talk about a technical text, I'm referring to something related to the writing of code, the development of code systems, code architecture, or any kind of theories about that work.

00:01:07.040 To be even more specific, that is the technical part of it. When I mention a text today, I mean a book-length text written in chapter format—very traditional. The reason I want to emphasize that I am talking about books is because while texts could include a tweet, blog post, TED talk, or conference presentation, today I want to be very literal about referring to a chapter book.

00:01:16.000 If you're wondering what sorts of technical texts I'm referring to, consider a book that has a picture of space on the cover, an abstract 3D art piece, or most popularly, a 19th-century illustration of a bird. These are signs that you're about to read a technical text.

00:01:29.920 But why should we even read these? Why am I discussing how we might tackle them? Someone might read these books because they're very commonly recommended. I know when I started as a software developer, people said, "You should read Clean Code." These texts are often guidebooks given to early career and mid-career engineers or developers, and even those who have been in the field for 10 or 20 years revisit them.

00:01:40.400 Another reason I think these traditional books are useful is that they present longer arguments for particular approaches to code. You can read a tweet that tells you something interesting, but that argument is incredibly compact. The amount of information received in a tweet is minimal. By reading a book-length text, you're exposed to a different kind of evidence and argument, which lends itself to different kinds of learning.

00:01:56.000 Now I want to lay out a roadmap for where we're going today. We've established what a technical text is, why we should read them, and why they might be useful. I want to start by telling you about how I discovered that I was a disengaged reader—that I was not engaged in reading technical texts. Then we will discuss what it means to be an engaged reader: what does an engaged reader do?

00:02:10.479 Finally, I want to show you practical examples of how I put the theory from the second part into practice. For some of you who are itching to know what you can actually do to be more engaged with the text, I will share the literal transcription of what I did. Last of all, I want us to think about how we can extend these ideas beyond just reading technical texts.

00:02:28.400 I'll start by telling you a story about a student I had; let’s call him Jason, a seventh grader.

00:02:33.919 During independent reading time, he got to choose his book and read it. Every time I looked over during this time, he was nodding his head, his eyes were moving, and he was turning the pages at an appropriate rate. He indicated physically that he was reading a book; he looked engaged. As the teacher, I might ask, "Hey, Jason, how's your book?" because I had read that book.

00:02:46.479 Jason replies, "Good." Now, I can’t tell if this is an actual review of the book or if he’s just being a monosyllabic teen, so I ask some follow-up questions: "What do you wonder about the main character? What do you think about her?" He replies, "She’s nice." That sets off alarm bells in my head because the main character is a serial killer—she’s not very nice.

00:03:00.400 So while he's physically reading the words, he's not really making any sense out of the book. Fast forward ten years: now Steve, the teacher, has a better haircut and is a software engineer. At work, they’re reading Practical Object-Oriented Design, and he’s super excited. He’s convinced he’ll finally gain the technical knowledge he needs to understand some of the concepts missing from his coding bootcamp.

00:03:17.120 They go to the first meeting, and a really wise engineer asks, "What did you think of that second chapter?" Steve responds, "That’s good." When she follows up, "What do you think she was ignoring in the second chapter, though? It felt like there were a lot of holes in her argument," Steve just responds, "Sounded good." This should set off alarm bells in your head because Steve does not sound engaged.

00:03:30.720 The shocking part is that this kid loved reading. I read all the time as a kid and never had to work hard to make sense of texts; fiction was easy for me, and a lot of nonfiction was too. However, I was really struggling to engage with technical texts. That's when I decided to think about how I dealt with a student like Jason—how do I teach a seventh grader to engage more with a book—and how can I, as a 39-year-old, implement those practices with a really dense, challenging text.

00:03:53.239 Now, let’s talk about what it means when I say Jason wasn’t engaged with his fictional text, and I was not engaged with my technical text. What does it mean for a reader to be engaged with a book? I want to first start with some baseline assumptions so you know where I’m coming from theoretically.

00:04:10.959 First of all, reading is a skill. Note that the word "do" is italicized; it’s an active verb. Many people think reading is simply opening a book and letting words and ideas flow into their heads. However, meaningful reading and making sense of a text is an active skill that requires actual thinking. You need to be aware of your thinking, which we’ll get into. This means reading is a skill that you have to practice and often learn.

00:04:28.320 Second, this might be obvious, but it’s worth saying: just because you read well doesn’t mean you’re smart. Conversely, importantly, just because you're really smart doesn’t make you a good reader. I like to think of myself as somewhat smart, but I struggled to be a good reader of technical texts. This meant I needed to supplement my reading with new skills in order to make meaning out of technical books.

00:04:43.840 Lastly, texts are not documents set in stone. This comes from my undergraduate degree as an English major, where you learn that texts are flawed and biased. We should think of any book we read as a reflection of one person's point of view, presenting their experience and argument with the evidence available. The richness that comes from a text arises from our dialogue with the author. We shouldn't take the books literally or as 100% true; instead, it’s for us to interrogate and engage with.

00:05:00.480 Next, let’s talk about what an engaged reader does. An engaged reader has an active mind while reading about the text itself. I emphasize "about the text itself" because we have all had experiences of having an active mind while reading, but we were not thinking about the reading. We might be thinking about having enough lemons for a recipe or a project we need to respond to. Instead, an engaged reader focuses their thoughts on the book.

00:05:14.080 Importantly, engaged readers are aware of what those thoughts are. This sounds a little bit like meditation; in meditation, it's not that you don't have thoughts, it's that you are aware of them. You can notice and label your thoughts. Engaged readers can do the same thing.

00:05:30.720 I’m going to create five very crude, arbitrary categories to describe the actions of engaged readers. I say they are arbitrary because all things in life are arbitrary, and there will be similarities. However, what I want to argue is that an engaged reader previews the text, connects with it while reading, questions the text, reviews it, and applies what they’ve learned from it.

00:05:44.960 An important note here is that previewing happens before you start reading the bulk of the book, while applying happens after you've read the book. Most of what you'll be doing as an engaged reader of a technical text happens during the reading—that's where connecting, questioning, and reviewing come in.

00:05:58.160 So, what does this look like? Let’s label these five verbs. One, previewing. Some of us are really good at this already, while others may not be aware of the tools available to us. A good reader will pick up the book and start to get acquainted with it. You read the back of it to see what it's about, who the author is, and where they work. You might skim through chapters or sections of the book to orient yourself.

00:06:09.440 This is like when you're going on a trip and you check the overview in Google Maps or similar software before diving into the directions. You want a big picture of where you are going.

00:06:21.120 Next, while you are reading, you make connections. This is familiar to anyone who has taught in middle or high school. An engaged reader can make connections in three ways: text to self, text to text, and text to the outside world. For example, as a software developer, you might read a passage and think about how it relates to code you've written. You could also recall a blog post or a previous book that covered a similar idea.

00:06:33.760 Last but not least, you connect it to things you see outside. This is closely related to text to self, as we live in the same world, so it may be easy to make those kinds of connections.

00:06:46.560 Another important action is questioning. You can ask questions about the text, both to clarify what the author is stating and to interrogate their point of view. This reflects the idea that texts are not set in stone. You might read a passage and wonder why the author left something out or what might provide a counterpoint to their argument. You can continuously ask yourself questions as you read.

00:07:03.679 Now, reviewing is also essential. An engaged reader will reflect on what they’ve read previously. Before starting a chapter, they might flip back through what they read to recall the main ideas. A truly engaged reader can summarize, meaning they can restate an idea in their own words. This step gets you closer to comprehension.

00:07:16.000 Last of all, an engaged reader applies what they’ve learned. This is perhaps the most crucial action because it reflects why we read technical texts to begin with. Nobody reads Practical Object-Oriented Design for the plot; we read to gain insights that will inform our work.

00:07:28.640 An engaged reader can take the concepts from a text and adjust their approach at work. They can finish a technical text and when they read another, recall relevant ideas and recognize differing arguments. We can also apply these ideas to other areas of our lives.

00:07:42.560 To review, an engaged reader previews the text before reading, connects while reading, questions the material, reviews what they’ve read, and is capable of applying the knowledge gained to various contexts.

00:08:01.440 Now, let’s examine what this actually looks like in practice. Referring back to my experience, consider the book we were reading as an informal study group among engineers.”},{