I would try to structure your learning path a bit more. So if web dev is something you really want to pick up, I would start at the basics. Learn the frontend part (html/css & JavaScript) If you want to keep using python that’s fine as you already have a clear understanding of it. But I wouldn’t follow a tool (django) but rather learn how to setup some sort of backend with python with flask? So basically your focus (maybe) could be to start with frontend, move to familiarising yourself with JS frameworks(how to build a blog, with a js backend) Afterwards start working on the backend side using python But mostly importantly is to figure out how much time you want to spend on learning all this (per week), hyperfocus is really important to not “lose faith” More on reddit.com

https://www.theodinproject.com/ This is probably the best full stack from nothing tutorial And please don't use chat gpt More on reddit.com

Personally, I just found random YouTubers that explained things simply and concisely and learned things piecemeal as needed. I learned 10x from trying to build my own projects then I ever did from any course material/tutorials. I've been using Python for about 7 years now and consider myself pretty decent at it. Ymmv. More on reddit.com

Take a breath. Don’t overwhelm yourself by thinking you have to become an expert in everything. You really just have to know enough to get your foot in the door as a junior software engineer. Then you pick up the rest as you go. I’m a cloud engineer of a few years at a large, well known company. I’m not an expert in React, JS, or anything really (yes, not even Python). And neither are my teammates who are more senior than me. Often times, front-end is an afterthought and just strung together enough to make it work. What you’ll need to be successful skill wise will vary by company, but here’s what I’d recommend you start with: One Python Course We recommend CS50, MOOC.fi, and Python Crash Course the most often here. None of them are better than the others, just different styles of teaching the same things, so pick the one that works for your learning style. Practice 5-7 days per week for an hour a day. Review the previous days learnings for 15 minutes at the start of each learning session. Do all of the exercises and code alongside the course. Git This is used by every software engineer at every company. It can be learned in an afternoon. Don’t worry about all of the edge commands. The basic ones are: git add, git commit, git push, git pull, git branch, and git merge. Use it all the time to store your code in GitHub. One Cloud provider AWS is the most common I’ve seen. Azure and Google Cloud less so. Pick up a practitioner (beginner level) cert to become familiar with the basics of the core cloud services. This is really just a vocab test for the most part and can be studied for in a few weeks. After you have learned these three, put together a couple basic projects using all of them to establish a simple portfolio to show them off. If you need ideas, come back here after. In the mean time, try to get a non-technical job in IT at a large company. There are actually lots of them in the form of governance, ITIL, project managers, operations, and so forth. Use this time to network and get to know the business so when it’s time to jump to an engineering job, you know people and have company knowledge. It may take a year or two, but you’ll get there. This route will prove much easier than cold applying to companies you don’t work at. More on reddit.com