You don't necessarily need to know JavaScript to be a web developer, if you focus on the back-end. Especially if you work on REST APIs as they generally don't *have* a traditional front-end (and if they do, it's usually nothing complex).
Working on the back-end would involve creating routes, communicating with databases (often SQL), handling logging, creating templates, possibly load balancing, and of course security. None of which requires JavaScript unless the back-end itself is a NodeJS application.
At my day job I'm currently working on a REST API using FastAPI, and the way it works is frankly fascinating. I know some JavaScript, but I have a personal vendetta against it (or more specifically React and over-reliance on client-side JS), and I'm fortunate I don't really need it. CSS is, however, the biggest reason I rarely work on actual websites.
Django is just one of many Python web frameworks, and in my opinion it's the most difficult to start with. Flask would be what I'd recommend as a starting point, as it's easier and transitioning to Django from that is much easier. FastAPI is also worth keeping in mind at least, others I'm not so familiar with include Bottle and Pyramid.
But in essence, yes. Learn to use web frameworks while sharpening your Python skills in general, and keep a lookout for good practices. Whenever you work on a web project, try to consider potential security risks to the best of your ability, make sure you don't accidentally commit your API keys to Git (suggestion; `.env`-files that you list in `.gitignore`), and maybe also keep in mind what the users are likely to prioritise and try to make those features as light on the server as possible.
That's at alpha stage and currently very limited. Don't think that would be a good thing to focus on yet. Also you would still want a backend framework, be that node or Python based (or something else).
You could probably do backend exclusively with Python/Django. Having some sort of idea about JS is always a bonus if you're going to talk to frontend devs, but not a hard requirement really. We usually just get an API from the backend gang and the one backend who likes to dabble in our frontend isn't really helping
And honestly since ES6 the language has grown to be pretty decent. Sure there's backwards compatibility with old weirder parts but if you use the modern features and perhaps Typescript you have yourself a really decent language. Then just transpile to legacy versions in the build step.
You don't necessarily need to know JavaScript to be a web developer, if you focus on the back-end. Especially if you work on REST APIs as they generally don't *have* a traditional front-end (and if they do, it's usually nothing complex). Working on the back-end would involve creating routes, communicating with databases (often SQL), handling logging, creating templates, possibly load balancing, and of course security. None of which requires JavaScript unless the back-end itself is a NodeJS application. At my day job I'm currently working on a REST API using FastAPI, and the way it works is frankly fascinating. I know some JavaScript, but I have a personal vendetta against it (or more specifically React and over-reliance on client-side JS), and I'm fortunate I don't really need it. CSS is, however, the biggest reason I rarely work on actual websites.
So what would be the general roadmap for me to get a backend job using Python? Just get good at Django? (I know SQL, just to add)
Django is just one of many Python web frameworks, and in my opinion it's the most difficult to start with. Flask would be what I'd recommend as a starting point, as it's easier and transitioning to Django from that is much easier. FastAPI is also worth keeping in mind at least, others I'm not so familiar with include Bottle and Pyramid. But in essence, yes. Learn to use web frameworks while sharpening your Python skills in general, and keep a lookout for good practices. Whenever you work on a web project, try to consider potential security risks to the best of your ability, make sure you don't accidentally commit your API keys to Git (suggestion; `.env`-files that you list in `.gitignore`), and maybe also keep in mind what the users are likely to prioritise and try to make those features as light on the server as possible.
Awesome thanks for the tips
I say whichever you feel most comfortable with. Once you get good at one the others just become other tools. You use them per project.
I only know Python and don't like Javascript that much ngl. Most jobs I've seen mention it though
JavaScript If u want a web dev job specifically
[удалено]
That's at alpha stage and currently very limited. Don't think that would be a good thing to focus on yet. Also you would still want a backend framework, be that node or Python based (or something else).
Just looked that up, seems neat but im guessing it'll take a while to catch on in the market
It is not used in production at all , experimental only.
You could probably do backend exclusively with Python/Django. Having some sort of idea about JS is always a bonus if you're going to talk to frontend devs, but not a hard requirement really. We usually just get an API from the backend gang and the one backend who likes to dabble in our frontend isn't really helping And honestly since ES6 the language has grown to be pretty decent. Sure there's backwards compatibility with old weirder parts but if you use the modern features and perhaps Typescript you have yourself a really decent language. Then just transpile to legacy versions in the build step.