Effective Understanding of a Topic

Table of Contents

This time, the topic slightly ventures beyond IT projects. Recently, I’ve been doing a lot of research work where I need to construct a coherent extract of practical information from a multitude of knowledge sources. After extensive work in this area, I’d like to share a few tips that I’ve had the chance to apply multiple times.

If you want to build knowledge on a certain topic, like continuous integration or technology X.

Objective: You want to really understand the topic well.
Assumption: You don’t know anyone who could guide you in the right direction. ;-)

Steps to Effective Understanding

  1. Conduct a spike (maximum a few hours) regarding information sources - where you can find materials and their quality (credibility and detail):

    • Specify the questions you would like to find answers to.
    • Primarily choose books - if they are good, you will find reliable and organized information there.
    • Secondly, select academic materials (PhD theses, conference papers) - they are credible, but sometimes unorganized, and if the author is poor, it might just be fluff.
    • Opt for blogs and articles by credible industry figures (recognized and esteemed).
    • Avoid, as much as possible, forums, blogs, and loose information of unknown origin - you’ll read a lot but learn little.
  2. Once you’ve determined a list of credible sources - determine the minimum you need.

  3. If you start reading a text (and it pertains to your minimum), read it very carefully. Do not proceed if you do not understand what you have read.

  4. I have repeatedly found that it’s better to learn less but have razor-sharp knowledge than to skim through everything superficially.

  5. Take notes! This is one of the most important components! Many people read a lot but don’t take notes. Notes force you to better understand what you are reading. To make a note (usually), you need to understand something. Let the note be a paraphrase (your own wording), not a quote.

*Spike - a time-limited, short period to investigate a topic (maximum 2 days) that is unfamiliar or little known to you.

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)

Related Posts

Clean Code

The Importance of Clean Code

There are ongoing philosophical discussions on whether clean code matters and if it is worth investing time to read it. I won’t engage directly in this debate. Instead, a small example should suffice:

Read More

Code Cleanup: Not Just About Refactoring Part 3

Introduction

Due to formatting issues on the blogspot, it is advisable to read this article as a PDF file. You can download the PDF version of the article here.

Read More

The Scrum You Don't Know

But we don’t have a Product Owner! The Product Owner is unavailable! We are working on several projects at the same time! Our deadlines are getting delayed. Testers do not have time to test our code.

Read More