add explanation for the problem with atomic

[Amy-Franz]

No description provided.

[meshy]

Thank you! I'm going to apply a few further changes just before merging:

[meshy]

This sounds a little internal, so perhaps should be:

Suggested change

	1. We create savepoints with decorators. *Linting for this is possible, but each existing case requires investigation.*
	1. Indicating "this should be atomic" is often done by decorating functions with `atomic`.

[samueljsb]

Personally I think we can just simplify this:

Suggested change

	1. We create savepoints with decorators. *Linting for this is possible, but each existing case requires investigation.*
	1. Savepoints are created with decorators (`@atomic`).

That point probably requires a bit of explanation, but we can add that when we revise this.

[samueljsb]

I think this has got a bit mixed up in formatting.

Suggested change

	## Problems
	1. Django's atomic creates many savepoints that are never used. There are a couple of main causes:
	1. We create savepoints with decorators. *Linting for this is possible, but each existing case requires investigation.*
	2. `atomic` creates savepoints by default. The default arguments (*Behaviour* **A**) are an [attractive nuisance](https://blog.ganssle.io/articles/2023/01/attractive-nuisances.html) because they make us create savepoints when we don't need them.
	> … if you have two ways to accomplish a task and one is a simple way that *looks* like the right thing but is subtly wrong, and the other is correct but
	more complicated, the majority of people will end up doing the wrong
	thing.
	— [**Attractive nuisances in software design](https://blog.ganssle.io/articles/2023/01/attractive-nuisances.html) -** [Paul Ganssle](https://blog.ganssle.io/author/paul-ganssle.html)
	>
	3. We have no easy way to indicate the creation of a savepoint that doesn't have the potential to create a transaction instead. The only tool we have to create a savepoint is *Behaviour* **A**, which can create a transaction.
	## Problems
	Django's atomic creates many savepoints that are never used. There are a couple of main causes:
	1. We create savepoints with decorators. *Linting for this is possible, but each existing case requires investigation.*
	2. `atomic` creates savepoints by default. The default arguments (*Behaviour* **A**) are an [attractive nuisance](https://blog.ganssle.io/articles/2023/01/attractive-nuisances.html) because they make us create savepoints when we don't need them.
	> … if you have two ways to accomplish a task and one is a simple way that *looks* like the right thing but is subtly wrong, and the other is correct but
	more complicated, the majority of people will end up doing the wrong
	thing.
	— [**Attractive nuisances in software design](https://blog.ganssle.io/articles/2023/01/attractive-nuisances.html) -** [Paul Ganssle](https://blog.ganssle.io/author/paul-ganssle.html)
	>
	3. We have no easy way to indicate the creation of a savepoint that doesn't have the potential to create a transaction instead. The only tool we have to create a savepoint is *Behaviour* **A**, which can create a transaction.

[samueljsb]

Personally I think we can just simplify this:

Suggested change

	1. We create savepoints with decorators. *Linting for this is possible, but each existing case requires investigation.*
	1. Savepoints are created with decorators (`@atomic`).

That point probably requires a bit of explanation, but we can add that when we revise this.

[samueljsb]

The formatting has gone a bit wrong here, perhaps an artefact of copying from Notion?

Suggested change

	— [**Attractive nuisances in software design](https://blog.ganssle.io/articles/2023/01/attractive-nuisances.html) -** [Paul Ganssle](https://blog.ganssle.io/author/paul-ganssle.html)
	— [**Attractive nuisances in software design**](https://blog.ganssle.io/articles/2023/01/attractive-nuisances.html) - [Paul Ganssle](https://blog.ganssle.io/author/paul-ganssle.html)