It’s live! Direct link: 2024 Django Developers Survey. This is run in partnership with JetBrains, with them doing the bulk of the work to set up the survey and report on the results.
This year, we’re hoping to have the survey running for much less time, and have more answers . We got 4186 completed responses last year, so hope for 4500 in 2024. If you want to help out, here are relevant social media posts to boost:
I also was unable to enter alternative name for “task queue”.
We can think to share a preliminary version of the form as a test between all DSF members so that we can fix all the issues, before publish it, when will be too late to change things.
I filled the feedback form with a couple of suggestions.
I’ll share the survey form , but I’ll write other posts with the original URL and not the short ones we used in our posts for the motivation I already wrote on Discord and in the feedback form.
If you want to help out, here are relevant social media posts to boost:
I know that facebook is still pretty strong in Southeast Asia,
especially Thailand. So I took the liberty to post the announcement in
one of the groups I’m a member of.
For this question: “Which version of Django do you use for new projects?” it is a radio button for either 5.1 or LTS.
Our agency starts projects on both depending on the needs of the project. My personal preference is latest to get all the new features that make life easier, so I guess I’ll be putting that.
Edit likewise with the question “How often do you upgrade Django in your projects?” - it depends on the project.
I almost wonder whether there’s any real point in restricting responses to an exclusive option in surveys
There were a handful of things that were single choices that could have allowed multiple I feel, again because not all projects are alike.
I also thought not having uv in the Python / virtualenv management questions was a bit of an oversight given its overwhelming adoption over the last half year or so, and while Ruff was an option as a linter, it should also have been an option for the formatter.
However, for positive feedback: really like that we were explicitly asked about type hints and other features.
I haven’t done the survey yet, but that screenshot looks like leading the witness.
Update: OK, I’ve done it. Several of the questions struck me as pushing a particular agenda — Django needs more features, certain things should be included, typing should be added. Independently of whether I share those opinions, the wording is likely to skew the results, but make them invalid in demonstrating anything… Grrrr
The give a concrete example, phrasing as Are there features that you think should be added to Django? Followed by ≈ Are there ecosystem packages that serve this need for you currently? (with similar for removals… flatpages, anyone?) would provide a much more neutral framing.
In general, I found the survey’s questions or reply-options confusing. I found leading questions, or limiting reply option (single choice when it should have been multiple choice).
I also found it too long. I started the survey on my phone and got interrupted after like 5-7 minutes not even being half-way through. I lost all progress and did not bother restarting the survey. I can imagine that there are many more people that didn’t complete the survey because of the sheer amount of questions asked, possibly introducing a lot of bias. (Saying that as a layman).
. We got 4186 completed responses last year, so hope for 4500 in 2024. If you want to help out, here are relevant social media posts to boost:
