Summary Before I get into this article, I would like to sum it up and not waste your time: Find your own way, and find it slowly I realize this goes against the barrage of marketing for paid courses, books, and boot camps that want you to believe that you can learn a new trade in a week (or even less!). This is of course my own experience. I began my journey in 2004 when Doom 3 was the benchmark for all new graphics cards. I have noticed that as well as the number of resources being a lot more abundant as years went on: so has the commodification of these resources. Free Materials & Teachers There are a lot of free resources out there. Starting with the library (as we didn’t have broadband initially) and then onto many free tutorial websites. There are some great paid resources as well as bad free resources, and vice versa. However, I think its wise to bear in mind the author’s intent for creating these resources. A free resource might be an authentic effort to impart knowledge, shameless self-promotion or even both! A savvy seller of courses is intent on selling courses, for example. His interest is going to be on after selling you , selling you . If you not confident without his resources, but believe he can help you if you spend enough money - then he has successfully locked you into his brand. part one part two To summarise: Avoid spending money when you don’t know what to spend money on yet. You will use a myriad of different resources on your path. I would be very suspicious of any single resource or person claiming to hold all the answers - as you are not talking to a teacher, but a salesman at that point. Basic Programming Principles My own path was not a straight road. It was an overgrown hedge maze. I used a myriad of different resources over my journey to wrap my head around the most basic of programming fundamentals including: Books - be they borrowed, bought or still yet to be returned to the library A bodacious amount of Search Engine queries Unsolicited advice from chatrooms I learned a surprising amount from chatting to (self proclaimed) IT professionals over various games and chatrooms. Some of these connections even landed me a free FTP Server account to learn my trade without any ads. Some of the games even had internal scripting languages and map editors. It was these tools that I really started investing a lot of time in, and without even knowing it at the time was where I cut my teeth on the fundamentals of programming. Making simple teleports and eventually even more complicated scripts was where I gained a lot of experience using loops, conditional branches and of course gained lots of experience debugging the many bugs I myself added. So to summarise: Learn your fundamental programming principles via whatever engages you in an enjoyable way To elaborate further on this point; I believe it is essential that you initially enjoy working with the code and projects you using to learn basic principles. You need to write a lot of bad code. You need to make lots of mistakes. A boot camp or crash course will let you what to do, but you won’t why you are doing it. You’ll be a monkey copying another monkey. know understand Self Reliance When things go wrong. I mean really wrong (people start shouting and crying) you’ll find that you only have yourself to solve the problem. Google is indifferent to your particular issue. Your colleagues are too busy preserving their own livelihoods to get burnt by your garbage fire. Some people fall apart during these times. I’ve seen developers with university educations behind them, thousands of pounds of courses and resources throw their hands up saying “I don’t know”. However when it comes to sticking your hands inside the hot mess of a codebase someone else has written, and then promptly fled to another company, you need to to have had the chops developed to and . work it out get it done These skillsets of: debugging code. recognizing different coding styles (not taught in any course, but rife in business). keeping yourself going (making sure you are getting enough sleep and the right food to keep your concentration going under weeks of long hours and pressure) These are just some of the essential assets you need to embody to really be of any use in the industry. But You’ve not pasted in a single code snippet yet The point I am trying to make is that it does not matter what language you start in, or what methods you use to get started. A developer is not defined by their syntax, IDE, or even their internal ideologies and philosophy. Its all the above and more combined. The sum is greater than its parts. “You are what you repeatedly do” - Aristotle To get started you need to get started. It doesn’t matter where you start, just start somewhere that is at least enjoyable or interesting to yourself. Get used to this feeling of not knowing and having to go out and teach yourself from scratch. Conclusion Please don’t part with your money, especially if you don’t have a lot to begin with. Only you can teach yourself, no one has the answers. Start now and start learning from your mistakes. Finally . The more you know the more you know you don’t know. Get used to this feeling of not knowing what you are doing If you want a quick and dirty roadmap of what specific languages you should start with then I have another article . here

Google

2022 - HackerNoon Contributor of the Year - Game Development

2022 - HackerNoon Contributor of the Year - Philosophy

2022 - HackerNoon Contributor of the Year - Self Improvement

clintveasey.co.uk

Nominated for 2022 - HackerNoon Contributor of the Year - Philosophy

Nominated for 2022 - HackerNoon Contributor of the Year - Game Development

Nominated for 2022 - HackerNoon Contributor of the Year - Self Improvement

Full Stack Web Developer

Too Long; Didn't Read

In your car, at home, or at work — Bosch technology shapes many areas of life.

Web Development: Teach yourself to Teach Yourself

Web Development: Teach yourself to Teach Yourself

Too Long; Didn't Read

People Mentioned

Company Mentioned

Clint Veasey

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

Web Development: Teach yourself to Teach Yourself

Too Long; Didn't Read

People Mentioned

Company Mentioned

Clint Veasey

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES