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

So How’s It with Architecture - Up-Front Design or Evolutionary Architecture?

So How’s It with Architecture - Up-Front Design or Evolutionary Architecture?

Where does architecture currently stand? We can say that there are two classic approaches:

Read More

Have a Clear Vision, Stick to the Intention and Adjust the Implementation

No matter if you are a tech lead, Scrum Master, Product Owner, or a member of the team, if you want to make your idea a reality, here is a very simple (and of course very difficult to implement) advice:

Read More

Ease of Access Over Information Organization

Ease of Access Over Information Organization

Recently, I’ve been experimenting with various ways to access information remotely from anywhere. My primary tool has been SVN, which works great for software projects, but it’s not as effective for document storage in my case. There are two reasons for this:

Read More