3 reasons why you fail in new technologies
Tags: career, learning, coding, motivation
Published: 2019-03-22 06:44:27

---
title: 3 reasons why you fail in new technologies
published: true
description: 
tags: career,learning,coding,motivation 
cover_image: https://thepracticaldev.s3.amazonaws.com/i/lm7duhn7ebcqjllgz8vh.jpg
---

Developers write code, designers draw interfaces, architects plan buildings, engineers build things. All kinds of specialists do different kinds of things. But what action is common for them all?

This action is called **Learning.** Learning is an obligatory stage of every job you need to perform. But to actually learn things you need to learn how to learn.

Usually, to start our jobs we spend approx 10-18 years on learning things (school, college, master degree, etc). But in fact, this approach may mislead us in the future.

<center>**Meet Peter. Peter is a back-end web developer.**</center>
<img alt="Meet Peter Developer" src="https://thepracticaldev.s3.amazonaws.com/i/0s7fg53bl3flcnwev42j.jpeg" width="600"/>

He writes code in Python and is good at Math and data structures. He likes exploring new technologies and wants to extend his development stack. Recently Peter started to show interest in Machine Learning (ML). He is captivated by some new popular projects that were built using ML. He definitely decides to start learning it. As his day-to-day job does not require ML, he comes up with an abstract idea of building some side-project.

Peter has a plan. It looks pretty good for him: 
1. Download (or buy) a couple of top-rated books on the topic. Read them.
2. Register at Coursera/Udemy/Lynda/etc. Sign up for a course on the topic. Finish it. Get a certificate.
3. Watch a series of Youtube lectures on the topic. Full 160 hours.
4. Sketch up a ML project idea. 
5. Develop a project on GitHub
6. Enjoy!

For Peter the expectation of achieving the goal to finish a ML project looks like this:

![learning and then doing](https://thepracticaldev.s3.amazonaws.com/i/n8c3t0ghwj4ur66ocgwo.png)

Nothing can go wrong, right? 

![right?](https://thepracticaldev.s3.amazonaws.com/i/ehn1j6judqhcg88orz7x.gif)

Of course, not! 
In real crucial life what Peter got looks like this:

![long learning and no doing](https://thepracticaldev.s3.amazonaws.com/i/3oiqa3ze0mv8ulzdkmb4.png)

Familiar, right? 
But why it happened in such a way? 

There are at least several reasons for it:

1. Peter is used to doing it like this.<br>
    From early childhood, he was always taught to do it this way by our school, university, relatives, and friends. Paradigm of "first long learning - only then doing" was given for him as the only possible.
![learning](https://thepracticaldev.s3.amazonaws.com/i/wkzav8fjgbzwzxlg68ts.gif)

2. Fear of new knowledge.<br>
   Plunging into all this new knowledge, Peter realizes how much he does not know yet and how long the learning path is gonna be. Understanding this does not motivate Peter at all.
![fear of knowledge](https://thepracticaldev.s3.amazonaws.com/i/e44wmqkuwj6jw5jqjn62.gif)

3. Learning in advance does not work.<br>
   One can not absorb tons of new theory knowledge for several months and then just start using this in practice. Learning doesn't work like this. Knowledge requires consolidation and immediate application.
![rocko's knowledge](https://thepracticaldev.s3.amazonaws.com/i/icy51o6uew9of7u0rr0j.gif)

But, what Peter can do?

Cutting a long story short, Peter just needs to immediately start doing things without spending lot of time on learning. Both *learning* and *doing* processes should be divided into small pieces and combined into a whole process that will give Peter the desired result.
Peter needs to do the paradigm switch:

<center>"*First Learning And Then  Doing*"
→
"*Doing by Learning And Learning By Doing*":</center>

![learning by doing](https://thepracticaldev.s3.amazonaws.com/i/blfuufp3yclsonmi5wup.png)

<br>
Achieving "Doing By Learning And Learning By Doing" is not a simple thing by itself too. I've built several rules and concepts for this, and I'd like to share them with you in the next article.
<br><br>