dangers of unibrowser: microsoft should have made me happy and chose firefox instead of chromium
you don't need to know everything: basically the title but longer
the new macbook pros are overpriced: basically the title but with nice tables with colors and a super long discussion underneath it (tldr; Apple has many of us locked in)
books i found at my parents: this is quite nice, I won't spoiler it!
I submitted my final grad school assignment ever just now, so my spare time can be spent on actually reading things now haha
Have fun! You'll need a looooot of tea to get through all of them :P
I definitely was thinking of that as an anti-pattern. Would you say the "archive" solves this?
Also: Your feedback Kayla would definitely be valuable along the way in terms of "should there be a trash"? A next-level archive for things that just can't be tossed.
I don't think we need anything like that tomorrow, but down the road you'll discover needs like that sooner than others.
Other categorization could make sense too, maybe being able to bucket stuff as "old" reads, but that you might still want to peek into from time to time.
I try to keep my Reading List to the purest form of just stuff to read. Once read, it gets unsaved and then heart or unicorn reacted. So my end goal has always been Reading List (0) since that means I got to everything I wanted to do. Like an Inbox Zero workflow.
In the spirit of the archive/buckets, I was keeping a Gitlab snippet for me to store links and comments so I could come back to it if there was something that interested me. Like "Awesome portfolio examples", "Good use of linters", "I still don't know wtf map and filter do" (I think I saved every dev.to article on JS tips purely due to map...). All that's been moved to Pocket so it's just a button click away, but I need to figure out how to comment in Pocket (I think Recommending it would do that).
Functionally, I could see me moving my Pocket stuff back to dev.to and archiving those as things to be saved but not in my face to read, but having played with that feature with your post on the Social Network soundtrack, seeing it still bookmarked is going to bug me. Especially since I think I have probably 100 things from the dev.to domain in Pocket.
My current Reading List workflow, as arguably a power user:
Go to Reading List
Open a handful of articles in new tabs, prioritizing new articles in tags I mod or short things that may need a comment to help boost them up :)
Read article
Remove bookmark reaction
React appropriately
Comment if the article isn't too old for the comment to be relevant or helpful
Move on to the next tab
When done with those tabs, refresh Reading List
Repeat
So it's not like I'm unsaving from the Reading List view -- I'm removing the reaction that no longer applies since I now have a new reaction to the post, all in the article view.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
😱😱😱
It's only since October, too, since back in October I got my list down to 0.
Looks like 4 of them are yours <3
And it's at
1229 after this morning1231 now.I submitted my final grad school assignment ever just now, so my spare time can be spent on actually reading things now haha
Ahah I'm going to summarize them here:
Have fun! You'll need a looooot of tea to get through all of them :P
Would that imply that you "unsaved" the posts?
I definitely was thinking of that as an anti-pattern. Would you say the "archive" solves this?
Also: Your feedback Kayla would definitely be valuable along the way in terms of "should there be a trash"? A next-level archive for things that just can't be tossed.
I don't think we need anything like that tomorrow, but down the road you'll discover needs like that sooner than others.
Other categorization could make sense too, maybe being able to bucket stuff as "old" reads, but that you might still want to peek into from time to time.
Look out in June for when I get to reading and commenting on all your old articles :D
I try to keep my Reading List to the purest form of just stuff to read. Once read, it gets unsaved and then heart or unicorn reacted. So my end goal has always been
Reading List (0)
since that means I got to everything I wanted to do. Like an Inbox Zero workflow.In the spirit of the archive/buckets, I was keeping a Gitlab snippet for me to store links and comments so I could come back to it if there was something that interested me. Like "Awesome portfolio examples", "Good use of linters", "I still don't know wtf map and filter do" (I think I saved every dev.to article on JS tips purely due to map...). All that's been moved to Pocket so it's just a button click away, but I need to figure out how to comment in Pocket (I think Recommending it would do that).
Functionally, I could see me moving my Pocket stuff back to dev.to and archiving those as things to be saved but not in my face to read, but having played with that feature with your post on the Social Network soundtrack, seeing it still bookmarked is going to bug me. Especially since I think I have probably 100 things from the dev.to domain in Pocket.
My current Reading List workflow, as arguably a power user:
So it's not like I'm unsaving from the Reading List view -- I'm removing the reaction that no longer applies since I now have a new reaction to the post, all in the article view.