Every developer wants to be Full Stack !
Why ?
It has it's own perks and benefits...
You get paid more...
You are no more dependent on other d...
For further actions, you may consider blocking this person and/or reporting abuse
I'm not a fan of phrases like this, like "rockstar" or "ninja", etc.
I'd like to comment on this particular one though: it's very gendered. It's very "bro".
I can't imagine anyone making a post called "How to become a full stack Wonder Woman" without raising eyebrows, so I'm going to raise my eyebrow at this one.
Curious on why rockstar and ninja are gendered. There are a lot of female rock stars. Furthermore the data shows rock bands that include at least one female member are getting labels deals at 8 times the rate of all male rock bands. Female bands are also selling significantly more. I also know over 10 cases where the bands' record deals were revoked because a female member left the band purely out of personal decision and a shift in their interests. If anything there stars to be bias against males in the music industry. Can't speak to ninja as I don't know any male or female ninjas but if you are going to make such comments please do some research. Opinions are irrelevant and even dangerous on such sensitive subjects. We are not going to end sexism with speculations but with precise strikes to the source of the problem.
Edit: there were also a lot of female rock stars in the 80s, arguably the most misogynistic times of rock n roll so I don't know of time where rock star purely represented males.
Rock star and ninja aren't particularly gendered. What I was getting at was the trend a while ago for describing developers as something extraordinary, like "10x" or "guru" or something. The "superman" part was the gendered part. I was trying to convey that while I didn't like that type of term in general, it was the specific instance of being gendered that made it seem too much.
If we can't flip the genders and still be comfortable with the sentence, then something's up with it, and I think most people would find a title like, "10 ways to be Supergirl with Javascript" to seem clunky.
Oh my bad. Apologies, I misunderstood. Yes I agree with you on the superman part and the whole idea behind that "10x" trend.
Yeah I agree on that. I have updated the title name though. Supergirls are awesome by the way!
Great, but why "supergirls" and not "superwomen"? I see that at least you managed to use the latter in your revised title, but in your comments you're not demonstrating much awareness of the issue being raised here.
I'd recommend against all the click-bait superlatives and "we're all trying to be rock-star devs" nonsense. I gave up reading the article as soon as I got to "fullstack ninja". I came to the comments to say as much and saw someone already had.
For those who don't want to conform to the gendered, macho stereotypes you're perpetuating it is all very off-putting.
I honestly don't know why anyone would want to be a fullstack dev. I worked for multiple unicorns, I worked for start ups where there was an abundance of work to be done. In both cases full stack devs are always pushed to play with the mediocre, boring parts of both worlds. "oh here you go, set up this api while we experiment with all the cool stuff in the backend". And in both cases fullstacks were paid less because they don't need to have as much critical thinking skills as all in backend. I certainly agree that every dev should have full stack skills, it really helps when you are experimenting with stuff, or simply building your own company. Being able to bootstrap your product is a huge plus. I wouldn't do it with any of the languages mentioned here but yeah :) and don't get me wrong, I am not saying as developers they are inferior or anything. I just would never apply to a fullstack position because of the scope of their duties
You're absolutely correct, sticking to a stack and become the best is better.
Yeah I think focus should be on one language at both stacks. It's a better decision in the long run.
If you focus on one point in the stack, you can pivot more easily. Swapping from dotnet core to spring boot for backend is way easier than swapping languages and frameworks for both your api and UI.
Absolutely correct
Yeah Donovan. You are correct..
Nice article, but none of these tutorials teach you superhuman strength or speed though ;)
I think if you do even a single end-to-end project you are more confident in presenting your skills then. Also, these are for beginners. So, you can relate.
Well I'm beginner to think someone's salty lol
Oh that's cool though.
Thanks, @saeeddev . I'm glad you found these freeCodeCamp video tutorials so helpful. Thanks for helping raise awareness of them.
We publish new full-length courses each week on our nonprofit's YouTube channel. We just passed the 1.5 million subscriber mark this week, too.
Everything's free and there are no ads, either. I hope you all find these helpful in your coding journey.
Thank you so much @ossia . You are inspiration for me and millions of devs like me. You are a great teacher and a person too. I have a great wish to talk with you. May be I can come across a chance to speak to you. Thank you so much for commenting here.
I swear "Superhero" would have worked just fine, if not better.
This is a good article by the way. Although I would still feel horrible about myself if I'm not able to complete all these projects in less than a month, thus I'm not good enough.
Your wording is really really interesting
You can bro...Just start with easiest one or with which you are more comfortable...Then let us know about your journey...We are here for your help...
lol nvm
What? Why? It gives you a full No-SQL database and serverless functions out of the box. It's a fully-managed full-stack setup. You CAN ignore the backend and just use the web libraries, but you can also build a full set of Flask or Express microservices on top. It's awesome.
I guess it's best but for beginners. And it make you a bit lazy too. You cannot understand backend completely until you endure the pains of setting it up manually. Thanks for your comment too.
Yeah. But it's good for beginners. The list contains projects which use MySQL and MongoDB as well. So, that makes sense I guess. To start with Firebase and then move on to conventional DBs.
Why no Spring Boot? Clearly it's one of the most used RDFs in n use today.
You can have look at the below playlist, it's about building a full stack Reddit clone with spring boot and angular.
youtube.com/playlist?list=PLSVW22j...
Note that this series is not complete yet.
I have another playlist which is completed.
Building a simple blog with spring boot and angular
youtube.com/playlist?list=PLSVW22j...
Yeah. But I though according to a new person who is learning backend. So, I think he should be comfortable with Django, Flask and NodeJS. After that he can pick up Spring Boot.
Thanks so much Saeed. Really helpful info for me and Btw the title is just fine, I am a woman.
Thank you soooooooo much Gal. You are absolutely a SUPERWOMAN. Go and rock the world!
Thx for this! This is really what I wanted. Helped A LOT.
Can I translate in Korean this post? If you don't mind, I wanna share this awesome post in Korean. Surely, There will be a linke directing to this original post.
When the actual title have more comments than the content.
Yeah. Priorities of people matter.
No vue huh...
I personally love Vue but I was forced to compile this list according to the requirements of the market.
Well.. its time to learn a new tool.. thanks for the lists.
Yeah my strategy in this regard was to learn JS, then ReactJS and then you can move on to Angular, Vue or Svelte.
Thank you so much for appreciation. I will soon share more free resources.
Much much thanks. Amazing. This helps a lot for beginner developers such as me.
Thank you so much for your appreciation Hina. You can ping me anytime for help in ReactJS and Django.
Yeah sure. One rise by rising others!
Absolutely. I feel great when I help others.
Great resource! Thanks for this
Thanks for your appreciation. Will you want to add some others which you think would be great for newbies?
Good to hear that. Let us know about your progress in this regard. We would love to hear that.
This is beautiful! Thanks for sharing, Saeed
That's great Bashir. Thanks for appreciation. Stay tuned. I will share more free resources soon.
Great Edwin.
Good work saeed ! . I wanted to know about firebase this seems ideal to learn
Thank you so much Majid. Stay tuned. I will share more free resources soon.
I m waiting !!!! .
Thanks bro.
This felt more like a Great FCC ad than an article. But kudos nonetheless for highlighting a great source of free training.
Yeah I chose FCC videos because it's free and tutorials are awesome too.
Thanks for that tip man. I'm already familiar with SQL server and MongoDB so I wasn't too keen on learning yet another database.
Yes. These tutorials are for beginners. That's why I included Firebase, MongoDB and MySQL as well.
This is really helpful Saeed. It will go a long way, I needed this. Thank you once again.
Thanks Vusi. Stay tuned. I will share more free resources for beginners.
Django is so bad though 😩
Like, I would honestly take a five-years outdated version of Rails over today's version of Django >.>
Rube dev here. I'd like to know your reasons for hating Django too. I don't have mu experience in it, but generally in many aspects it seems better designed than Rails.
I haven't worked on Rails but Django's structure is a great thing.
I haven't used it for 5 years or so, but it was pretty damn good back then. What's changed?
I don't see anything bad in it. Yeah it has a lot of django-specific clutter but still it's amazing once you have a good grip on it. What are the reasons due to which you didn't like it?
I would love to hear the reason why you think Django is bad😀
You are welcome. I regularly share stuff like that. Stay tuned for more in coming days.
Are these the kind of projects where you need to have a basic understanding of the languages used?
These are fantastic ideas.
Yeah most probably firebase users are beginners or novice devs.
Nice post. Thanks
I have very basic knowledge about django so simply following along with the video(4) give some meaning to my time or should i be more through woth the topics ?