Machine Learning for the Web developer in 2021.

The beginner's guide.​

🧵👇

Are you planning to learn 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)

Everything you need to know about the math for machine learning as a beginner.

🧵👇

Before diving into the math, I suggest first having solid programming skills.

For example👇

(2 / 17)

In Python, these are the concepts which you must know:

- Object oriented programming in Python : Classes, Objects, Methods
- List slicing
- String formatting
- Dictionaries & Tuples
- Basic terminal commands
- Exception handling

(3 / 17)

If you want to learn python, these courses are freecodecamp could be of help to you.

🔗Basics: youtube .com/watch?v=rfscVS0vtbw
🔗Intermediate :youtube .com/watch?v=HGOBQPFzWKo

(4 / 17)

You need to have really strong fundamentals in programming, because machine learning involves a lot of it.

It is 100% compulsory.

(5 / 17)

A git cheat sheet for all your needs!

https://t.co/H7QdOrthwV

Here's what you'll hear when you first get into machine learning.

- Neural networks
- Loss
- Weights
- Biases
- Epochs
- Neurons
- Optimizers
...

It can get very confusing really fast!

Here are some of the terms you should know about.
(I wish I had this before)

🧵👇

These terms won't mean anything unless you know what Machine learning is all about.

> Machine learning is the process of making a program which allows a computer to learn from data.

The data could be anything, images, audio or even text.

In machine learning we use something called a neural network, this is essentially an imitation of the human brain.

> Neural Networks are a digital imitation of the neurons you see in the human brain.

In these neural networks, data flows through them and each neuron (the circle) has a numerical value which will change.

> The value of a neuron gets changes to something which is close to what we want each time the data passes through the neural network.

Think of the neurons as dials on a lock, you have to tune every dial to open the lock.

It is almost impossible for a human to tune thousands of dials like these, but a computer certainly can.

These are the tools you will need for machine learning in Python.

🧵👇

Anaconda

When you work in python, you'll be working with several frameworks and many of them work only on specific versions of python.

(2 / 13)

Now imagine downloading a new version of python and then installing it for every framework you want to work with 😬.

Meet Anaconda which allows you to run several versions of python. It comes pre-installed with several data science and machine learning frameworks.

(3 / 13)

Pip-env is also a way of maintaining several versions of Python and comes pre installed with Python.
You can use pip env or Anaconda, whichever works for you.

(4 / 13)

Jupyter Notebooks

Jupyter notebooks is an IDE just like VS code or Sublime. The special thing about jupyter is that you can parts of code in mini code editors called cells. This is great for prototyping and testing code.

(5 / 13)

Okay, doing my first baby steps with r2frida (which combines the power of @radareorg and @fridadotre).

Gonna share my progress in this thread (live, so keep calm).

The goal: Runtime inspection of data sent out by TikTok !!before!! it gets encrypted

1/many

First of all, we do not start from zero. I got some prior knowledge from past reversing attempts and want to share some important facts.

TikTok's (log data) encryption is accomplished by a native library. The Android Java code just serves as proxy function to the native function

The decompiled code for the respective native JNI function of an older TikTok version looks something like this, but in this example I use the most current TT version (no statical analysis done, yet)

In case you never reversed native libraries which were build to interface with Android Java layer via JNI, I highly suggest the entry level introduction on the topic by @maddiestone

Before we start, I want to pinpoint some important aspects (which are also covered by Maddie's videos).

1) Unlike raw C-functions, JNI functions like the one showcased above, receive pointers to complex Java objects .

F.e. a function receiving a String on the Java layer...

1/ It's probably not the first thing you think of, but when we started .NET (COM+) in the late 90s, C# didn't exist yet. We were working on it at the same time as the CLR and the framework. So, you might wonder, what language was being used to generate IL and write the BCL?

2/ The answer is a language that we called SMC that Peter Kukol wrote the compiler for. Peter is a flat out amazing engineer and wrote the core parts of the compiler in just a few days. This unblocked the framework team, allowed vetting the runtime and interpreter, etc.

3/ SMC was a trimmed down C++ variant and the compiler was written in itself (i.e. SMC). It didn't support things like destructors, multiple inheritance, virtual base classes, etc. But, overall it enabled progress that would have otherwise been stalled.

4/ It did introduce a problem for the C# language and compiler team though. Every day more and more code was written in SMC, a language that we did not intend to ship externally. Designing a new language is hard (well, at least, a general purpose one that becomes popular).

5/ So there was a constant balancing act between laying enough of the foundation of the language and the C# compiler to replace SMC and making sure that the design lived up to the goals and ideals the team was striving for. If we waited too long to adopt C#,

The "polarization is the problem" narrative to me is bad because it implies the status quo was a stable and acceptable set of trade-offs. It's the equivalent of a pollyanna "why can't we all get along" but the we in question is white supremacy and its targets.

like i understand that conflict mediation requires mutual concessions (i did my MA in conflict studies) and while it's important to meet people's deep needs across spectrums of difference, certain things are just not up for negotiation.

Also while peacebuilding work is good. It's not just "seeing each other as human" it's literally about transforming structural issues. (hence Galtung's distinction between positive and negative peace wherin negative peace is like a ceasefire and positive is a transformed society.

And I think that to whatever extent that kind of peacebuilding work is applicable, it's not between fascists and people who think fascists are bad. Fascists are not invited. They are only invited if they seize territories and can't be crushed. Then secret negotiations.

The US is always like "we don't negotiate with terrorists" but literally every president negotiates with who they consider to be terrorists. It's all just down low. But that's just because counter-insurgency failed.

In this thread, I will tell you how to learn python for data science in 1 hour 👇 1/N

It's not possible 2/N

It's not possible 3/N

It's not possible 4/N

It's not possible 5/N