Maaz Ahmad’s Post

Decoupling logic in Django is always an interesting architectural challenge. Recently, I’ve been relying more on Django Signals to keep my models clean and enforce a strict separation of concerns. For those who haven't dug into how they work under the hood: Django signals essentially implement the Observer design pattern. There is a central dispatcher, when a specific action occurs in the application (the sender), the dispatcher routes that event to any function "listening" for it (the receiver), allowing them to execute their own logic independently. In the snippet below, I’m using the post_save signal. Whenever a new Student instance is successfully created, this receiver catches the signal and automatically generates a CreditWallet for them. Why use a signal here instead of just overriding the save() method on the Student model? It comes down to encapsulation. Overriding save() works fine for simple apps, but as a project grows, it can lead to massive, bloated models. By using signals, the Student model remains strictly responsible for student data, while the financial/wallet logic is encapsulated in its own domain. It makes the codebase much easier to maintain, scale, and test. I’m curious to hear from other developers on here: What is the most complex, creative, or technically challenging way you have utilized Django signals in a project? I'd love to learn from your experiences! #Django #Python #SoftwareEngineering #WebDevelopment #Architecture #Coding

Understanding Django became much easier once I learned this 🔍 When I first started with Django, everything felt confusing… But one concept changed everything: 👉 Django follows the MVT architecture (Model–View–Template) Here’s how I now see it: ✔ Model → Handles database (data) ✔ View → Contains logic (what to do) ✔ Template → Handles UI (what user sees) Once I understood this flow, building projects became much more structured and easier. Still learning and improving every day 🚀 What was the concept that made Django click for you? 👇 #Django #Python #WebDevelopment #Backend #Learning

A Python package to clean Django project junk and free space. Over time, my projects kept filling up with things I don’t actually need… __pycache__, .pyc files, logs, staticfiles, even old virtual environments. Cleaning them manually every time was just… annoying 😅 So I made something simple to handle it. 🧹 Django Cleaner It scans your folders, detects Django projects automatically, and removes all the unnecessary stuff safely — without touching your actual code. You just run: django-cleaner ~/Projects and it does the rest. What it handles: • Removes __pycache__ and .pyc files • Cleans logs and staticfiles • Optional removal of venv • Shows how much space you freed I kept it simple on purpose. No setup, no complexity — just something useful that works. Published it on PyPI 📦 🔗 https://lnkd.in/gSvj5U3Y Code on GitHub 👇 🔗 https://lnkd.in/gNur8fN3 This is one of those small things that actually makes working on multiple projects easier. If you use Django, it might help you too. #Python #Django #OpenSource #BuildInPublic #SoftwareDevelopment #BackendDevelopment #DeveloperTools #Programming #Tech #CleanCode #Productivity #CodingLife

Devlog Day 30 Today I revisited a question "Two Sum II" which is a very simple problem until you know the approach. The difference between Two Sum and Two Sum II is in Two Sum II the array is sorted and you have to solve the problem with O(n) TC and O(1) SC. Using two pointer approach you can solve this question. In brute force we use nested loops which loops through entire array to check if the sum of nums[i] and nums[j] equals to target. Else continue. It takes O(n2) TC and O(1) SC as we are not using any extra space for solution. In better approach we use two pointers by taking advantage of sorted order of array. We start from first and last pointer and check if the sum of them equals to target. If the sum is less we move left pointer else right. The problem in itself is not that hard but I am started analysing the pattern of such questions like if you have sorted array and want to find any element or perform any operation it is most likely targetting binary search and two pointers. Anyways later I continued my django course and today I learnt static files handling when your code is in production and even wrote a command script. Django lets you write your own command and you can access that command using python manage.py <command_name>. It really helps when you are containerizing your code and want to automate some processes like fetching static files from third party cdn and load it in locally so you dont have to request api for every reload. #DevLog #BuildInPublic #DSA #NeetCode #Stack #LearningInPublic #IndieHacker #WebDevelopment #Django #Coding #Development #Explore

Day 2/7 – Django Projects Challenge 🚀 Today’s project was a Student Record Management System built with Django. This project was especially useful because it helped me understand something very important in backend development: 👉 How real-world data is connected and managed ✅ Features implemented: Student management Course management Marks management Student detail view Search and filter functionality 📚 Concepts I strengthened: Django models ForeignKey relationships Django ORM CRUD operations Template rendering with related data What I liked most about this project is that it was not just about creating pages — it actually helped me think more about database design and backend logic. Step by step, this challenge is helping me become more confident with Django through hands-on practice. Excited for Day 3 🚀 Github Link => https://lnkd.in/gU5tx-mZ #Django #Python #BackendDeveloper #WebDevelopment #Programming #SoftwareEngineering #BuildInPublic #LearningJourney #DeveloperJourney #TechProjects

I kept writing Django APIs… but something felt off. The code was working. Responses were coming. But if someone asked me: 👉 “What actually happens when a request hits your API?” …I didn’t have a clear answer. That bothered me. So I went back to basics. Not tutorials. Not copying code. Just understanding one simple flow: User → request → view → model → database → response And suddenly, things started clicking: Patient.objects.all() is not just a line of code… it’s a query hitting the database and returning structured data. request is not just a parameter… it’s literally everything the user is sending to your backend. GET, POST, PUT, DELETE are not just methods… they define how your system behaves. The biggest realization? 👉 I was focusing on “how to write code” 👉 instead of “how things actually work” Now I approach backend differently: I don’t start with code. I start with flow. And that small shift is making a huge difference. Still learning. But now it feels real. #Django #BackendDevelopment #Python #LearningInPublic #SoftwareEngineering #BuildInPublic

🚀 Day 4 of my 7 Days Django Challenge Today I built CurioLog — Daily Curiosity Journal 🧠✨ It’s a Django-based journaling web app where users can store and organize: ideas questions observations experiments learning notes Instead of making a very basic project, I wanted to build something that feels more practical and meaningful. ✅ Features: User authentication Add / edit / delete entries Categories and tags Search and filters Dashboard analytics Monthly and category charts CSV export Responsive UI 🛠️ Tech Stack: Python, Django, Bootstrap 5, Chart.js, Pandas, SQLite 📚 What I learned: Django authentication CRUD operations Model relationships Search & filtering Dashboard logic Data visualization Exporting data This project gave me a much better understanding of how real-world Django apps can be structured beyond just forms and models. 🔗 GitHub: https://lnkd.in/ggTm7Hyc #Django #Python #WebDevelopment #FullStackDevelopment #BackendDevelopment #StudentDeveloper #Projects #LearningInPublic #GitHub #SoftwareDevelopment

💡 Imagine this... You send ₹1000 to your friend, money is deducted from your account… but your friend never receives it ❌ Scary right? This is where Django’s "transaction.atomic()" comes in 🔥 It ensures: ✅ Either all database operations succeed ❌ Or everything is rolled back When you wrap code inside transaction.atomic(): ✅ All database queries succeed → changes are saved ❌ Any error happens → everything is rolled back No partial updates. No broken data. That’s why I’m learning and using this in my Django projects 🚀 #django #python #backenddevelopment #webdevelopment #learning

Most developers do not fail at Django because the framework is difficult. They fail because they learn in fragments and try to build systems before understanding structure. Right now, I am revisiting Python fundamentals alongside Django with a different approach. Not rushing features. Not chasing projects. Rebuilding how backend systems actually behave from the ground up. For beginners, the mistake is usually the same. Too many tutorials, not enough structure. That is why starting with a guided introduction matters. A useful entry point is here: https://lnkd.in/dCUgNqjH w3schools.com W3Schools provides a simplified Django structure that helps you understand how projects are organized before you tackle complex system design. What matters most is not syntax. It is flowing. Request → Middleware → View → ORM → Database → Response If that chain is unclear, every advanced topic will feel random. If it is clear, Django becomes predictable and logical. At Teklini Technologies, this is the standard. Systems are not built around speed. They are built around clarity first, then scale, then performance. If you are learning Django or restarting your backend journey, stop collecting tutorials. Start mastering structure. What is the one Django concept that only made sense after you built something real? #Django #Python #BackendEngineering #WebDevelopment #SystemDesign #CleanArchitecture #CodingJourney #TekliniTechnologies

Understanding Django's .get_or_create() Pattern A pattern I see frequently misunderstood in Django codebases: This returns a tuple of (instance, boolean). The comma performs standard Python iterable unpacking—it's not Django-specific syntax. Common mistake: Treating the unpacked variables as a single unit. They're independent references. obj is a fully editable model instance, and created is simply a boolean indicating whether a new record was inserted. Practical application—handling placeholder records: Consider a ProjectMembership model where new clients are created with project=None as a placeholder. This pattern: Finds the existing placeholder if present Creates one if absent Updates the project reference in either case Result: The placeholder is upgraded rather than orphaned. No duplicate records. No cleanup required. Key takeaway: .get_or_create() followed by assignment provides atomic-like "get or upsert" semantics without race conditions that plague separate get-then-create logic. This protection only works if there's a database-level unique constraint on the lookup fields (or Django's unique_together in Meta). Without it, .get_or_create() still has a race condition window. The database constraint is what guarantees atomicity. #Django #Python #BackendEngineering #SoftwareDevelopment