How To Master Programming technique That Changed My Life forever?

 “Everyone in this country should learn to program a computer, because it teaches you to think.” — Steve Jobs

How to Master Programming?



You've probably wondering what what it means to think like a coder. And how do you go about doing it?

It all simply refers to a more efficient approach to problem solving.

My purpose in this piece is to teach you how to do it that way.

You'll know exactly what measures to follow to become a better problem-solver at the end of it.


Why is this important to learn Programming?


The meta-skill is problem solving.

We're all dealing with issues. Both large and small. The way we deal with them can be a little...awkward at times.

Unless you have a system in place, this is likely how you "fix" problems (like I did when I first started coding):

  • Make an attempt at a solution.
  • If that doesn't work, try an other approach.
  • If that doesn't work, go back to step 2 and try again until you get lucky.

Look, you never know when you'll get lucky. But that is the most ineffective method of problem-solving! It's also a complete waste of time.

The most effective method entails a) developing a framework and b) putting it into practise.

So, what should you do if you run into a new programming problem?

The steps are as follows:

1. Observe

Make sure you understand the question. The majority of difficult situations are difficult because you don't comprehend them (hence why this is the first step).

How do you know when you've grasped a problem? When you're able to express things in simple terms.

Do you recall being stuck on a subject, starting to describe it, and immediately seeing gaps in the reasoning that you hadn't noticed before?

This is a common experience among programmers.

2. Make a strategy

If you don't have a plan, you won't be able to solve the problem (and somehow hope you can muddle your way through). Make a strategy for your solution!

Nothing will be able to assist you if you are unable to write down the specific instructions.

This indicates that you shouldn't start hacking right away in programming. Allow your brain to assimilate the information and examine the problem.

Answer this question to acquire a solid plan: “Given input X, what are the steps required to return output Y?”


3. Make a division

Keep your eyes peeled. This is the most crucial phase of them all.

Do not attempt to address a single large problem. You're going to cry.

Instead, split it down into smaller chunks. These sub-problems are a lot less difficult to solve.

Then, one by one, solve each sub-problem. Start with the most basic. Simplest implies that you already know the solution (or are closer to that answer).

After then, the term "simplest" refers to the fact that the solution of one sub-problem is independent of the solution of others.

Connect the dots when you've solved each sub-problem.


4. Are you stuck?

You're probably thinking to yourself, "Hey ... That's great, but what if I get stuck and can't even solve a sub-problem?

To begin, take a few deep breaths. Second, that's reasonable.

But don't be concerned, pal. This is something that happens to everyone!

The distinction is that the finest programmers/problem solvers are more fascinated than upset by bugs/errors.

In reality, here are three things to attempt when you're dealing with a bad situation:

Debug: Go over your solution step by step to see where you went wrong. This is referred to as debugging by programmers (in fact, this is all a debugger does).