What Django project ideas and tech stacks define beginner, intermediate, and advanced skill levels?

Using Django
1

Hi everyone,

I’ve built a few Django projects so far and I’m trying to figure out how to accurately gauge my current skill level, and what to build next to grow.

I’d love to get community input on the following:

  1. What kind of Django project (in terms of complexity and features) would be considered “beginner level”? What technologies/tools are typically enough at this stage?

  2. What separates an “intermediate” Django project from a beginner one? What additional technologies or practices (e.g., caching, background tasks, testing, deployment) should I start incorporating?

  3. What does an “advanced” or production-grade Django project typically look like? What’s the common tech stack used alongside Django at this level (e.g., Celery, Redis, Docker, CI/CD, microservices, etc.)?

If possible, it would be great to see specific example project ideas for each level, along with the recommended technologies to use.

Thanks in advance for any guidance!

2

Welcome @FaridunDev !

Personally, I wouldn’t grade or rank a Django project based upon the technologies being used.

A project that satisfies all requirements for that project is “production-grade”, regardless of how it’s built or deployed.

I’ve deployed Django projects that run on a Raspberry Pi, using runserver and sqllite. And because it fulfills every requirement for that system, I consider it as complete as any other project I’ve worked on.

Django ecosystem knowledge is not a linear slope or a straight-forward path. It’s a whole bunch of boxes where you either know the subject or not. The more boxes you can check off, the more complete your knowledge is.

However, not everyone is going to gain the knowledge in those boxes in the same order. There’s no specific sequence or set of prerequisites to learn along the way.

So rather than trying to somehow measure where you’re at, I’d suggest identifying the areas where you know your knowledge may be lacking, and identify ways you can learn about those topics - if it’s something that’s going to be useful to you.

3

Humm…
I don’t think the distinction is really about the number of models or lines of code. It’s more about the engineering practices and architectural decisions involved.