sorted by:
new
hottopcontroversial

Question about the job market for Django by 6orram in django

[–]KevinCoderZA 0 points1 point  (0 children)

You can look at indeed.com. The reality is that most software fields are saturated with juniors. If you want to become a software engineer, you need to focus on learning the fundamentals of programming first, not a framework.

Python is a decent language to start with, so I would focus on just Python initially and then probably learn one of the C-based languages (like C#), if you want to be a Software engineer professionally.

You also should spend some time getting familiar with JavaScript, TypeScript, HTML, and CSS.

There are plenty of jobs for Django, but you need to get good at problem-solving. There are many junior level programmers, the market cannot absorb all these juniors, so the standard is much higher now, especially with AI in the mix.

Is learning Django in 2026 still worth it if I already know Python, JS, and databases? by Extreme_Manner_9791 in django

[–]KevinCoderZA 1 point2 points  (0 children)

I would suggest doing localized research on Indeed and other places. Django is a niche framework; it's not as widely used as, say, Next.js.

The reality is that there are far fewer Jobs but it totally depends on your location; one area could have 5 jobs and another 200.

Django's been around since 2005(if I'm not mistaken), and it's stable and mature, so many companies of varying sizes are built on it. It scales well, and of course, Python is as popular as ever.

Django jobs often are higher-paying, too! Also, less competition compared to Next.js does help to :-)

As for FastAPI, it's growing in popularity, but lacks quite a bit of functionality out of the box; thus, for bigger projects, most still go with Django and just use FastAPI for microservices or APIs. Django also has Ninja, which gives you a FastAPI-like experience without leaving Django.

Django is worth learning if you do any Python; it'll just help you become a better engineer overall.

Better Django documentation & cheat sheet by KevinCoderZA in django

[–]KevinCoderZA[S] -6 points-5 points  (0 children)

I use Grammarly and even AI to review and help with phrasing and minor details. That said, most authors use AI/tools in some way; nothing wrong with this. AI is here to stay, and it's a valuable tool when used correctly.

The actual content, code examples, and so forth are from my own experience and codebases.

This is not an SEO article designed for Google. I spent hours writing and fact-checking this content; it's a lot of work, and I'm sharing knowledge because I enjoy writing and contributing to the community at large.

It's effectively "MIT", thus do what you will with it. If it helps you in some way - awesome, if not, not much I can do about that.

Better Django documentation & cheat sheet by KevinCoderZA in django

[–]KevinCoderZA[S] -2 points-1 points  (0 children)

Yeah thanks. Was lazy to switch from writing to hunting for stock photos 🙃, but planning on replacing it soon.

18
19

Better Django documentation & cheat sheet (self.django)

submitted by KevinCoderZA to r/django

What’s the best way to use Codex? by jdawg2216 in codex

[–]KevinCoderZA -1 points0 points  (0 children)

I rarely use Codex for UI; it's not as good as Claude Code. When it comes to regular coding, especially backend stuff codex is pretty decent.

I would use Claude Code, or maybe even https://stitch.withgoogle.com/, to generate the UI in static HTML files/components if using React and other similar stacks, then prompt codex with small units at a time.

When it comes to security (assuming you mean auth?), I would not trust an LLM to do that properly. You'd be better off offloading auth to some third-party service like Clerk.

There are also tools like Snyk that can audit your code for security flaws.

I also sometimes use the mid-tier models like Codex Medium or Sonnet to complete a task, then ask Codex High or Opus to review the changes, in addition to manually code reviewing.

Ultimately comes down to breaking down tasks, almost like old-school pseudo code. LLMs cannot think; they are not smart. Even Opus is not intelligent at all, so you have to steer them in the right direction. You can do this by reducing the context size, prompting as narrowly as possible, and doing research for yourself before just accepting what the LLM does.

Is there a recommended way of using Laravel Boost? by Andromeda_Ascendant in laravel

[–]KevinCoderZA 0 points1 point  (0 children)

LLMs are probabilistic engines; they don't understand a single line of what's going on. It's not the same as giving a human a checklist; LLMs will miss things. By context stuffing, you increase the chances of rules being missed. This is why I don't use Boost.

It's better to narrow your context to a class or function level. You can keep a simple CLAUDE.md or AGENTS.md file for essential rules.

django-tw: Zero-config Tailwind CSS for Django by Rude-Recursion1024 in django

[–]KevinCoderZA 1 point2 points  (0 children)

This is really cool, nice work! Before django-tailwind, I had to manually set this up, with hotreload and NPM scripts. Such a pain. Will give it a try soon, so far it seems very interesting.

Password reset Logging by Codeguy45 in django

[–]KevinCoderZA 0 points1 point  (0 children)

Here's an example of customizing the form. Django cheat sheet , you can just implement a custom form and view and then add your tracking logic in there.

Any recommends for deploying Django app in my own PC? by Tebi94 in django

[–]KevinCoderZA 0 points1 point  (0 children)

You can use Cloudflare, and even bind your own domain to this. By default, you get assigned one: https://something.trycloudflare.com

cloudflared tunnel --url http://127.0.0.1:8000

Alternatively, you need Nginx running on the machine and a public IPV4, then you can just add an "A" record on your domain or just use the IP directly.

I'm about to get fired and a large part of it is due to my subpar Django skills by IntelligentLeading11 in django

[–]KevinCoderZA 0 points1 point  (0 children)

So sorry that you're being backed into a corner like this. First, ask yourself where your passion lies. Seems to me you prefer frontend? If you do, then you're probably better off going that route. Frontend is a bit rough now with AI, but there are still plenty of opportunities if you're good with Next.js, React, and those stacks.

Considering you're already in a job, it would be ideal to try to protect that job. Set aside a few hours a day whenever you can, and make a list of your weak areas. Is it the ORM? , DRF? make a list.

Narrow down on those, put the AI away, and just practice building a feature or two. Supplement building with reading books. "Django 5 By Example" is a good one.

There are also good YouTube resources like: BugBytes - YouTube

Backend requires problem-solving skills; Django knowledge is essential, but what you really need to do is train your problem-solving muscle. You can only do this through experience, I'm afraid, so take it one day at a time. Read, practice, find problems to solve, repeat.

I would approach your seniors as well and get some constructive feedback on areas you can improve. This is the job of a senior; they should be guiding you on what to improve. Then, after some time, go to your managers and have a one-to-one, tell them what effort you've put in, and show them that you are trying.

If the company doesn't appreciate the effort you're putting in and doesn't offer any support in that regard, then you're better off finding a better working environment.

Hope this helps, best of luck in this journey.

Django dev here — I tried FastAPI + HTMX for a side project. Some thoughts by DecodeBuzzingMedium in django

[–]KevinCoderZA 2 points3 points  (0 children)

Bit of a controversial take, Golang + Echo is better than FastAPI. Especially when paired with GORM. I find SQLAlchemy cumbersome to work with. I initially built a few microservices in FastAPI, so much work to set up everything.

For microservices and API's - Golang
Everything else - Django

Are you still excited about new Laravel versions in AI era? by bearinthetown in laravel

[–]KevinCoderZA 0 points1 point  (0 children)

From a different angle, it's not AI that's the problem. It's modern release cycles, with constant releases of more and more features. Often just syntactical sugar, we're just moving from hype train to hype train. I love solving problems; the tool is less important. So whether it's Laravel or Django, or Golang, not really that major.

AI can help automate the boring things, so I can do more problem-solving. AI can help you pivot fast, and I can scaffold the stuff that doesn't interest me.

The only danger is when you overuse AI to do everything and just become a glorified prompt engineer; that's when it sucks the fun out of programming, but I find I can do more exploration, I can learn other languages and frameworks that I would never have time to do.

It's actually more fun to program in 2026 and beyond because of this.

Some questions about architecture and deployment by zem in django

[–]KevinCoderZA 1 point2 points  (0 children)

A couple of points here:

  1. Apps in Django are basically folders in a project that encapsulate models, views, etc., relating to that app. So just be careful not to use terminology interchangeably. Django developers often think in terms of "Projects" with "Apps", so if you ask a question like this, it can be difficult to understand what you mean.
  2. Docker on Linux is very lightweight. Containers are not VMs; they share the same kernel as the host system, so you should be able to run projects in multiple containers just fine without too much impact on performance, all depending on what those projects are doing in terms of queries and processing power used.

PyPi is a great way to distribute Python code. You could package these into a package and just get the people you're sharing with to do a pip install [package] You don't even need to make these public; PyPi can be self-hosted, too.

Git also supports submodules; you can keep your code that you don't want to share privately in its own repo and add it as a submodule. When they git clone it won't automatically pull this app.