Get an improved navigation experience with a Chrominium based browser.
Dismiss
Ruby Video
Talks
Speakers
Events
Leaderboard
Sign in
Talks
Speakers
Events
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Technical books can be a key and important source of learning for engineers and developers of all experience levels. However, it is not uncommon for some of us to pick up even a famously “approachable” text and struggle to hack our way through each page. Help, however, is on the way -- there are concrete skills that engaged readers of all kinds of texts employ while reading. This talk will outline those techniques while also providing concrete questions that can be used during reading to help you stay
Date
Summary
Markdown supported
### 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.
Suggest modifications
Cancel