← All posts
In progress

Learning How To Learn

Note ~8 min read

This is my take away from the learning process module on Hack The Box (HTB). I should say this is a really well thought out and skillfully written module. Although the module’s focus is learning in the field of cyber security, Its content is valuable even in the computer science or software engineering fields.

The module is separated into four sub-modules each divided into sections. The combined sections count from the whole module is 20. The four sub-modules are

  1. Mindset
  2. Learning Dependency
  3. Learning Overview
  4. The process

The First sub-module, The Mindset has four sections that explain how an aspiring security analyst ought to think and learn. Section 1: The Way of Thinking, opens up with a scenario of a an aspiring programmer who spends 20,000 hours learning 200 programming languages 100 hours each. Given he spends 8 hours a day every day, that would take him 7 years. After the seven years, he has learnt the 200 languages but has written no program in any of them, he was learning passively. So he spends another seven years actively learning those languages. That scenario is meant to show the learner that their is a lot out there to learn in the field computer science and software engineering and thoughtless deciding to learning everything and anything is the trap. You can learn about every topic out there and specialize in none (essentially becoming a jack of all trades master of none 1 ) or you could learn about just one topic and become an expert in it. This first section also emphasizes the need to learn fast and quickly adapt ones knowledge without learning everything there is about a concept. The scenario commenced with in section one shows that it is redundant and unnecessary for one to learn every language just to consider themselves a programmer. Gaining deep speciality in one langauge allows one transfer knowledge when starting with new languages because all those languages share the three principles tennent stated. That is :

  1. principle of abstraction
  2. principle of correspondence
  3. and principle of data type completeness

Section Two: Think outside the box is more inclined towards security showing the learner that a penetration testers mind should not be restricted by standards set by the system. I didn’t see much connection between this section and the software engineering field.

Section Three: Occam's Razor. Now section three is titled occam’s razor and asserts that the simplest solution/explanation is the most probable one. This could be useful to an engineer trying to come up with a solution to a problem. This hinders them from over engineering the hell out of a problem that could have been solved simply.. It could also be helpful during debugging of one’s code. It would be absurd to come to a conclusion in the face of code that fails to compile and gives no straightforward error message that your code is okay is the reason it is failing to run is because of a bug in the compiler or the hardware architecture of the CPU. Swapping out the cpu for another one would be an overkill solution yet the reason could be way simpler.

Section Four: Talent. This sections emphasizes that although genetics influence ones’s thinking processes, talent itself is not something innate. I agree. The ability to solve a complex problem roots from thought processes developed mainly in early childhood. Children unlike adults effortlessly develop these thought processes because they have not yet developed complicated thinking (which takes us back to occams razor) and have no complex hurdles to overcome. The official definition of talent is natural or inborn potential to do something well without needing extensive instructions. This definition is not precise because it assumes the ability is caused by nature and holds for everything. No child born can suddenly start speaking in 5 different languages or explain to the doctor which laws were not adequately followed during childbirth. Developing talent during childhood often depends on how the parents encourage a child, the section says.

" If a child enjoys something, or at least it is presented as fun by the parents, and the child engages with it, it learns to deal with the given situation. This opens up new possibilities for the child, and new thought patterns are formed, which will be followed by the thought processes first."

The Only reason we are quick to assert that one is talented is when they quickly, efficiently and effortlessly grasp the functionality of something new. That ought to be the definition of talent, the ability to transfer thought processes and patterns from one learned task to another (hence appearing to effortlessly learn the new task).A guitarist who has been playing a guitar for years will find it easier to learn how to play a bass guitar than someone who has never played a stringed instrument in their life. Even a drummer will find it easier to learn how to play the bass guitar than someone who has never learnt how to play a musical instrument because drummers have good sense of rhythm. When learning the bass guitar, the drummer will focus on learning completely different skills that the person whose never played an instrument is yet to learn. Putting these two together in a room, the drummer is perceived as talented because of his effortless grasp of the instrument and unseen thought processes carried over from years of playing drums.

So all in all, this sections takeaway is that, since we posses influence on the development of our thought patterns, thought processes we therefore all have the ability to influence our talent. Masters are not born, they are created.

Section five in the Learning dependency sub-module is titled Way of Thinking. It defines the art of thinking out side the box (as a hacker skill-set but I believe there is a hacker in every programmer ) as seeing things outside the limitations placed on one. The article introduces a scenario that I found insightful to paint the value of possessing a goal towards and achieving that goal. The scenario is:

You're standing still in a room, and your instructor instructs you to move across the room, and you start moving. After a while, the instructor puts a chair in your way. What will you do? - You may sit down on this chair.

Think about it, what would you do? But what if we twist the scenario a bit and say:

Your instructor instructs you to move to the other corner. We start moving, and the instructor puts a chair in our way again. What will we do?

For the second scenario, you will definitely pass the chair and continue to the corner because you know your goal.

In software engineering, computer science, Cyber security or any other field you are trying to get good at, if you don’t have a goal, you will stop at the first obstacle that gets in your way, but with a goal you will resist the urge of skipping from topic to topic when things get tough.

Section 6: Learning Efficiency takes us back to the aspiring programmer student we began with at the beginning. Even if you decide to niche out in a sub-discipline of software engineering, there is a lot still to cover there before one becomes good. So what does it mean to be good at something. Some one good at something has experience in that field which experience is attained from associations and practice made through their learning journey. So the question then becomes, how much should one practice to become competent at a task

The article presents the 10,000 Hour Rule. It says :

The rule explains that you need to spend 10,000 hours to become good at something.

10,000 hours huh!?, That is about a year and two months of continuous learning without factoring in sleep and personal life. If you factor those in, and say you will study for 8 hours a day every weekday (That is Monday to Friday because duh, man has a life), the 10,000 hours are spread out to 5 years. That is the period it takes a medical student at University to study before graduating.Damn, who’s got that time.

We certainly don’t and so this calls for a need to learn as efficiently as possible and get good at our game in the least amount of time. At this point the article introduces the pareto principle also commonly known as the 80/20 rule. The rule states that:

With 20% of the effect we achieve 80% of the effect

So we can become pretty good at something fast rather than spend 10000 hours. We can learn something new in 20 hours, even working on it for just 45 minutes per day. I propose you look at the Learning Pyramid also referred to as the cone of retention which show how to achieve higher retention rates for the information we learn.

Change Log

1 total
  1. complement #1 Return

    Jack of all Trades: The rest of the story

    But as most of you readers already know, the 400 year idiom that started out as just, "Jack of all trades"(initially a compliment by the way), went through evolution in the industrial revolution to become a backhanded compliment warning workers against superficial knowledge across too many domains. The phrase, master of none that got added on later was a caution to workers against spreading themselves thin without acquiring mastery in one craft.(This was of course due to the economics of labour division aimed at output maximization in the booming industrial age). However, in the 20th century, the phrase was further extended in defense of the generalists whose knowledge breadth allowed them to adapt across various disciplines. The full modern day phrase then became, "Jack of all trades, master of none but oftentimes better than a master of one". Here me out, I am not not against possessing broad knowledge across several domains. I personally do. But, I believe one should specialize still. There is this concept of a T-shaped people popularized by Tim Brown. A T-shaped person is that individual who has both deep expertise in a specific domain (signified by the vertical bar in the T) and a broad set of skills in various discplines (the horizontal bar in the T). Today, companies are organized in a such a way that the engineers and marketing team work together. Therefore the marketing team and the engineering members both ought to posses some knowledge in several areas of each others disciplines for a successful company to be build. if the marketing team resolve not to learn or get involved in anything and everything engineering related, then the marketing team may proceed to come up with product expectations that the engineering team may never be able to deliver. T-shaped people are cross functional adaptive collaborators that are highly sought out for today.