Somewhat related but it is amazing how clear things become to me when I draw a diagram about something I have to learn or build. Make visual connections leads to an immediate deeper understanding. It has become second nature for me to start up my diagramming app the moment I don't understand something
Another "been there, done that". If I could give advice to my 30 year old self, without doubt, it'll be: #1. Focus on finding the right job that works for you and pays the bills. Once you are back to feeling good start a side project.
Chasing the "dream" of having my own business without realising what that actually requires. Then when it got difficult or boring, the next freelancing job is so much easier (and way more lucrative). Back and forth with spending savings on projects that never amounted to anything.
Slowly realised that nowadays, for us techies, there's a much better way of having a good life. Just find the right job (look long and hard), get paid well, hone your skills. I wasted a lot of time.
I could have written this exactly - lived it. Combine that with the crappy economy of 10-12 years ago, vomit.
Kids, you think you're dreaming now. Just imagine how much you'll be regretting later. Just quit your job, take some time traveling then go find another job. You'll feel better eventually.
This reflects badly on the developer who posted this. Though it is easy to sympathise, this is not professional behaviour. Learn from mistakes and move on focussing on finding good clients.
This route exists, it's called training and you can earn even more doing that. Absolutely doable, but it's a long road to get there (salary- and lifestyle wise).
You could use this as an opportunity to show you are capable to handle anything that is thrown at you. This is a highly valuable skill, way more valuable than your current tech stack. For you personally and the company hiring you.
After you have proven your value then talk to your boss. If things don't change, move on. Surely you'll find something better.
Forget puzzles! Solve a real problem with code. Read only as little as necessary and then build something you care about. Before you know it you have become a programmer.
Rather this:
> Code is secondary. People are first
This is easily overlooked. Your social skills matter most. Leading, listening, communication. Most problems are people problems.