Your Coding Teacher

Coding 24/7 mentality is overrated, Coding 4 hours/day with intese focus is underrated.

This is how you get a salary of $0k this year: Don't learn to code.

Being able to adapt to any environment is the mark of a true programming master

"In what programming language is this awesome app written?" Said no paying customer ever. Focus on what matters.

Frontend dev: Hello World! Backend dev: Hello Server Fullstack dev: Hello StackOverflow...

"How do I stay motivated all the time?" You don't need to stay motivated all the time. Don't rely on motivation. Rely on discipline.

Signs of a BAD programmer: - Arrogance - Lack of empathy - Lack of patience - Doesn't learn from mistakes - Uses the same language for every task

Reading other's people code is free. Writing code is free. You are losing a lot of money and opportunities for being lazy.

Make this year the year where you finally move past "Hello World!".

30 minutes of coding will do more for your programming skills and bank account than 30 minutes of watching tutorials.

The best programmers I've worked with always start with a requirements.txt first.

Dumb programming myth #4155: "You have to be a genius to become a programmer"

You: "It is important to write readable code" Also you: "main(_){_^448&&main(-~_);putchar(--_%64?32|-~7[__TIME__-_/8%8][">'txiZ^(~z?"-48]>>";;;====~$::199"[_*2&8|_/64]/(_&2?1:8)%8&1:10);} "

Broke: "I want to learn to code" Woke: "I will learn to code" Bespoke: "I learned to code, just waiting for time to catch up"

The same way musicians practice scales, you should have some exercises to get you up to speed. For example, when I learn a new language, I make sure I implement some algorithms (that I already know) that cover the basics: - Tree traversals - BFS - Mergesort - Etc

"The theory behind open source is simple. In the case of an operating system, the source code is free. Anyone can improve it, change it, exploit it. But those improvements, changes, and exploitations have to be made freely available." - Linus Torvalds

You learn more from "unexpected results" than from getting things right the first time

If you're overwhelmed by some big complex problem, break it down into small chunks. Focus on each of them individually and then build up your solution. Divide and conquer.

If your bug has a one in a million chance of happening, it'll happen next Friday

Design patterns in 1 tweet Observer: A publisher notifies a list of subscribers of changes in a class Ex: People who receive their monthly subscriptions (subscribers/observers) from their favourite maganizes (publishers)