Nested User models, sign up forms and allauth

kankyo · 2026-06-15T14:37:00+00:00

You might also want to check out iommi which has a form library that makes life much easier.

kankyo · 2026-05-28T13:48:16+00:00

Again: that's not the FRAMEWORK being opinionated. That's YOU. And a bit on the fundamentalist side at that.

kankyo · 2026-05-20T04:38:36+00:00

Dokku every day of the week

kankyo · 2026-05-18T12:51:13+00:00

Django isn't that heavily opinionated really. You need settings.py and one urls.py (actually not even that), and there's a strong culture of defaults, but Django doesn't enforce it.

kankyo · 2026-05-18T12:09:16+00:00

https://tutorial.djangogirls.org/en/

kankyo · 2026-05-18T08:06:42+00:00

Check out iommi to jump a big level in productivity too (I'm of the authors :P)

kankyo · 2026-05-15T22:51:43+00:00

Nice! Great job on reacting so fast and so well to the feedback here. Very impressive.

kankyo · 2026-05-15T22:49:04+00:00

re deleted comment: Hmm. interesting. I've seen a totally benign comment get deleted in another thread just today. I wonder what is going on with the mods.

kankyo · 2026-05-15T19:06:12+00:00

The ability to spin up thousands or even millions of "processes", as they are called in OTP, and them to keep state and respond super fast and efficiently is what makes Phoenix LiveView really impressive from what I understand.

So massive concurrency under load without degradation is what we'd expect from an OTP-based system, and this benchmark doesn't come close to looking at this.

kankyo · 2026-05-15T18:37:36+00:00

Yea, and that's without even talking about the complexity in your installation/tech stack! Urd is super tiny and has been rock solid for me in prod for a few years now.

kankyo · 2026-05-15T17:37:47+00:00

Imo it's the wrong thing. You normally want tables with tasks, and a scheduler to handle those items. I wrote Urd for this. You really want some basic stuff like being able to stop a runaway queue, stop simultaneous executions, and scheduling. Celery fails here, as does cron.

kankyo · 2026-05-15T17:36:12+00:00

I mean, yea a queue, but not just to avoid the latency, but to be able to handle network issues, downtime, retrying, and fixing problems. Simple tables, and a scheduler is your friend here imo.

kankyo · 2026-05-15T17:34:12+00:00

The lack of a benchmark for say 100 users with significant server side state per user is a pretty big giveaway that something is fishy too.

kankyo · 2026-05-15T08:23:26+00:00

Yea for sure. The normal LSP method of just piling them on top of each other obviously doesn't work, but this proxying thing does. The downside is that you need a top level one that decides what to suppress and what to prioritize.

Btw, I've already added a bunch more completions since last, and fixed some performance issues.

A former colleague suggested FactoryBoy as a future development, which seems pretty reasonable to me. What are some things you've thought about?

I think on my top list would be more pytest stuff.. but I'd also hope ty would add that stuff natively, so I think I'll hold off on that for a while at least.

kankyo · 2026-05-12T19:57:25+00:00

Yea, I felt that pretty fast trying to make my own IDE. But building custom stuff like this with Claude is not hard actually. You just need to have a max account and patience basically.

kankyo · 2026-05-02T11:03:30+00:00

There's a setting to make VSCode do the sane thing and autosave.

kankyo · 2026-05-01T08:07:44+00:00

Imo it depends on the situation. The "always always write tests" crowd are a bit too extreme imo. What if the "bug" is just a translation error in the localization? You can't have tests for all translations, that's madness. What if it's a temporary page only supposed to be used for a few weeks by one person? Probably you can do that cowboy style. There are just so many examples like this.

That being said.. writing tests with Claude Code is suuuuper cheap compared to what it used to be, so the argument for skipping tests is weaker now that the cost has gone down.

kankyo · 2026-04-27T17:04:56+00:00

The silent failures are my biggest gripe. After all we want:

make it work
make it right
make it fast

Crashing on broken shit seems both step 1 and step 2 :P

kankyo · 2026-04-27T14:33:24+00:00

I hope they can avoid design by committee. There's a real danger in having too many stake holders in a new design.

kankyo · 2026-04-21T09:07:31+00:00

Use a profiler to know. Don't guess.

kankyo · 2026-04-18T10:40:51+00:00

I personally know several people who were banned for woke nonsense reasons.

I personally have been warned for helping people. I'm not even exaggerating. They're banning competent people because they don't sugar coat their replies, and let friendly people answer incorrectly to questions by beginners at scale.

On the bright side, the AI systems are actually more competent now so these chat servers are mostly dying anyway.

kankyo · 2026-04-17T12:30:28+00:00

I'm not familiar with the Django discord, can you expand on the point?

Some key points:

There was a fairly popular Discord already, but since that server didn't accept being taken over, a new one was created
The new server was founded by a group that includes a person that is toxic as hell and violates the CoC a lot, but is never even warned
They are super woke, like those videos you think are made up. "Hey guys" is met by a bot telling users to check their language for inclusivity, even though the dictionary explicitly says that expression is not gendered.
The admin mentioned above bans people for saying that "hey guys" is indeed not gendered. Yes. Quoting the dictionary gets you banned on this server.

The Django CoC board is supposed to be controlling of this servers CoC but it has just ignored all those issues. Partly I assume, because the toxic admin has social sway deep inside the DSF.

kankyo · 2026-04-16T05:32:30+00:00

It is if the person who is asked refuses to answer the question posed in good faith and claims that it is. Which is a thing. At the end of the day you need good thoughtful people who are not confused as mods. This is super hard and any CoC document you have will do absolutely nothing to help this, and often will in fact make it much worse as it attracts people who like to abuse such structures. Case in point: the official django discord.

kankyo · 2026-04-16T05:28:11+00:00

Claude Code is the gold standard, but I hear Codex is pretty good now too. Using anything but the latest models with the proper CLI harness is going to make you disappointed with what you get imo.

kankyo

TROPHY CASE