I'd find a way to make it cheap for you (in time and energy) to iterate such that the one-off content that you're providing can be used as stepping stones to a paragraph, and then a chapter, and then a book.
As an example, I've written thousands (!) of customer support messages, via email, chat, or reddit, to help my PhotoStructure beta users.
I've found that the second or third time I answer a question, either I need to fix the product so the question doesn't show up again, or I transcribe my response onto a new page on photostructure.com. In my case, it's just `hugo new content/faq/post.md` and then I dump the new content into the new page.
It doesn't have to be an elaborate post. Perhaps a bit more nuance or detail than my customer support reply, but not much more than that. Sometimes it's only 1 paragraph.
I've found that these "humble starts" can then be iterated on fairly easily, as inspiration comes to you.
As an example, according to git, I've made 15 commits to <https://photostructure.com/faq/library/>. The first iteration was just a handful of sentences I wrote as a response to what I meant by "library."
If the first step is too big or the end goal is too far, I cut the first step into smaller steps, and try to find a tempting intermediary goal.
Right now, I'm restoring an old motorcycle, and it's not going well. A bolt broke and I need to extract it from the engine I just reassembled.
My end goal now isn't to ride a shiny vintage bike, it's just to get it running. The first step isn't to extract the broken bolt, it's to open the engine again, a ten minute job.
Start small, set reasonable goals, and be careful about premature optimisation.
Start working on something small and easy that's related to the thing you're actually trying to accomplish, and that'll help swap the broader context into your head that you need to work on the larger problem.
Break the larger problem down into tiny little pieces that are easy to accomplish. Put them in a list. Pick off the easy items first each time you're trying to get started.
That’s really interesting, I’m the opposite where starting on things is easy but pulling through to the end and actually making a finished product is tough. I wonder if there’s a word for that.
I'd find a way to make it cheap for you (in time and energy) to iterate such that the one-off content that you're providing can be used as stepping stones to a paragraph, and then a chapter, and then a book.
As an example, I've written thousands (!) of customer support messages, via email, chat, or reddit, to help my PhotoStructure beta users.
I've found that the second or third time I answer a question, either I need to fix the product so the question doesn't show up again, or I transcribe my response onto a new page on photostructure.com. In my case, it's just `hugo new content/faq/post.md` and then I dump the new content into the new page.
It doesn't have to be an elaborate post. Perhaps a bit more nuance or detail than my customer support reply, but not much more than that. Sometimes it's only 1 paragraph.
I've found that these "humble starts" can then be iterated on fairly easily, as inspiration comes to you.
As an example, according to git, I've made 15 commits to <https://photostructure.com/faq/library/>. The first iteration was just a handful of sentences I wrote as a response to what I meant by "library."