Go to your profile. Set your "noprocrast" to yes. Set you maxvisit to 15. Set your minaway to 60. I'll be back in an aware to see if anyone replies. ;)
Get a load of this guy, typo out in the open and helpless to save his proof reading reputation.
Stop looking at HN and go work that thing you promised yourself you'd work on
61–70 of 88 posts
Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#62New Year Resolution: turn noprocrast on, with maxvisit 5 and minaway 240.
And for those of you just tuning in (like me) -- noprocrast is a setting in your hackernews profile (upper right corner). Turn it on and it will only allow you on the site for a maximum amount of time (maxvisit) before preventing you from using it for a minimum amount of time (minaway). It has to be turned on manually. The maxvisit 5 and minaway 240 would let you visit for 5 minutes every 4 hours. I just turned mine…
I've used Leechblock (firefox extension) in the past for the same purpose. One feature it has which I found particularly useful is the option to delay pages instead of completely blocking them.
Instead of the transition being an abrupt stop that makes me want to turn the blocking off to finish what I was doing, the delay makes it a gradual frustration, and feels a lot more like getting naturally bored of browsing.
Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#63TL;DR
Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#64I will keep looking at HN because I learn a lot about the technology and the trend from it. And I also found the comments on HN are high-quality.
The only thing I don't like on HN is the UI. So I created http://hackernewsroom.com based on HN API. Now I read it everyday. But HN API is read only. When I want to comment, I have to click a link to go back to HN to make comments. Another con of hackernewsroom.com is some websites have the same-origin policy which are unfriendly to iframe.
Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#65Do you mean... "Looking at HN" or do you mean "Reading and commenting on HN and getting into arguments with people and checking your karma and replies and upvoting / downvoting / flagging posts and making observations about the correlation between username and karma and generally not even bothering to read TFA or the front page and just trolling the comments section for interesting things to respond to like this" It…
^ downvoted for referring to being downvoted.
Um, let me rephrase that.
Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#66I was, but it's compiling...and now it's done. Back to work.
Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#67I'm just here because my compile times are slow. 3 hours later… after 12 tweets, reading 6 articles, filing a GitHub issue, and watching a show on Netflix… what was I building?
I know, Scala, right?
Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#68Earlier quoted context omitted.
And for those of you just tuning in (like me) -- noprocrast is a setting in your hackernews profile (upper right corner). Turn it on and it will only allow you on the site for a maximum amount of time (maxvisit) before preventing you from using it for a minimum amount of time (minaway). It has to be turned on manually. The maxvisit 5 and minaway 240 would let you visit for 5 minutes every 4 hours. I just turned mine…
I've used Leechblock (firefox extension) in the past for the same purpose. One feature it has which I found particularly useful is the option to delay pages instead of completely blocking them. Instead of the transition being an abrupt stop that makes me want to turn the blocking off to finish what I was doing, the delay makes it a gradual frustration, and feels a lot more like getting naturally bored of browsing.
Nice! Thanks for the tip!
Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#69I'm just here because my compile times are slow. 3 hours later… after 12 tweets, reading 6 articles, filing a GitHub issue, and watching a show on Netflix… what was I building?
Hmmm....you may have been compiling Scala.