My time at Lofty is coming to a premature end, and outside of my circumstances. If you're in need of a Senior Software Engineer with Data Engineering Skills in the US Remote CST zone, reach out and let's talk about any potential opportunities for work.
If you have a current colleague of mine that you are interviewing or considering offering, I'd be happy to vet and provide recommendations for all of them. #techjobs#jobs
So whats up with the doc note on Model.Meta.unique_together maybe being deprecated in favor of constraints in #django? Is this still an active conversation? Is the doc note still relevant?
For context, we've got some internal discussion around it and prefer unique_together style and would hate to see it go style wise.
@adamchainz@emattiza unique_together is intended to be removed, but it's tricky. Deprecating index_together has already been a big challenge so we want to catch our breath and see how many issue it causes. No rush 🧘
I got asked about using .save over .create in #django and wanted to put my thoughts down in some longer form about my experience. Anyone else using .full_clean and .save instead of .create? Are you a .create fan? How do you choose?
@valberg@nessita@tykling Hard topic, but from an UX POV I think .save() is too late to nicely communicate validation errors. This is way easier to handle at an explicit (forms) layer. And if we were to add validation to .save() one would by default do validation three times: first during forms, then during save (full_clean) and in the db (for constraints etc) when the data is actually committed. We can't get rid of the last one, but between forms & .save() I am for forms.
I hate seeing good colleagues leave, and this one really hurt. I just wasnt ready to feel so deflated after building someone up so much.
If you need a very strong backend #django, #graphql, #python and #react#typescript web developer, I know a guy, and we wrote some great, well tested, and typed code