Ir al contenido principal

Learning different subjects requires different sources

Hello peers on Wisdom,

This week I came across the idea of optimizing study time across different subjects, frameworks, languages, methodologies, algorithms, and fundamental concepts.

My first reaction when learning something new has always been to go straight to YouTube and search for a tutorial. It certainly has great advantages, such as:

  • Animations: They make understanding easier.
  • Code examples: You can quickly grasp simple applications.
  • Comments section: Other users often enrich the video with insightful knowledge.

However, there are also disadvantages:

  • Not every explanation is of good quality.
  • Sometimes the video is an hour long, and you just want to know one specific thing.
  • The video ends without the author going deep enough into your questions.

Another tool I often use is AI chatbots. They are very helpful when you need a quick answer to a specific question. But the trade-off is: “This AI can make mistakes, so always verify the answers provided.”

A great middle ground, in my opinion, is blog tutorials. Why?

  • Code is highly accessible — just copy, paste, and compile.
  • Authors usually explain step by step.
  • If you’re looking for a specific concept, you can simply press Ctrl+F (or F3) and search.
  • Sometimes there’s also a comment section.

And the cons:

  • As with YouTube, not everyone is a great explainer.
  • As with AI, sometimes the author can unintentionally cause misunderstandings.

Takeaway Points: My Preferences

I would separate them by levels of complexity:

  • Simple concepts: For things like the syntax of a function or a concept I already know, I would just ask an AI.
  • Medium complexity: For learning the syntax of a new language or framework, or a set of related concepts, I would choose a blog tutorial or a book. Blog tutorials are great (example here )
  • High complexity: For learning a new paradigm, architecture, or knowledge structure that is complex and unfamiliar, I would start with YouTube to grasp the essentials. Once I’m familiar enough, I would move on to a book for deeper understanding.

— Alan



Comentarios

Entradas populares de este blog

I forced myself to read Rust code

 Hello peers in wisdom, One month ago I found myself reading The passionate programmer by Chad Flower, here the author gives valuable advises for building a strong career as a software engineer (is not easy by the way).One of his insights inspired me to write this brief blog to share with whoever read this. The more or less I learn this week.  As the title suggests, the advice is READ CODE. What kind of code? The good kind. So... after dedicating around 100 hours to read the Rust book and resolve some basic exercises   I felt prepared enough to tackle some real code. I decided to search in the popular section of crates.io, and I found serde, a rust library for data serialization/deserialization. After 5 minutes of cloning the project and reading I was completely lost. Are people who wrote this geniuses or did I just lose 100 hours of my life? Fortunately (or not) it was a mix of both. Anyway, the next day I am back at crate.io and this time I chose something less popular....

Applying DDD on pricing goods at supermarket

Hello peers in wisdom, I hope you had a wonderful week. Todays topic consist on exercising a non technical part of software. Domain-Driven Design DDD is a set of tools that makes easier to understand business experts and then translate their knowledge domain to our domain (software). I encourage you to learn more by reading and watching the resources I found useful, they are at the bottom of the post. Pricing goods The definition of the problem is on this  kata . The goal, basically, is think about functionalities, edge cases and implementation for pricing goods at a supermarket. Steps I followed     Event Storming . This method helped me to start defining what where the things I expected to happen in this system. In the image you can identify them by the salmon color. Its important to note that at the bottom right is defined the meaning of each box color.           Commands and actors . The next step was to ask who makes what . In this case ...

The Profitability of Knowledge: Learning for Use vs. Learning for Joy

Hello peers in wisdom, Today I bring to the table the next question. Is any knowledge profitable? Context I am a newbie back-end developer and recently I was studying a pair of low level programming concepts. While doing so, I asked myself "Am I really going to use this? If yes, when? if not... why?" That’s when I realized I was studying simply because it was entertaining.  Is that wasting my time? It could be... but what is the purpose of life? Isn't everything we do, in some sense, a waste of time ?  I will defined as an inefficient activity. The time my brain will retain the vivid image of those new pieces of information is very short, I am talking about one week max, after that just crumbs of knowledge and a memory of joy for learning something new will remain. It would be better if I applied that knowledge to something practical.... What is the alternative? Some time ago I read a post talking about learning just-in-time JIT. This approach brings numerous benefits t...