[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance

Search:


View post   

>> No.23789378 [View]
File: 291 KB, 569x469, Untitled-1.png [View same] [iqdb] [saucenao] [google]
23789378

>>23788928
>>23788950
This guy is a loser who is shit at coding because he went to college. Don't listen to him.
Self Taught Programming:
>Step 1. Get better at math
A lot of programming boils down to math. If you want to get paid big bucks, you'll need to know more than basic algebra. If you're bad at math, and don't feel the drive to improve, you'll never be a high paid software engineer.
>Step 2. The beginning
You'll obviously need some sort of "intro" class. For me, this was youtube and months of free time during middle school. For you, this could be a paid coding bootcamp or such.
>Step 3. Your own projects
Look, these bootcamps will only teach you so much. Their "projects" are really linear in progressing you. What you need is a *lot* of small projects. You need to ENJOY doing these small stupid projects just for the challenge. This is ENTIRELY how you improve as a software engineer. You go "Oh this is stupid but it may be a fun challenge" and complete that task. For me, this was almost entirely making cheats for videogames. I am a good software engineer today because I wanted to be a good cheat developer back in the day. Other things I've done for shits and giggles includes: remaking minesweeper, making a blackjack game, creating my own screenshot tool like Lightshot.
>Step 4. Networking
Without an actual degree, you'll find it extremely challenging to get your resume onto people's desks. Your side projects from step 3 will help buff out your resume and get the employer interested, but first, you gotta get there. By making cheats, I met tons of smart dudes and they got great jobs. They knew I was smart and came to me asking if I wanted to apply for jobs that opened in their departments.
>In conclusion
This is essentially the way I did it. Not for everyone, but you'll learn a completely different way to software engineering. I still do side projects in new languages and with new technology for fun
>t. Tesla Software Engineer

Navigation
View posts[+24][+48][+96]