Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/qfutukmy/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/qfutukmy/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/qfutukmy/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/qfutukmy/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/qfutukmy/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/qfutukmy/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/qfutukmy/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/qfutukmy/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/qfutukmy/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home4/qfutukmy/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Multi-book series – Gillian Andrews
tablet, hands, keep-1632909.jpg

Multi-book series

stamp, banner, business-895383.jpg

I am politely declining long, multi-book series

Just recently I have come across so many authors who decide to make more money from 21 books of 50,000 words rather than 7 books of 150,000 words.  And it really annoys me.  It feels like a way to ‘milk’ the reader.  Yes, you get a loss leader, with the first book probably permafree, but then the reader is faced with 20 further books that the author expects you to buy.  And I really, really don’t want cliffhangers in the next 19 novels to tempt me into buying the next in series.

I don’t mind up to seven books in one series.  (I have to say that because my own longest series, the Ammonite Galaxy was that.  It took me eight years to write and each book was a reasonable length, I think.  I hope.).

I often look at the free kindle bestseller lists, here:

https://www.amazon.com/Best-Sellers-Kindle-Store/zgbs/digital-text

to find new and interesting authors I haven’t heard of before.  I have found some great ones (and lots of not so great ones, too, but hey, they are free.  It’s easy just to stop reading, right?).

So now, apart from filtering by number of stars, I am careful always to look and see how many books there are in the series.  Up to seven?  Fine, I’ll give it a go.  Over seven? Not a chance.  After all, it only took Harry Potter seven books for all his adventures.  Who needs more?

books, stack, learn-1015595.jpg

So I will vacuum up your standalones, your duologies, your trilogies, your tetralogies, your pentalogies, your hexologies, your heptalogies.  But not your nonodecologies or your icosologies.  Enough is enough!

I make exceptions for Janet Evanovich and Michael Connelly, though reluctantly.  I still think they could have tied it all up in seven books.

For the rest of the world …

…the finger paused, didn’t click, and moved on.