Want to become full stack developers in 40+ age & ADHD

Hi,
Thank for reading this, as title says i am 40+ man with ADHD but really want to learn “Full Stack Web Development” because this is my chance to switch my career and get higher pay.
I chose " Certified Full Stack Developer Curriculum" yesterday and am fully determined to learn it but found today that its in beta phase.
So please guide me should i follow the above mentioned curriculam or switch to " freeCodeCamp’s core curriculum" ?

I am also follwing OdinProject too…

HI @saud-kazmi !

Welcome to the forum!

The beta curriculum is way more comprehensive. So I would suggest going through the full stack cert.
Even though it is still in beta, there are way more opportunities for practice and better understanding.

Hope that helps

1 Like

Thanks for your reply…
but some topics are in coming soon status…

Yes, but by the time you finish the existing content the other content will be available.

What is already there will take most people several months to get through.
Also, when learning it is best not to speed run through curriculum because it will lead to gaps in your knowledge.
Taking your time and learning deeply is the way to go.

So, I would suggest starting at the top and work your way down :+1:

Thanks, I am going to learn the “Certified Full Stack Developer Curriculum”
for me, it’ll be 3x times tougher because of my age and ADHD.

I used to have my website with a paid domain and hosted on a free hosting server, which was made by “Dreamweaver” through page making, with very little HTML use.
The purpose of that website is to host my “Tutorials” on 3DS Max and Flash.

Being 50+ and with ADHD and 28+ years of experience coding

  • one piece of advice I do not see much talk about is “the Feedback Loop.”
    Whatever aspect of coding you try to learn, break it down to the tiniest task you can and get it to work. Then, build the most minor thing on top of that and get that to work. You mustn’t get ahead of yourself. This is the feedback loop — one tiny thing at a time, and make sure it works - that is the feedback. Do not try to write a lot of code; then try to fix whatever issue/bug your runtime tells you is there. Often, I have tried that I had to pull apart 90% of the code only to find I had missed something.
    This is also the way that I work on larger projects. The worst is when you have to wait while GitHub is running 1000 tests, and you have to wait 10 - 15 minutes before a result. 10 - 15 min before a result is no feedback loop. You need feedback every 1 - 2 minutes. So it only a few expressions or lines at the time. Then, try to test your code.

Hope it will help you. Also , remember that frustration it part the developer experience. With experience you’ll learn that if you keep attacking the problem/bug from different angle you will discover the root of it all. You’ll still get to be frustrated, only with experience you’ll learn that if you keep at it a little longer a solution will come to you.

Best of luck to you!

1 Like

thanks for your advice, I really appreciate it.