Thank you Kaushal Joshi that means a lot! Getting comments is really encouraging.

I hope I make it worth your time. And that you find value in what I have to share :D

Regarding the writing style, I write in a way that is easy to read for me. As I have ADHD. Reading is very hard for me if there are long sentences and paragraphs. And if people use the passive voice too often.

Sometimes I use the Hemingway app

Hemingway is dope. Sometimes i use it myself too.

It is very interesting that you mention Popper's. His approach of scientific-knowledge-as-provisional is one of the starting points of the topic of "logics of discovery". The question of whether we can find a way to scientifically study the process of hypothesis-making, which is the most creative part of science.

Karl Popper was very ambiguous, but mostly negative, about it. While other philosophers, like Peirce, defended it. Peirce had a name for it abductive reasoning

Which is one of the approaches to creativity I was attempting to use in my own research. Here, I just mixed it up with the basic ideas of the "embodied" cognitive science movement :D

I really enjoyed that thread! Thank you for sharing Mathieu Lalonde

Hi Kelvin. Here is the simplest way I can put it: Would you be able to teach whatever you learn? In fact. Here's the practical suggestion: Do teach whatever you learn. Perhaps in blog-format! Even better if you infuse it with what you can uniquely offer.

That is precisely what I am doing with this blog. I am new-ish to software development. But I come from a non-cs academic background, so I decided to share my learning journey along with the things I know from outside the software world.

But let me elaborate a little.

There are only two things of real substance that I suggested

1. Reframing knowledge. From a theoretical "having information", into a pragmatic "be able to explain and build stuff".

But with a small twist.

1. Focus on the "why" and the relations between things or ideas. Not so much on the individual ideas themselves.

You can always find a tutorial about making a React app. And you would be able to make a react app. And that's pretty much it.

But after all that effort how would you answer when someone asks you why would you want to use react over vue? why not svelte? why redux over useContext? For example. (I am foolishly assuming you know about react)

If you start with why react exists? (and take a brief history lesson), you are in a much better place than many. why use hooks? why choose functional components?

If your goal is being able to build react apps, having an answer to at least some of those questions will make it much easier to find the answer to any technical questions you may have.

The reason is as simple as it gets. Because all the technical decisions that where made when creating react where made for the purpose of solving a problem. They were not arbitrary (or at least not completely arbitrary).

It is much easier to remember lone technical facts if you have their context than otherwise. Every single aspect of react's api and jsx syntax is there for whatever purpose the people that made it needed it to satisfy.

In a nutshell. Start with "why X" and go all the way to "How X". Instead of starting with "how".

Hopefully that helps :D

Thanks for the kind words Roshaan

Please let me know how it goes!