The 8-step quick-start guide to learn Machine Learning.

🧵👇

I learned enough AI/ML in 12 months to change my life forever.

You can do the same, and it all starts with a killer process to learn new things.

You can steal my approach. Every detail on the latest issue of my newsletter: https://t.co/9gaenLByFb.

Make it work for you.

10 machine learning questions you should be able to answer.

I started experimenting with a questionnaire before interviewing candidates. Applicants submit a video or written answers to apply for the position.

Thread: Let's look at 10 of these questions.

The questionnaire solves a couple of problems:

1. Weeds out candidates that aren't ready for the job.

2. It significantly cuts down the time we spend talking synchronously.

One problem: It requires extra time from the candidate before the phone interview.

Here are some numbers on a job posting before using the questionnaire:

• 249 applicants
• 13 good applications

That's only 5%.

This sucks.

Numbers after using the questionnaire:

• 44 applicants
• 21 good applications

That's 47%.

This is much better.

I look at it this way:

Sooner or later, I'll ask these questions, and the candidate will have to answer them.

I'd rather give them space and the opportunity to think about their answers without any pressure.

Those who can't or don't want to answer won't apply. That's fine.

I told everyone that I didn't care.

"Screw math! I've never been great with it, so I'm not starting with machine learning to fail at the end."

That was many years ago.

Math is still hard, but I don't think you should be scared at all. Here is why: 🧵👇

[1] One thing changed my mind: school pushed me to the deep end of the pool, and I was forced to swim.

I had to face my fears, and I started machine learning and realized that the math involved is not as scary (or as much) as some people believe.

👇

[2] Probably one of the most frequent questions I get is around the math needed for machine learning.

Answer:

▫️ Probabilities and Statistics
▫️ Linear Algebra
▫️ Calculus

But it turns out that this is not helpful.

👇

[3] What are you gonna do with this?

Are you going to learn all there's is about linear algebra before looking into machine learning?

How about probabilities and statistics? Or calculus? Do you know how extensive calculus is?

👇

[4] Many people stop looking into machine learning as soon as somebody tells them that calculus is a pre-requisite.

First of all, the amount of calculus you truly need is minuscule.

Second, without proper direction, there's no way you'll find your way through the noise.

👇

I sat next to one of the smartest, most successful software engineers in the country for over 10 years.

Here's what I learned.

Fast is 10 times better than good.

9 out of 10 times, a "good enough" solution is all you need to unlock time, money, and attention.

Focus relentlessly on being first. Then take the time to be right.

Fast, then right.

Ship more frequently.

The faster you show your work to your users, the faster you'll hear their feedback, you'll adapt, and you'll ship again.

A question you should ask every day:

What can I do to ship this one day before planned?

Technical debt is a good thing.

Everyone hates technical debt. I think they don't know how to take advantage of it.

When used appropriately, technical debt means working on what truly matters and deferring anything that can wait.

No debt ⟶ You waited too long.

Ask, don't think.

People burn their time every day instead of asking for help.

You don't get extra points for working harder, especially when a little help will make you faster.

Time is your most valuable resource. Don't waste it.

Many machine learning courses that target developers want you to start with algebra, calculus, probabilities, ML theory, and only then—if you haven't quit already—you may see some code.

I want you to know there's another way.

↓

2. For me, there's no substitute to seeing things working, trying them out myself, hitting a wall, fixing them, seeing the results.

A hands-on approach engages me in a way pages of theory never will.

And I know many of you reading this are wired just like me.

3. I feel that driving a car is a good analogy.

While understanding some basics are necessary to start driving, you don't need to read the entire manual before jumping behind the wheel.

As long as you practice in empty parking lots and backroads, you'll be fine.

4. As you make your way to public roads, you can start incorporating more of the theory that will help you stay safe.

At this point, that theory won't be lost on you: your hours behind the wheel will help you make the necessary connections.

Things will start clicking quick.

5. I've talked to people struggling with derivatives that have no idea why or when they'll become helpful.

I've seen others memorizing what eigenvectors are, or manually transposing matrices because "that's what it takes."

Honestly, for the most part, it's not.

11 key concepts of Machine Learning.

— Supervised Learning Edition —

🧵👇

😜

Before starting, remember that, if you follow me, one of your enemies will be immediately destroyed (and you'll get to read more of these threads, of course.)

And if you don't follow me, well, you just hurt my feelings.

😜

1. Labels

(Also referred to as "y")

The label is the piece of information that we are predicting.

For example:

- the animal that's shown in a picture
- the price of a house
- whether a message is spam or not

👇

2. Features

(Also referred to as "x")

These are the input variables to our problem. We use these features to predict the "label."

For example:

- pixels of a picture
- number of bedrooms of a house
- square footage of a house

👇

3. Samples

(This is also known as "examples.")

A sample is a particular instance of data (features or "x.") It could be "labeled" or "unlabeled."

👇

Are you planning to learn to Python for machine learning this year?

Here's everything you need to get started.
🧵👇

In this thread we'll look at all the concepts in Python you need to know for machine learning along with free resources to help you out.

All of this is based on my experience of successfully teaching 300+ students how to code using Python.

(2 / 19

You can use many languages for machine learning, why Python?

Because of 2 reasons:
- Comparatively easier to learn than other languages
- Has the biggest and most mature community

This makes Python a no-brainer to learn for machine learning as a beginner.

(3 / 19)

These are the absolute basics which you must know about:

- Basic terminal commands
- Basic arithmetic (+,-,/,*)
- Accepting user input
- For & While loops
- Exception handling
- If-Else statements
- Functions, modules & Imports

(4 / 19)

Then comes the more tougher concepts which you must know about:

- Object oriented programming in Python:Classes, Objects, Methods
- PIP (Pypi)
- List slicing
- String formatting
- Dictionaries & Tuples
- Managing environments
- Dunder methods like __init__

(5 / 19)

Thread for beginners; How to learn machine learning.

Let’s start with something really simple and useful not just for Machine Learning.

Start with a Python library called pandas. It’s a huge library but it's mostly fun for traders because it's kind of rewarding to learn each function and how it gonna affect the way you handle the financial data.

Then learn some basic stuff about Python library called NumPy. Pandas is built on NumPy. Numpy is huge, you just need to understand some basic NumPy functions like NumPy shapes and NumPy arrays

If you understand pandas then you will understand NumPy arrays and shapes easily. Side note: Numpy shapes gonna play an important part in the deep learning model called LSTM - mainly used for time-series analysis(such as financial data) and Natural Language Processing (NLP)

I've applied for a total of 10 development jobs in my life:

- 7 lead to interviews
- Of those 7, 4 was a good fit for me
- Of those 4, 3 offered me the job
- In all 3 cases, I negotiated a better deal

🧵 on what worked for me and what YOU can do to get similar results 👇

1. Apply for the RIGHT jobs. Look for midsize to large companies, not necessarily tech related. These tend to get way fewer applications than traditional tech companies, so it's easier to get your foot in the door - and they also tend to be great environments for learning.

2. Spend time on your application. Make sure your resumé and written application is tailored to the exact position. Recruiters or hiring managers can smell a copy/pasted resumé from miles away. Use as many words from the job spec in your application as possible.

3. Have a portfolio. Show off your skills and some personality on your website. This is a nobrainer for front-end devs, but it's true for other areas too. It's a great way to stand out over other candidates by actually *showing* the value you can create and your experience.

4. Establish personal contact. Send a quick message or make a phone call before applying. Just introduce yourself to the person in charge of hiring and ask a simple question. It's the best way I find to make them remember your application when you submit it.