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

Estimation Is Not a Commitment

Estimation Is Not a Commitment

You’ve probably heard that estimation is not a commitment. Sometimes in teams using estimation techniques, some form of accountability for the accuracy of estimation emerges. This is unfavorable for several reasons:
a) firstly, estimation is an approximation (with some probability), not a definitive result;
b) secondly, when accountability kicks in, project games emerge;
c) there are at least several factors causing estimation to differ from the actual time spent on a given task:

Read More

Act as if You Have Infinite Time...

Act as if You Have Infinite Time…

Tick tock, tick tock… The clock is inevitably ticking, time is passing, the deadline is approaching, yet the tasks are not decreasing. The more you rush, the more shortcuts you take, the more problems arise. Meanwhile, the answer is simple: Act as if you have infinite time!

Read More