while learning about something new, what do you think is a more important question :
- What is X? or
- How do X work ?

because some people try to go for route a: i.e, first understanding what is X followed by how it works, while some try to jump straight onto how X works, and a working code teaches them about the what and why behind X.

  • 1
    It's a matter of personal preferences.

    For me I try to understand what is "X" first.

    After I understand what "X" does and I can use "X" without any problem , I try to figure out how actually "X" work.
  • 3
    there is a method for that called System Mapping which is a part of System Thinking. Where you explore complex topics fast and methodicaly via a visual representation. It's used in the Service Design field to asses and adress problems.

    Here is a good article about that.

  • 1
    What is X, how can I use it to solve Y.

    After/during implementation. Does it work?

    Yes -> depending on how much time I have, either note down some usage info or a bunch of TODOs.

    No -> why didn't ... Work, what did I do wrong... Checks the docs in details, searches the issues, look for the quickest fix
  • 1
    HOW and WHY are the questions that tell us the most.

    WHAT's answer is likely to be too vague.

    When I'm learning smth new, I'm firstly asking WHY does the world and I need it (i.e. what problem does it solve) and HOW does it work.

    WHAT doesn't tell me much. Possible answers are: "REDIS", "AIX", "Tivoli Storage Manager", "Netcool", "Software", etc. See? There's not much use for this info.
  • 3
    Honestly I don't get it.
    If I don't know what X is, why should I learn how it works?
    That doesn't make sense.
    Obviously first I need to know what X is.
  • 2
    @Lensflare I'm in the same boat. First what, then why, then how does it work / how do I use it. And I don't really see another way:

    What is creating interest and giving basic information, why is giving you reason to learn it, how is giving a deeper understanding and enabling practical use. If I don't have any clue what something is, then how can I understand how it works?

    Try explaining how a CPU works to someone without first saying that it's the things doing all the calculations in a computer.
  • 1
    best is if you can amswer all W questions at some point.
    the strategy to reach that point seems not to matter much.
    bigger issue is people forgetting some Ws.
    What is X and what can you accomplish with it, Where is it used, Why is it used, Who should be using it. Whether it should be used in the first place.
  • 1
    Start building shit and learn whatever you need to continue building the thing. The point is building stuff, not learning for the sake of it.
Add Comment