"Junior/Mid/Senior" titles are usually bs. The same person can be a mid level dev in company A and a senior developer in company B Remember this next time you believe you shouldn't apply for that job.
Shaw’s Principle: Build a system that even a fool can use, and only a fool will want to use it.
When you are learning programming, it looks like nothing makes sense until suddenly everything starts making sense Remember this the next time you want to quit because "you just don't get it"
This is the only time in history where you can learn the skills you need to get a 6 figure job from the comfort of your house.
Think about this The best developer you know And the richest developer you know Are not the same person
Getting started with programing is 10000 much more important that "what language do I learn first?"
I have 2 moods: 1. I'm a badass developer 2. I can't code to save my life
If you can't realize when good enough is good enough, are you a good programmer?
If you are unwilling to pay $30 bucks for a book to learn a skill that can make you 6 figures, Are you really going to put the time it takes to learn that skill, even if you get the book for free?
Focus on ONE THING AT A TIME: - A technology, not 5. Ex: first HTML, then CSS, then JavaScript, then ... - 1 language, not 7 - A fundamental concept (functions, classes, loops) - A paradigm (OOP, procedural) Then, focus on COMBINING them to build applications
Writing code to make your colleagues think how brilliant you are is the stupidest mistake a programmer can make.
Remember: You don't always need a database. Sometimes files are enough.