Comment on Installing Jellyfin as a Podman Quadlet
lime@feddit.nu 1 month ago
this guide, and the previous one, have a lot of weird superfluous steps. like, why use a command that includes nvim and then ask people to change it instead of just saying “edit the file”? why symlink systemd stuff to your own home directory?
the info is good, but having to separate the actually useful stuff from things that are specific to your config makes it less useful.
eric@lemmy.ca 1 month ago
I’m still learning how to write good posts. I’ll this into consideration for the next one.
lime@feddit.nu 1 month ago
your writing overall is good! it’s just a matter of information priority.
here’s a tip, dunno how applicable it is but i use it when writing technical documentation:
for each step, explain to yourself why you’re doing it the way you are. if it turns out you caused the step to be needed, rather than it being required, you probably need to rethink, or at least add the explanation to the text.
eric@lemmy.ca 1 month ago
That’s a good tip. Thanks. I think I might tweak the existing posts for readability.
eric@lemmy.ca 1 month ago
I rewrote my original quadlet article, can you have a look and let me know what you think? ericthomas.ca/posts/setting-up-podman-quadlets/
lime@feddit.nu 5 weeks ago
this is more focused for sure, but it lacks the enthusiasm of the original. if i was trying to do this for work, i would appreciate how quickly it gets to the point. however, it no longer reads like this is something you’re interested in. it reads a bit wooden. i get that would happen after you’ve been told to correct your style though.
to be clear, the original article doesn’t need to be rewritten. for the future though, when you want to tell the story of how you got something working, include your reasons for doing something a certain way. if you need a self-inflicted complication, that’s not really a part of it (unless it’s funny)