Yes, if you attempt to use Django like you'd use your typical Java, Swift, C#, or Objective-C framework, you're not going to have a good time.

I've seen the horrors Java devs start doing on a Python project when trying to "fix" things, where by "fix" they mean use patterns they had to in previous gigs.

It's a different world.

▲

DarkNova6 a day ago | parent [-]

Having basic defensive programming, some simple classes instead of dicts everywhere and avoiding n+1 is a "different world"?

▲

senko a day ago | parent [-]

Just asking these questions underscores lack of understanding how things are usually done in Django and Python in general.

In Django you'd typically use simple classes (models or forms, or even dataclasses nowadays) more than dicts everywhere; n+1 is trivially avoidable (as another sibling comment points out, and you also have multiple packages that autodetect such cases if you've missed them).

Python in general has a more "consenting adults" than "defensive programming" attitude (which doesn't mean exessive coupling or spaghetti, but the approach is different from the Java or C# mindset).

There's no one THE correct style of programming.

	▲	matsemann 16 hours ago \| parent [-]
		> Just asking these questions underscores lack of understanding how things are usually done in Django and Python in general. No, it doesn't. It's fair to criticize the consequences of this approach to coding.