Sometimes, actually every time, I get confused about what I am doing. Is it the correct thing, or am I just diverted from the real thing I wanted?

You don't really know the answer to such things, but finding them is an adventure in itself.

So, the first post from me is about How I find the answers?

The Questions

First of all, where do the questions really come from? For me, it's EXPERIMENTS. I do a lot of them, and errors (don't ask). But the feeling of making the screen go from red to white is really satisfying. So, advice number 1:

Try to solve your errors by yourself. Just search, read, and explore. What's stopping you from reading unless you don't know how to...

The Process

Here comes the so-called procedure to find answers. Someone might wonder, I already told it in the above quote, but in reality, that is what to do? and the procedure is how to do.

Many people ask me what course to follow, which video to watch for a specific thing, etc. But the trick is, don't watch; just read. Read hints, and docs. When you watch or read a pre-made, nicely done tutorial, you tend to copy it, knowingly or unknowingly. Rather than this, if you know the basics, choose the #FROMSCRATCH way. Yep, if you don't know a thing about that topic, then just follow the video. I, myself, am still figuring out the solution for this case.

Yes, you are going to get frustrated, demotivated, or whatever the words are... But in the end, you will feel it.

Learn and code >>> Watch and code.

So first learn the thing before hitting the board, then again learn while hitting the board, and then build upon it. Rethink what you did, why you did it, and how you did "it".

The Method

When faced with a problem, the first instinct might be to search for a solution online. While this can be helpful, there's something more valuable in trying to solve it on your own first. Here’s my approach:

1. Read the Error Message: It might sound simple, but truly understanding what the error message is saying can save you a lot of time.

2. Break Down the Problem: Isolate the part of your code that’s causing the issue. Break it down into smaller, manageable pieces.

3. Research Smartly: Look for similar issues online, but avoid copying solutions blindly. Understand why something works or doesn’t.

4. Experiment: Don’t be afraid to try different approaches. Sometimes, the most unexpected solutions come from a bit of trial and error.

Debugging is like being a detective in a crime movie where you are also the murderer.

The Learning Curve

Watching tutorials and reading documentation are great ways to learn. However, the real magic happens when you apply what you’ve learned by building your own projects. This hands-on experience solidifies concepts in a way passive learning can’t.

Code is like clay; the more you mold it, the better you understand its properties.

The Answer

Maybe the last step. How do you find it? Well, in my case, I just don't. I think that there should be no end to curiosity, and a curious mind should never stop thinking. It's going too philosophical now.

Coding isn’t just about writing lines of code. It’s a mindset. It’s about being curious, asking questions, and never being satisfied with just the surface level. The more you dig, the more you discover.

Curiosity leads to discovery, and discovery leads to innovation. Keep that in mind every time you face a bug or an error.

This is going too philosophical...

So this is the end. Remember, every great coder was once a beginner who didn’t give up.

Keep coding. Keep growing. A gradient step at a time....

BTW, the title quote is from a curious mind on X. if you know him.