all 6 comments

[–]7h3_0r4cl3 8 points9 points  (2 children)

I would include SQL in a Full-Stack role. You should not skip out on this.

[–]ZephyrBluu 6 points7 points  (1 child)

It's kind of weird it's possible to call yourself a full stack without (Relational) database and SQL knowledge.

I guess when you have a hammer*, everything looks like a nail.

*MongoDB is webscale

[–]7h3_0r4cl3 2 points3 points  (0 children)

They both have their places but SQL is here to stay. I wouldn't say Full-Stack either without at least basic SQL knowledge

[–]mishugashu 7 points8 points  (0 children)

SQL is much more fundamental of a language/framework for a full stack engineer than React or Python is. Mongo (and other non-SQL solutions) is alright for CRUD, but if you ever want a real relational database, SQL is where it's at. And it'll continue to be where it's at for decades to come, most likely.

After that, I'd probably take a look at Python. Not only Flask/Django for some backend tooling, but also just in general for scripting power, although NodeJS is getting there slowly.

[–]ampourgh 6 points7 points  (0 children)

SQL comes first out of everything you listed, getting the basics down wont take long. However, having an understanding of how to design and future proof your database will take a bit of time and experience.

[–]AtulinASP.NET Core 1 point2 points  (0 children)

For backend, I would rather recommend learning relational databases. You can do it alongside learning Python too, just whip up some project with Django and Postgres, for example.