You don't understand, you just grasp it

You think you understand the subject, but you’re not able to design a project from a blank page; specifying the problem, the objective, and the specific programming resources.

Then you don’t understand. You just grasp it, if that.

You won’t be able to trust your skills to work on real projects.

If you’re an employee, you don’t contribute because you don’t know how to design solutions. You just talk about them: charlatan.

If you’re a boss, of yourself or in a company, you run the risk of wasting resources or being fooled because you don’t know how to design solutions, nor distinguish who knows from who doesn’t.

You can’t count on yourself, nor can others count on you.

For example, imagine you have a company that sells car insurance.

How do you design a programming project that helps your company?

Key questions before doing anything.

Market questions:

• What is the project’s objective?
• Who will use it?
• How will they use it?

Web calculator project to offer personalized car insurance with Machine Learning and Artificial Intelligence algorithms.

Technical development questions:

• How would you design the project phases?
• What programming resources do you need?

Let’s reflect on your understanding and technical development capacity.

If you don’t understand programming resources, you won’t know how to design the project phases and you’ll fool yourself. Or worse, others will fool you.

What does it mean to understand?

If you’re able to outline the project with specific programming resources without Internet help, congratulations: you understand programming resources.

Whether you’re entrepreneuring, or working in a company, with a group of people: you contribute.

Otherwise: you subtract.

You stay quiet because they don’t know what they’re talking about.

And if you try to contribute, you run the risk of being a charlatan.

You don’t have practical perspective, but theoretical.

You think you know because you once took a course where you copied, pasted, and executed. Since the result came out, you assumed you already understood.

But you don’t understand. You just grasp it.

Better to count on another person to implement the project.

So, how do you come to understand?

Implementing practical solutions.

Applying theory in new practical cases.

How can I help you understand?

By guiding you.

I’ve designed the materials specifically so that you implement the theory in new practical cases and thus come to understand, not just grasp.

I won’t just tell you what you have to do, but you’ll work on them live while I watch you to make sure you reach the goal and don’t deviate along the way.

On time and in form. Without frustrations. Enjoying the journey.

When you finish the programming project, you’ll know how to outline it because you implemented it yourself.

Imagine what new paths will open before you because now you do contribute.

They count on you in a company. You count on yourself in your venture.

For more information, contact us.