Question for those of you who read technical blog posts:
I'm writing a post that just keeps growing, and there are probably three separate sections that are each as long as one my normal posts.
All three could be articles on their own, BUT they are telling a single story (I'm trying to do X, but needed to learn and dig into Y and Z to get X done)
Do folks prefer multi-part stories spread over several articles, or should I commit to having one mahoosive piece that tells the full story?
tomhazledine /
npub13v…0jz7v
2024-06-18 13:30:16
Author Public Key
npub13vu8esvvj2stf4ptm3p3ey73pslzacrwmg7gd9mqu390g96twj2sz0jz7vSeen on
wss://relay.nostr.bandPublished at
2024-06-18 13:30:16Event JSON
{
"id": "97ab0e3f3c60a11c6834e165169b33234243f57160c85416b9f72db7f6875539",
"pubkey": "8b387cc18c92a0b4d42bdc431c93d10c3e2ee06eda3c869760e44af4174b7495",
"created_at": 1718717416,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.social/users/tomhazledine/statuses/112637864609662672",
"activitypub"
]
],
"content": "Question for those of you who read technical blog posts:\n\nI'm writing a post that just keeps growing, and there are probably three separate sections that are each as long as one my normal posts.\n\nAll three could be articles on their own, BUT they are telling a single story (I'm trying to do X, but needed to learn and dig into Y and Z to get X done)\n\nDo folks prefer multi-part stories spread over several articles, or should I commit to having one mahoosive piece that tells the full story?",
"sig": "7f1bb5d3dd1fe1e1faab48bb36d4a6a8853d95ce335ac3d83c2e2c3f47c2c8d803333953e5e4e3cf0fdcb1b45113ae69da69677647a9fc21f0c14e1e2b8fba56"
}