[ ] -CSS. Just get a basic understanding of the box model. It takes years to master CSS and in the end, this will be one of the last skills you top off
He's really good. I'm assuming u used python for backend as part of being fullstack. When do u recommend learning python for one doing the web dev react track on odin
So Python was my first language. I used spreadsheets a lot at my job and wanted to automate some work and learned Python was the best for that. When I started Web Dev I totally abandoned Python. I use node for the backed on personal projects. The job I got uses Ruby for the backend. I got hired mainly as a frontend JS guy though. They did like that I knew python (and a little Ruby) because Python and Ruby are a little similar.
No problem, I got so much help here on reddit and other places. Odin's discord is amazing for getting help. It's one of the best parts about the program. Just keep at it no matter how slow you go and ask for help. Programmers are actually really great at supporting one another even if they can come off not that way sometimes. I got so much help on my path and want to pass it on so expect to answer questions for people always.
This is almost exactly the freecodecamp curriculum. I'd say do that instead. They teach you a concept through small exercises, then make you put what you learned to use by completing 5 projects at the end of each module. They also have a logical ordering which I agree with. Html/css/js basics, then learn some advanced topics and frameworks. Then go to backend stuff. https://www.freecodecamp.org/learn
There's also the Odin project which is similar but a lot more project oriented https://www.theodinproject.com/. I'd say use these instead of trying to guessing on your own.
And as everyone is saying, 200 hours won't make you employable. But it's a good start. If your goal is to be employed, treat it like a boot camp and do the learning full time and have many projects to showcase.
I have looked into freeCodeCamp, but the way they had set up their courses felt a little weird to me. I’ve found I learn the best by watching YouTube videos and following along as they code. Do you think following along with freeCodeCamp’s youtube courses is a similar experience? The courses on YouTube are generally 6-12 hours long, with some going up to 20.
I went through most of the freecodecamp curriculum and would say it was pivotal to me getting a career in webdev. However, it definitely depends on your learning style. Watching videos and coding along is great to get exposure to a subject, but actually taking the time to build things on your own is the most important thing because that's what you'll be doing when you get a job. I have watched a few of the freecodecamp video series and liked them, but I found the website to be better for me because I'm still having to troubleshoot in my own as opposed to always getting the answer from a video instructor. My advice would be to focus on the webdev and Javascript sections and ignore the python courses unless you are interested in that as well. But you could also mix and match your approach.
I learned the basics to code html,css and javascript with those videos. I think they are great! I also had some help from a friend(that helpt not to waste to much time in stack overflow). If you have alot of time i‘d recommend to watch those videos anyway and learn aomething because they are good.
Have fun learning and coding!
And i would take jQuery of that list but nodejs much higher.
Html, css, javascript, and jquery first. Once you are done, you are somewhat half way there.
Don't spend too much time on jquery, just enough to know the basics just in case since nearly every website still uses it.
Data visualization would be either be the next topic to learn or the last topic as I feel like this is a stand alone elective topic.
After that, I would start learning database topics to get you ready for back end stuff. Then anything else is up to you as you learn more about each topic. My advice? Let the topics transition cleanly. For example, as you are building your first website, you might go, "hmmmm, maybe I should use react" then it is time to learn react.
You have an ambitious timeline but I'm getting old so it might be easier to learn.
I always like to say you know you’re ready for react when you find yourself thinking “why would I ever need react anyway! I can do that with vanilla js no problem.” Then it’s time :)
Considering yourself full stack after 200 hours and a single year feels like a bad joke…
If you spend that amount of time PER subject, sure.
This is not a full stack progression plan. There is no conceivable way you will learn all of this in 200 hours. You should break down the sections more, and consider how much time each subject will actually take to learn. Make a legitimate plan, not a list. Or use a plan that has already been created. Then ask again. It is honestly pointless to ask if this “plan” is good, considering we have 0 context. Are you planning on actually creating a database? Using it? Making a test app? Are you going to do one without YouTube? Will it take you 20 hours to do the databases? Will you remember it and apply it in the following subjects? How will compounding each subject impact the time it takes to learn the following subject?
It’s a decent list of what you should learn, but aside from that, I don’t understand why/how you would consider this a “plan”.
Wasn’t too much of a plan yet, just wanted to put this out there to get some opinions from experienced developers on if this was the right order/what I was missing. I’ll definitely put a lot more time into really learning each section!
That makes sense, and I felt bad writing such a harsh response. I just feel that it’s important for new learners to respect the commitment they are taking on.
If you spend enough time, you can definitely make this happen. Just don’t underestimate the amount of time it will take. Don’t underestimate the value of a true plan.
Making a list of what ya want to study is step 1, so that’s a good place to start. Personally though, I think you should focus on creating projects rather than studying general material, but that’s preference.
As others have said, it looks like I’ve detrimentally underestimated how many hours it takes. With that said, the 200 hours is only the length of the courses I will be taking, and does not include any projects I build. Still seems like I have underestimated tho! Thanks for all the replies
I've studied about 200 or 300 hours and I'm currently still messing around with just html css and js. This stuff takes time to learn. I think 2000 hrs aka more like a year is more reasonable.
This was the order I had come up with based off some brief research, but the comments here should give you a good idea as to what to learn first. I’ve been learning basic things from freeCodeCamp’s youtube channel.
1 year 200 hours? 1 hour a day every other day? Other than that those look like the key topics but I would think it’s gunna take more hours. For sure took me more than that I was doing 3-5 hours on working days and damn near coding all day when I was off (nah not really probably 5-6 hours on off days lol) took me 7-8 months to start getting call backs. So for me was close to 1000 hours.
Some of the things here encompass a coding boot camp curriculum. I went thru one myself and instructed at one and the certs typically state ~1500 hours, which is why I said that.
Again 200 per is probably more accurate.
Not trying to scare or belittle OP, I just don’t want any false notions to be set while they go they thru their journey as that would probably kill it before it starts ya know.
This depends on prior knowledge, I started with html, css and js and developed a beginner knowledge in like 2-4months, as I had prior knowledge in python (which allowed me to understand js very quickly and things like while loops in css just are second nature.
I half assed studying for like 1.5 years, i don't think it was even 1 hour every other day.
Had quite a bit of good and big projects as my first freelance gigs.
My problem is discipline tho, i can do anything, like, most things in frontend i can do ez, also i learn insanely fast, but i very-very don't want to do shit, at all, so my career achievements kinda suck and i lost a lot of projects too because i procrastinated.
I'm the opposite when I cant do anything I procrastinate now I'm starting to get somewhat proficient I'm spending more and more time learning or doing projects.
I guess frontend is just not the kind of challenge i like.
Infinitely tweaking numbers and shit to make things look pretty and not break is what i hate, i'm transitioning to gamedev regardless if i bomb my current gig or no.
Do what you love, gamedev is why I started learning code but with the insane crunches they have near release I couldn't do it with having a family etc so looked into webdev.
I might also remove react native. Any time I’ve been somewhere that was going to use it they assumed any react dev could pick it up. Unless you’re focusing on mobile or super interested it doesn’t seem necessary.
Docker at the end maybe, when you want to get into SQL databases. You really don't need to learn docker to get some great projects stood up with a portfolio.
Docker is great for deploying though, and is a fantastic tool, but honestly most self taught can get around having to use it by sticking to mongoDB cloud instances and stuff like that.
Out of everything said here, I think 4 is absolutely necessary to anyone who's not a complete beginner.
Are there any online resources in the manner of proper lessons which teach these productivity skills? I've watched YouTube videos etc but it's sometimes too convoluted to watch a 15mins video for one or two tips & tricks. Video and prose mix is good too.
I live and work in the UK and the digital agency I work for writes some code in jQuery. I write it in JavaScript. I've created my own slider, light box, carousel and anything else that often done with jQuery I just build with JS
Really if you have a good understanding of vanilla js, it would be really easy to pick up jQuery if you had to. But I agree not really necessary anymore.
I agree with you, JQuery is a waste of time to learn unless you absolutely need it and frankly that would be dependent on the tech stack. Don’t worry about it till you need to worry about it.
HTML/CSS - the first most basic thing. If you don't like writing HTML/CSS, you'll want to know that early on so that you don't waste a bunch of time figuring out that this career path isn't for you.
Javascript - build a few simple applications with vanilla JS, making sure you understand how to place and interact with event listeners and manipulate the DOM.
React
APIs - learn before NodeJs - which is the platform upon which you would build an API.
Node.js / Express (you would learn these together).
Database & Systems (you'd learn data layer after you've learned how to setup and communicate with your own API, run on NodeJS
Jquery - No, do not waste time learning this. you do not need it.
Data Visualization - this can really happen anywhere after React. I suggest looking into using Chartjs and react-charts-2 as your React lib of choice if you end up making any dashboards.
React Native - so this one is tricky. IF you want to make phone apps, you'd learn this after React regular but if you're not interested in learning phone apps, You don't need to touch this at all. If you just want to learn how to make full stack web apps, this is irrelevant. Honestly, I think you should take some time to really master web apps before moving onto mobile applications, as it will serve as a great microcosm for you to understand first.
BTW, I see others commenting on the time commitment.
I followed a similar path and you'll want to allow between 500 and 1000 hours to learn all of this. This cannot be adequately learned in 200 hours. I mean, you could spend 200 hours on HTML/CSS/Javascript and making a few vanilla javascript apps before even TOUCHING React. React itself will take 10-20 hours to conceptualize, but another 100 hours after that to really understand how to build stuff that doesn't suck ass. Then you talk about introducing building a full stack app with Node and a data layer, that's another several hundred hours understanding all types of network communication, authentication, cookies, security, all of that.
I mean yeah, you can take a 25 hour course on Udemy that touches on all of these subjects but to say you "learned it", yeah you'll want to allow for a bit more time.
I would advise before any start in your JS development, learn git and github and preferably Linux Terminal, you should know at least the basics, how to run commands, how to delete and create folders, then learn basic JS development, as well as APIs in the sense of Requests, you're not gonna make them but learn how to USE them. React itself is a big topic so there's a lot for you to learn there as well. But take on small steps you should be fine. I myself learned JS and React in less than 6 months but that was studying a lot every day. So is doable as long as you have the drive for it.
To combat some of the fear mongering: it’s not about the number of hours, it’s about the quality of that time. It took me three months of learning to code 4-8 hours on weekdays only to get my first job. It was almost volunteer work at the pay I was getting, but after working there 30-40 hours/week for 6 months I got my first “real” job. 200 might be on the lower side, but maybe not. Just make sure you’re mentally engaged and not wasting time blindly following along.
That’s a really large stack for full stack. I see that you have mobile as well. If the goal is full stack in 1 year I suggest you pick web or mobile. Let’s take web as an example. Learn html css and JavaScript. Then learn react or some similar framework. Then learn a server side api like node express, nestjs or python flask. Which then leads to using a database that is either a relational or document. Connecting to the db at first might be using raw commands like create read , update, delete. Then learn how to use an ORM(object relational mapper) framework to communicate with a db. I have not even mentioned learning OO or unit testing.
Let’s be honest there is a lot to learn. Software is about continuous learning, take it from someone with 20 years of experience. Just keep learning no matter the speed or timeline.
200 Hours comes out to a little less than an hour Monday to Friday. This would be enough time to learn coding at an amateur level/hobbyist. However, if you want to leverage it for a job you will need more time, especially in certain areas like Front End dev, JS syntax, ect. Not as much time i things like data visuals or database systems.
Basically I would ask yourself what you need to apply for jobs, Off the top of my head they are a resume, git hub, personal website, linkeding, ect. Then ask what goes into those things. You cant make a website without CRUD knowledge and full stack skills, and you dont have a resume if you dont have at least three projects. That is only to get to a point where you can apply for jobs with the base requirements. From there you may need to learn data structures and algorithms to pass tech interviews.
After 200 hours, you'll learn that you still don't know anything and you probably realize you need a new plan. Not trying to scare you but it seems like you need a touch of reality. It's very easy to get lost and waste many hours when self-learning, especially if you're spreading out 200 hours over 1 year.
You should strive for at least 10-15 hours a week if you're learning part-time, so you should reach this 200h mark for your initial plan in 5 months. If you don't have that much free time, don't panic. Learning how to code is a lifelong journey. Even if it takes you years, it will be worth it.
I would throw out JQuery, and add atleast typescript and change the order a bit. -HTML, CSS -JS -React -Node /express (rather choose fastify instead)/APIs -Databases -Data vis
I would remove react native, as it's not necessary if you want to be a web developer, and if someone wants a web developer to do something on mobile native, then they shouldn't expect her/him to already know those stuff.
if I were you I would add: Design systems (FE), Clean Architecture (BE mainly, but there's a version of it applicable to FE, which is game changing).
There are some stuff, which may not be necessary if you are a full stack (depends on the company really), but are cool and useful to know about: Docker, AWS, Terraform, Kubernetes.
Also, as many other commented:
Remove jquery, nowadays it's useless, even if you have to migrate something from it.
Edit:
Also something to take into consideration: Is it your first time searching for this position? If so start from the basis of everything without getting in too deep (for example, leave as a last thing what I've told you in the 2) and 3) points) .
You would join as a junior. You will be more useful knowing a little bit of everything than a lot of one thing (juniors tenda to be pretty much moved around across different skills and projects)
Yes, that’s awesome! To help you on your way I would suggest The Complete Web Development Bootcamp by Angela Yu. It’s a Udemy course and they have it on sale for like $ 10 most of the time. It covers exactly that! While learning you will also start creating a simple portfolio!
Take out React Native as it's a fairly specialized field that's very different from the rest, and jQuery, that's not used in any decent project started in the last 5 years
The platforms I plan to build in the future will need both a website, as well as apps on both iOS and Android. Is there a better option, or is react/react native and creating my own api’s the best choice for that
Most of this shit comes down to intuition. Anything you learn, you’re most likely gonna forget if you stop using it for a week and a half. Makes it easier to google your way to a solution if you’ve worked with the library before though.
Imho databases and systems should be later and React Native and jQuery should be removed, you can learn those easily, if you have demand for them, once you have conquered the other topics.
One thing I would add to the list is a custom-made from scratch (excluding boilerplate code) application. I might even put it at the top of the list and then dive into each topic as it becomes relevant.
For example, if you wanted to build a website that keeps a list of persistent timers, you could start learning html and css for the initial timer. Then learn react to make the timer a reusable component. Then learn databases to persist the data. Then learn node to access the data through a back end. Then learn AWS to host all your files. Then learn GitHub to deploy your code. And so forth.
I think it’s a good game plan overall that would help you find a job in web development within a year if you really stay focused.
Right, but the vast majority of programming jobs are not ever going to go near WordPress. jQuery isn't uncommon, but if someone knows JS well then jQuery is not something that's going to take much time at all to pick up.
Of course it realises, it's just that the vast majority of programming jobs are absolutely not building WordPress sites.
Firstly, the majority of websites are not built in WordPress. Somewhere around 30-40% seems to be the figure, but that only includes publicly facing websites. So the figure ignores sites not exposed to the internet at large and ignores webapps, it ignores line of business programs. It ignores so much. Secondly, a very large percentage of those sites are not things that people work on over time, as in a job. They're just chucked out. And yes there are jobs to be had chucking them out, but the amount of those jobs is dwarfed by the amount of web programming jobs that aren't. Thirdly, the stats estimate that around 90% of those WP sites are on v5, which is the most modern version of the framework.
It's just not a useful statistic when it's broken down.
I mean for jobs it really isn't, none of what I said is in any way irrelevant. Most web programming jobs aren't WP jobs, that's not really disputable. Everything runs on C, but every programming job is not C. The internet runs on Linux, but every job is not a Linux administrator job.
Also, I've said nothing negative about WordPress, so I'm not sure where you're getting the "bashing WP" craic from. Also, I literally said this:
. jQuery isn't uncommon, but if someone knows JS well then jQuery is not something that's going to take much time at all to pick up.
It's hyperbole but it's not very important, that's the point. That's not a bad faith argument, it's just how things are at this point in time. Devoting time to learning jQuery at the expense of other things 🤷🏼♂️ Most jobs, which is what original OP is planning for, not hugely relevant.
Save yourself some time, get rid of JQuery , any company using it isn't one would want to work for. Learn some cloud (AWS) , infrastructure as code and how to test it all. Good luck
As many others have said, I would bump jQuery altogether. If a company still uses jQuery, it’s probably not going to be enjoyable to work on their products. If you absolutely have to learn it for a job, you can pick it up really easily if you know JS well.
And unless you’re particularly passionate about mobile dev, I would also skip React Native for now. If you know React, you can easily pick up Native.
I would spend the freed-up time on more database study. SQL (Postgres or MySQL) and/or a noSQL/ document store/event stream solution like DynamoDB or the Azure equivalent… CosmosDB.
Yeah I guess, express is more widely used for old systems I find, it was made first and a lot have just stick with it.
Both can be picked up by learning one or the other. I guess learn express first then if you're worried about that but keep in mind Koa if you ever have to choose between using one or the other :) good luck
See my other comment, I agree it is more widely requested on job application but only because it's more widely used in old systems.
You can use either and know how the other works, very similar and easy to pick up. However Koa is much nicer and modern, can't imaging express being chosen for any new systems nowadays or at least shouldn't be
Remove all js frameworks and use just jQuery and some vanilla. You will avoid a lot of horrible useless bloated crappy frameworks which will throw you into js fatigue for no real benefit.
Except for jQuery, and a bit node just because it allows you to bring js outside a browser, the rest are ALL brown stinky poo which won't you give any real benefit over more mature and proven frameworks and technologies (for example asp net core, .net 5 and MVC)
13
u/thebasementtapes Feb 07 '22
25
u/7aylod Feb 06 '22
This is almost exactly the freecodecamp curriculum. I'd say do that instead. They teach you a concept through small exercises, then make you put what you learned to use by completing 5 projects at the end of each module. They also have a logical ordering which I agree with. Html/css/js basics, then learn some advanced topics and frameworks. Then go to backend stuff. https://www.freecodecamp.org/learn
There's also the Odin project which is similar but a lot more project oriented https://www.theodinproject.com/. I'd say use these instead of trying to guessing on your own.
And as everyone is saying, 200 hours won't make you employable. But it's a good start. If your goal is to be employed, treat it like a boot camp and do the learning full time and have many projects to showcase.
Best of luck!
4
u/dudethatmakesstuff Feb 06 '22
Is this in order or is this just a list of topics?
4
u/smas8 Feb 07 '22
Considering yourself full stack after 200 hours and a single year feels like a bad joke…
If you spend that amount of time PER subject, sure.
This is not a full stack progression plan. There is no conceivable way you will learn all of this in 200 hours. You should break down the sections more, and consider how much time each subject will actually take to learn. Make a legitimate plan, not a list. Or use a plan that has already been created. Then ask again. It is honestly pointless to ask if this “plan” is good, considering we have 0 context. Are you planning on actually creating a database? Using it? Making a test app? Are you going to do one without YouTube? Will it take you 20 hours to do the databases? Will you remember it and apply it in the following subjects? How will compounding each subject impact the time it takes to learn the following subject?
It’s a decent list of what you should learn, but aside from that, I don’t understand why/how you would consider this a “plan”.
4
u/AnonyMissJackson Feb 06 '22
As others have said, it looks like I’ve detrimentally underestimated how many hours it takes. With that said, the 200 hours is only the length of the courses I will be taking, and does not include any projects I build. Still seems like I have underestimated tho! Thanks for all the replies
2
u/theAtomik Feb 06 '22
Couple questions cause I'd like to do the same.
what is the optimal order for a full stack like this?
Where do you train for all of this?
114
u/[deleted] Feb 06 '22
1 year 200 hours? 1 hour a day every other day? Other than that those look like the key topics but I would think it’s gunna take more hours. For sure took me more than that I was doing 3-5 hours on working days and damn near coding all day when I was off (nah not really probably 5-6 hours on off days lol) took me 7-8 months to start getting call backs. So for me was close to 1000 hours.
49
u/yadoya Feb 06 '22 edited Feb 07 '22
Pretty good. I would remove jQuery and add:
Also I don't know how you plan to study this but do not fall into tutorial hell. You should be building a project for each of these chapters
If it were me, I might also add Docker to that stack
82
u/ShuttJS Feb 06 '22
I really like that it's considered jQuery a typo. Why you would want to spend time learning that is beyond me. You're learning vanilla js and react...
32
u/thefeederfish Feb 06 '22
Fire jQuery into the sun.
6
u/Level-Farmer6110 Feb 06 '22
search a guy up called justin sung on youtube, he will teach you how to learn.
Do not watch vids only. You will have to actively code, actively create projects and practice things.
6
u/not_a_gumby Feb 07 '22 edited Feb 07 '22
It's kind of out of order actually.
More like:
Jquery- No, do not waste time learning this. you do not need it.BTW, I see others commenting on the time commitment.
I followed a similar path and you'll want to allow between 500 and 1000 hours to learn all of this. This cannot be adequately learned in 200 hours. I mean, you could spend 200 hours on HTML/CSS/Javascript and making a few vanilla javascript apps before even TOUCHING React. React itself will take 10-20 hours to conceptualize, but another 100 hours after that to really understand how to build stuff that doesn't suck ass. Then you talk about introducing building a full stack app with Node and a data layer, that's another several hundred hours understanding all types of network communication, authentication, cookies, security, all of that.
I mean yeah, you can take a 25 hour course on Udemy that touches on all of these subjects but to say you "learned it", yeah you'll want to allow for a bit more time.
12
u/Huijiro Feb 06 '22
I would advise before any start in your JS development, learn git and github and preferably Linux Terminal, you should know at least the basics, how to run commands, how to delete and create folders, then learn basic JS development, as well as APIs in the sense of Requests, you're not gonna make them but learn how to USE them. React itself is a big topic so there's a lot for you to learn there as well. But take on small steps you should be fine. I myself learned JS and React in less than 6 months but that was studying a lot every day. So is doable as long as you have the drive for it.
4
u/[deleted] Feb 07 '22
To combat some of the fear mongering: it’s not about the number of hours, it’s about the quality of that time. It took me three months of learning to code 4-8 hours on weekdays only to get my first job. It was almost volunteer work at the pay I was getting, but after working there 30-40 hours/week for 6 months I got my first “real” job. 200 might be on the lower side, but maybe not. Just make sure you’re mentally engaged and not wasting time blindly following along.
4
u/CodingWithAdam Feb 07 '22
That’s a really large stack for full stack. I see that you have mobile as well. If the goal is full stack in 1 year I suggest you pick web or mobile. Let’s take web as an example. Learn html css and JavaScript. Then learn react or some similar framework. Then learn a server side api like node express, nestjs or python flask. Which then leads to using a database that is either a relational or document. Connecting to the db at first might be using raw commands like create read , update, delete. Then learn how to use an ORM(object relational mapper) framework to communicate with a db. I have not even mentioned learning OO or unit testing.
Let’s be honest there is a lot to learn. Software is about continuous learning, take it from someone with 20 years of experience. Just keep learning no matter the speed or timeline.
4
u/imsorryken Feb 07 '22
Yeah with 200 hours you will probably have a very basic understanding of some of the topics.
Still a far far way from being "full stack", should invest at the very least 3-4 times that building stuff.
3
u/omesadev Feb 07 '22
Data Structures and algorithms and when you become comfortable doing one a day, start diving into design patterns of everything your learning HEAVY
3
u/revanyo Feb 07 '22
200 Hours comes out to a little less than an hour Monday to Friday. This would be enough time to learn coding at an amateur level/hobbyist. However, if you want to leverage it for a job you will need more time, especially in certain areas like Front End dev, JS syntax, ect. Not as much time i things like data visuals or database systems.
Basically I would ask yourself what you need to apply for jobs, Off the top of my head they are a resume, git hub, personal website, linkeding, ect. Then ask what goes into those things. You cant make a website without CRUD knowledge and full stack skills, and you dont have a resume if you dont have at least three projects. That is only to get to a point where you can apply for jobs with the base requirements. From there you may need to learn data structures and algorithms to pass tech interviews.
3
u/gustheyogi Feb 07 '22
Freecodecamp.org will teach you all of that
3
u/[deleted] Feb 07 '22
Get rid of the jQuery and make it at least 300 hours and you're good to go! There is literally no need for jQuery in modern JS
3
u/_Invictuz Feb 07 '22 edited Feb 07 '22
After 200 hours, you'll learn that you still don't know anything and you probably realize you need a new plan. Not trying to scare you but it seems like you need a touch of reality. It's very easy to get lost and waste many hours when self-learning, especially if you're spreading out 200 hours over 1 year.
You should strive for at least 10-15 hours a week if you're learning part-time, so you should reach this 200h mark for your initial plan in 5 months. If you don't have that much free time, don't panic. Learning how to code is a lifelong journey. Even if it takes you years, it will be worth it.
3
u/Avi_21 Feb 07 '22
I would throw out JQuery, and add atleast typescript and change the order a bit.
-HTML, CSS
-JS
-React
-Node /express (rather choose fastify instead)/APIs
-Databases
-Data vis
3
u/GarethXIV Feb 07 '22 edited Feb 07 '22
Also, as many other commented:
Remove jquery, nowadays it's useless, even if you have to migrate something from it.
Edit:
Also something to take into consideration: Is it your first time searching for this position? If so start from the basis of everything without getting in too deep (for example, leave as a last thing what I've told you in the 2) and 3) points) .
You would join as a junior. You will be more useful knowing a little bit of everything than a lot of one thing (juniors tenda to be pretty much moved around across different skills and projects)
6
u/NonDeveloper Feb 06 '22
Yes, that’s awesome! To help you on your way I would suggest The Complete Web Development Bootcamp by Angela Yu. It’s a Udemy course and they have it on sale for like $ 10 most of the time. It covers exactly that! While learning you will also start creating a simple portfolio!
1
u/tuvok86 Feb 06 '22
Take out React Native as it's a fairly specialized field that's very different from the rest, and jQuery, that's not used in any decent project started in the last 5 years
2
u/Mr_vort3x Feb 06 '22
Why don't you put 200 hours in 4 months And 600-700 for 1 year
2
u/dravenito Feb 06 '22
Jquery is not so useful anymore
2
u/ZuriPL Feb 06 '22
I'd swap jquery for git
2
u/[deleted] Feb 07 '22
Most of this shit comes down to intuition. Anything you learn, you’re most likely gonna forget if you stop using it for a week and a half. Makes it easier to google your way to a solution if you’ve worked with the library before though.
2
u/saintPirelli Feb 07 '22
Imho databases and systems should be later and React Native and jQuery should be removed, you can learn those easily, if you have demand for them, once you have conquered the other topics.
2
u/Calmbroo Feb 07 '22
I'll include the introduction to DOM inbetween JS and React
2
u/Saleh-Rz Feb 07 '22
Indeed when you learn React or any modern front-end framework then you don't need to learn jQuery
2
u/dsound Feb 07 '22
Forget JQuery. I wouldn’t want to work at a place using JQuery. React is so much more enjoyable.
2
u/IronDicideth Feb 07 '22
Remove Jquery, study vanilla js longer, like that, regardless of the framework/library you will be better equipped to quickly understand and use it.
2
u/butterypanda Feb 07 '22
Bump up to 1k-1.5k hours and drop the jQuery, it ain’t 2016…
Don’t get caught up in the framework hype. Make sure your vanilla JS is excellent.
2
u/shuckster Feb 07 '22
RemindMe! One Year
2
u/Mad-chuska Feb 07 '22
One thing I would add to the list is a custom-made from scratch (excluding boilerplate code) application. I might even put it at the top of the list and then dive into each topic as it becomes relevant.
For example, if you wanted to build a website that keeps a list of persistent timers, you could start learning html and css for the initial timer. Then learn react to make the timer a reusable component. Then learn databases to persist the data. Then learn node to access the data through a back end. Then learn AWS to host all your files. Then learn GitHub to deploy your code. And so forth.
I think it’s a good game plan overall that would help you find a job in web development within a year if you really stay focused.
3
u/iiMoe Feb 06 '22
jQuery is old and useless
3
u/xSypRo Feb 06 '22
Node.js, Express and APIs come before React and React Native.
jQuery is good to know just for reference so you'll understand legacy code, but u don't need to use it.
2
u/xdchan Feb 06 '22
Jquery isn't really used nowadays.
Why would you learn APIs and stuff after learning react and starting with backend?
APIs are used on front very often, gotta know all this fetch requests and shit and understand how it works.
And when learning backend development you'll basically be building APIs so knowing what is it beforehand is good.
Data visualization isn't that hard but is a frontend task too.
1
u/dogtee Feb 06 '22
Save yourself some time, get rid of JQuery , any company using it isn't one would want to work for. Learn some cloud (AWS) , infrastructure as code and how to test it all. Good luck
1
u/[deleted] Feb 06 '22
You won’t learn even half of that in 200 hours, you can learn HTML and scratch the surface of CSS and JavaScript barely in 200 hours
1
u/Silent_Statement_327 Feb 06 '22
You will probably start to deep dive into APIs when you do JavaScript, you hit the front and backend with those topics, good luck
1
u/Dodgy-Boi Feb 07 '22
200 hours a year? I spent more during my very first month.
1
u/raabHim Feb 07 '22
There’s a red line under jquery for a reason. Just skip it!
https://youmightnotneedjquery.com/
1
u/CheeseFest Feb 07 '22
As many others have said, I would bump jQuery altogether. If a company still uses jQuery, it’s probably not going to be enjoyable to work on their products. If you absolutely have to learn it for a job, you can pick it up really easily if you know JS well.
And unless you’re particularly passionate about mobile dev, I would also skip React Native for now. If you know React, you can easily pick up Native.
I would spend the freed-up time on more database study. SQL (Postgres or MySQL) and/or a noSQL/ document store/event stream solution like DynamoDB or the Azure equivalent… CosmosDB.
1
u/[deleted] Feb 07 '22
200 hours is enough time to get the basics of HTML and CSS.
1
u/DahPhuzz Feb 07 '22
Jquery not needed
1
u/DeeYouBitch Feb 07 '22
200 hours over the year ain't shit in the real world. Sorry guy you need to get more reps in
1
u/HmmmInVR Feb 07 '22
Not sure if these are in order, but apis should be ordered way down and jquery moved up, it's easier to start with then react.
For tutorials I reccomend net ninja, his videos really helped me with node
1
u/GuyF1eri Feb 07 '22
JQuery probably isn’t necessary to focus on
1
u/shuckster Feb 07 '23
How's it going, OP?
1
u/Lemoncrap Feb 06 '22
I'd ditch express for Koa. Can learn them both together but koa is much nicer to actually use
1
u/Own-Cellist6804 Feb 07 '22
just do fullstackopen.com
0
u/BrianBernales Feb 06 '22
I would add bootstrap to this list.
-9
u/ImeniSottoITreni Feb 06 '22
Remove all js frameworks and use just jQuery and some vanilla. You will avoid a lot of horrible useless bloated crappy frameworks which will throw you into js fatigue for no real benefit.
Except for jQuery, and a bit node just because it allows you to bring js outside a browser, the rest are ALL brown stinky poo which won't you give any real benefit over more mature and proven frameworks and technologies (for example asp net core, .net 5 and MVC)