pyratelog

personal blog
git clone git://git.pyratebeard.net/pyratelog.git
Log | Files | Refs | README

commit 5b750319e63d639472139a6ec95fa6e63a80673a
parent c430b16ed6f09ca2441b5c8267dd84092368e4df
Author: pyratebeard <root@pyratebeard.net>
Date:   Sun,  1 Jan 2023 13:33:53 +0000

55_days_at_typing

Diffstat:
Mentry/55_days_at_typing.md | 6+++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/entry/55_days_at_typing.md b/entry/55_days_at_typing.md @@ -25,13 +25,13 @@ As you can see I started off the year strong. Twenty four entries in the first March was a bad month. I caught Covid-19 and was ill for about two weeks. For a couple of months after I also felt exhausted all the time, although having a one year old to look after did not help. Due to this I stopped writing every day, which in turn stalled my motivation and even my creativity. -The summer was a blur of work and parenting, barely getting a single entry published for a few of the months. Around this time I had also developed some rules on my writing. I had been drafting posts when I thought of what to write, but if a draft remained untouched for a few weeks, or I couldn't find the words, then it was forgotten. A number of the ideas I had on my list were either started as a draft or ignored if I couldn't think of how to expand on the premise. +The summer was a blur of work and parenting, barely getting a single entry published for a few of the months. Around this time I started to develop some rules on my writing. I had been drafting posts when I thought of what to write, but if a draft remained untouched for a few weeks, or I couldn't find the words, then it was forgotten. A number of the ideas I had on my list were either started as a draft or ignored if I couldn't think of how to expand on the premise. -My entries are also quite short on average. I have been told by some readers that they like this. Even my most lengthy entries can be read in 10 to 15 minutes. I try to develop my drafts in one or two sittings. If I can write a whole entry in half an hour then it will probably get published. +My entries are also quite short on average. I have been told by some readers that they like this. Even my most lengthy entries can be read in 10 to 15 minutes. I try to develop my drafts in one or two sittings. If I can write a whole entry in half an hour then it will most likely get published. Using that mindset has helped me to pick up the publishing a bit more near the end of the year to a comfortable rate. -A lot of the shorter entries were written at the beginning of the year but I quickly used up that backlog attempting to stick to publishing every two to three days. By the end of the year a was writing as and when the ideas came along. Either something new I was working on, or I had fleshed out an idea enough to start writing. +A lot of the shorter entries were written at the beginning of the year but I quickly used up that backlog attempting to stick to publishing every two to three days. By the end of the year I was writing as and when the ideas came along. Either something new I was working on, or I had fleshed out an idea enough to start writing. Considering between 2016 and 2021 I had only managed sixteen entries, I would say fifty-five in 2022 was a success. It has certainly got me into the habit of writing more and not only trying to write about technology. My [forged in metal](20220223-forged_in_metal.html){target="_blank" rel="noreferrer"} entry was one of the most enjoyable to write.