Thanks for the insight. I am constantly learning and studying. However, it takes me a while to get the grasp of things. React is the main skill that I know for sure I'll need to learn. So I guess job searching will be on hold for a while.
React would be important if you're aiming for a front-end developer job. Except odds are you will need a number of other skills to "stand out" beyond just React. What about state-management? UI/UX design? Responsive design? You might need SSR/SSG, so what about nexjs? The list can keep going on and on.
Everyone is learning and studying, and there will be continual changes/updates to the ecosystem so its a game that you don't play to "win", it's a game you must keep playing.
You're welcome to pause your job searching, but when it kicks back up, you'll find you might need to learn ___ now, and end up more or less back where you started, except with some pre-existing experience to build ontop of.
However, it takes me a while to get the grasp of things.
Time is time, it will take time to learn what you need, there isn't a shortcut besides selectively focusing on specific topics and using your time wisely. Everyone can have their opinion on what is important and what isn't, or what you should focus on or shouldn't. But it really depends on you, your goals, and job environment.
So depending on your position, understanding where you're trying to go (front-end developer?) a good way to get an idea of what the expected requirements are is to look at job posts. From there you'll get a direct idea of what is expected of you. Then you can compare that relative to what you currently know, and then estimate how long it will take to get to what is asked in the job post. If that estimation looks like it isn't doable in your expected time frame, then maybe shift to a different job with different requirements?
I usually say you only need 3 things to get into programming. Time, grit and an internet connection. Assuming you're serious enough to have enough grit to grind through any challenges you face, and pay your internet bill you just need time, which is something no one has infinite amounts of and what you'll want to make sure you use as wisely as possible to get where you need to go.
You're welcome to pause your job searching, but when it kicks back up, you'll find you might need to learn ___ now, and end up more or less back where you started, except with some pre-existing experience to build ontop of.
You made a point here.🤔 I think the best thing for me to do is just to learn the basics of HTML, CSS, and mainly JavaScript. Build projects and learn about new libraries and frameworks along the way. At this point, I'm open to applying for non-coding jobs. Just to get my first tech job and move on from there.
Then you can compare that relative to what you currently know, and then estimate how long it will take to get to what is asked in the job post. If that estimation looks like it isn't doable in your expected time frame, then maybe shift to a different job with different requirements?
Another point well made. I've been practicing my coding skills for quite some time now. I'm getting better but not 100% yet. I was hoping to get a job this summer BUT doesn't look it will work out that fast. So now I'm giving myself another 2-3 months. In the mean time, I'll look up apprenticeships and just keep applying for jobs that seem doable with the level of experience I have.
My humble opinion is DO NOT AIM FOR REACT (or angular, vue, svelte...).
Build up the basics, js, html, css .
When you know the basics, everything comes easily. By the way, frameworks come and go, languages stay much longer.
Cheers
Yes, I have been doing some serious thinking after reading everyone's comments. And I think I'll just focus on the basics. Especially getting a better understanding of JavaScript.
Why React?
If you have little Dev experience I think React is quite difficult to grasp. You can still do a lot of it by rote and copying patterns without really understanding what is going on.
Development is waaaay more than front-end or even Full stack web dev. Controversial IMHO coming up....
If you really want to add value to any organisation and also get a (fairly) gentle introduction to development, especially object oriented, learn some Excel VBA. The first time you show your manager that you have managed to import the last 24 months sales reports and convert them to Year-on-year trend analysis charts with the ability to filter by product range and region, and all they have to do next month is press this bug red button... You will be a GOD!
Yes I actually did learn about Excel VBA when I was trying to get an accounting job. But that's another story. I'll just have to refresh my memory on Excel.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the insight. I am constantly learning and studying. However, it takes me a while to get the grasp of things. React is the main skill that I know for sure I'll need to learn. So I guess job searching will be on hold for a while.
React would be important if you're aiming for a front-end developer job. Except odds are you will need a number of other skills to "stand out" beyond just React. What about state-management? UI/UX design? Responsive design? You might need SSR/SSG, so what about nexjs? The list can keep going on and on.
Everyone is learning and studying, and there will be continual changes/updates to the ecosystem so its a game that you don't play to "win", it's a game you must keep playing.
You're welcome to pause your job searching, but when it kicks back up, you'll find you might need to learn ___ now, and end up more or less back where you started, except with some pre-existing experience to build ontop of.
Time is time, it will take time to learn what you need, there isn't a shortcut besides selectively focusing on specific topics and using your time wisely. Everyone can have their opinion on what is important and what isn't, or what you should focus on or shouldn't. But it really depends on you, your goals, and job environment.
So depending on your position, understanding where you're trying to go (front-end developer?) a good way to get an idea of what the expected requirements are is to look at job posts. From there you'll get a direct idea of what is expected of you. Then you can compare that relative to what you currently know, and then estimate how long it will take to get to what is asked in the job post. If that estimation looks like it isn't doable in your expected time frame, then maybe shift to a different job with different requirements?
I usually say you only need 3 things to get into programming. Time, grit and an internet connection. Assuming you're serious enough to have enough grit to grind through any challenges you face, and pay your internet bill you just need time, which is something no one has infinite amounts of and what you'll want to make sure you use as wisely as possible to get where you need to go.
Good luck, keep learning, keep building!
You're welcome to pause your job searching, but when it kicks back up, you'll find you might need to learn ___ now, and end up more or less back where you started, except with some pre-existing experience to build ontop of.You made a point here.🤔 I think the best thing for me to do is just to learn the basics of HTML, CSS, and mainly JavaScript. Build projects and learn about new libraries and frameworks along the way. At this point, I'm open to applying for non-coding jobs. Just to get my first tech job and move on from there.
Then you can compare that relative to what you currently know, and then estimate how long it will take to get to what is asked in the job post. If that estimation looks like it isn't doable in your expected time frame, then maybe shift to a different job with different requirements?Another point well made. I've been practicing my coding skills for quite some time now. I'm getting better but not 100% yet. I was hoping to get a job this summer BUT doesn't look it will work out that fast. So now I'm giving myself another 2-3 months. In the mean time, I'll look up apprenticeships and just keep applying for jobs that seem doable with the level of experience I have.
My humble opinion is DO NOT AIM FOR REACT (or angular, vue, svelte...).
Build up the basics, js, html, css .
When you know the basics, everything comes easily. By the way, frameworks come and go, languages stay much longer.
Cheers
And patterns and algorithms never change.
Yes, I have been doing some serious thinking after reading everyone's comments. And I think I'll just focus on the basics. Especially getting a better understanding of JavaScript.
Why React?
If you have little Dev experience I think React is quite difficult to grasp. You can still do a lot of it by rote and copying patterns without really understanding what is going on.
Development is waaaay more than front-end or even Full stack web dev. Controversial IMHO coming up....
If you really want to add value to any organisation and also get a (fairly) gentle introduction to development, especially object oriented, learn some Excel VBA. The first time you show your manager that you have managed to import the last 24 months sales reports and convert them to Year-on-year trend analysis charts with the ability to filter by product range and region, and all they have to do next month is press this bug red button... You will be a GOD!
Yes I actually did learn about Excel VBA when I was trying to get an accounting job. But that's another story. I'll just have to refresh my memory on Excel.