"When I first started using RSS, I thought I’d found this great tool for keeping tabs on news, current events, and stuff I should and do care about.
After adding newspapers, blogs, magazines, publications, YouTube channels and release notes from software I use, I felt a false sense of accomplishment, like I’d finally been able to wrangle the craziness of the internet into a single app, like I had rebelled against the algorithm™.
But it didn’t take long to accumulate hundreds of posts, most of which I had no true desire to read, and soon after I abandoned my RSS reader. I came back to check on it from time to time, but its dreadful little indicator of unread posts felt like a personal failure, so eventually I deleted it entirely."
> As a byproduct of writing a Readme in order to know what you need to implement, you’ll have a very nice piece of documentation sitting in front of you. You’ll also find that it’s much easier to write this document at the beginning of the project when your excitement and motivation are at their highest. Retroactively writing a Readme is an absolute drag, and you’re sure to miss all kinds of important details when you do so.
"When I first started using RSS, I thought I’d found this great tool for keeping tabs on news, current events, and stuff I should and do care about.
After adding newspapers, blogs, magazines, publications, YouTube channels and release notes from software I use, I felt a false sense of accomplishment, like I’d finally been able to wrangle the craziness of the internet into a single app, like I had rebelled against the algorithm™.
But it didn’t take long to accumulate hundreds of posts, most of which I had no true desire to read, and soon after I abandoned my RSS reader. I came back to check on it from time to time, but its dreadful little indicator of unread posts felt like a personal failure, so eventually I deleted it entirely."