@mahryekuh Well, I’m old… when I began, there were only basics… the frameworks came later. But that describes everybody who got into the industry later AND tried make a living, in the face of competition, low rates, and the grinding demands of economic determinism. Folks need to get a job.
In that context, “basics” are levelling up. Foundations?
Presented like that, it might not get folks feeling defensive.
I recall many a grey beard making me feel bad as a junior for stuff I didn’t yet know.
@mahryekuh maybe there’s a real need for basic accessibility topics to be presented in a developer focused manner. 
I know this stuff has lots on it already, but that doesn’t seem to be getting across, hence the complaint in the first place.
@mahryekuh @jscholes there are many Django tutorials. Always room for one more. Likewise here I’d imagine.
@mahryekuh sorry 
@mahryekuh BLOG POST BLOG POST BLOG POST BLOG POST BLOG POST BLOG POST! 
@mahryekuh I don’t think I’m saying anything in that direction 
@mahryekuh But massive +1 to boosting our recognition of non-code contributions! (Long-burning topic, I'm not sure how much progress we're making on...)
@mahryekuh Sure! 
I meant as a **mental exercise** only. If I **imagine** that I can't change the code, what then?
@mahryekuh thanks Marijke l, yes, I think I agree. Mentally we could ask what we’d do if technically Django were frozen? How would we advance it then?
Obvs we’ll keep advancing, but I think the answer to that is where the low hanging fruit really is. (Sometimes the **if only we had X new feature** is catnip)
A little late because it was the kids' birthday yesterday, this month's Stack Report, some thoughts on Django Core.
https://buttondown.com/carlton/archive/thoughts-on-djangos-core/ #Django #TheStackReport
@jacob @simon @bmispelon wonder it there’s a market for a Claude wrapper that has “don’t use React” in the system prompt? 
@jacob @bmispelon I’m sure @simon could knock you one up with an AI while he's walking the dog 
@mahryekuh I think that would make an interesting discussion, especially thinking about progressive enhancement there. Zero, Some, More JS versions, say. 🧐
> The "Delete" checkbox is one sore point out of the box, as it gives little indication of which row is up for deletion.
The default markup could be improved right? 
@mahryekuh @CodenameTim With you almost to the end there 
@mahryekuh @CodenameTim Having said that, I acknowledge there's an amount of cruft in there, and a massive lack of decent How-Tos, so Formsets are also on the list for my "Modern Django Forms" piece, when I actually get to write that. 🫠
2/2 
@mahryekuh @CodenameTim Ha! Good! That's a stonking question! 
So, on the record, I love formsets, I use them all the time — ANY time I multiple forms to handle in a view. I do horrible things like create custom formsets to handle multiple form types when that's needed, and I think they offer a clean API (to the client, not necessarily the writer) that hides a lot of rubbish.
1/2
@CodenameTim @mahryekuh They're just a list of forms, asking you to love them 🥰
@mahryekuh Formsets are Django’s misunderstood middle child. 🥳
@mahryekuh Go @thibaudcolas Go! 🦸
