Readit Newshttps://papertrail.biblish.com
I am a writer of literary fiction first and foremost, and I never really understood the interest in tracking or reviewing books. I can see its usefulness for a certain segment of the market, but what I come to read is mostly the result of following the map of influences of the authors who inspire my writing. The quality of these works is thoroughly vetted by their centuries of survival. Little reviews do not seem like a useful mechanism for finding the best in contemporary literature either.
In any event, little reviews and social features are a much better way to develop a user base for your platform. Papertrail works fairly well as intended, and I use it extensively, but we found pretty early on that asking users to take extensive notes on books was too large a barrier of entry for people to cross and start producing the content the site needs to grow. My lead developer, who really functioned, perhaps a little too well, as cofounder, found a good job opportunity elsewhere, and I have not been able to replace him. Me and another developer are still working on it, but it looks to be on the road of another application that did not quite find a market.
My profile on Papertrail can be found below.
I'll give biblish a go!
TidyTweets analyses your Following list on Twitter telling you which accounts haven't been active in a specific time frame (one week, two weeks, one month, three months, six months and a year). You can then unfollow individual accounts, selected accounts or all at once.
Definitely still rough around the edges (particularly the UI) but it does what it says on the label.
Upcoming features area a more polished UI as well as a way to manage Lists (create/delete/assign accts).
TidyTweets is FOSS, if you'd like to contribute with code, bug reports or feature suggestions (or just take a look around) stop by Github: https://github.com/rlueder/tidytweets
Thanks!
Happy (tidy) tweeting! :)
I used Claude Code and while the end result works (kinda) I noticed I was less satisfied with the process and, more importantly, I now had to review "someone else's" code instead of writing it myself, I had no idea of the internal workings of the application and it felt like starting at day one on a new codebase. It shifted my way of working from thinking/writing into reviewing/giving feedback which for me personally is way less mentally stimulating and rewarding.
There were def. some "a-ha" moments where CC came up with certain suggestions I wouldn't have thought of myself but those were only a small fraction of the total output and there's def. a dopamine hit from seeing all that code being spit out so fast.
Used as a prototyping tool to quickly test an idea seems to be a good use case but there should be better tooling around taking that prototype, splitting it into manageable parts, sharing the reasoning behind it so I can then rework it so I have the necessary understanding to move it forward.
For now I've decided to stick to code completion, writing of unit tests, commit messages, refactoring short snippets, CHANGELOG updates, it does fairly well on all of those small very focused tasks and the saved time on those end up being net positive.