Live data from Hacker News

Stop looking at HN and go work that thing you promised yourself you'd work on

news.ycombinator.com

31–40 of 88 posts

Re: Stop looking at HN and go work that thing you promised yourself you'd work on

#31
Do 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 probably doesn't make a difference, so cheers.

Re: Stop looking at HN and go work that thing you promised yourself you'd work on

#32
post #6

I'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?

> 3 hours later… after 12 tweets, reading 6 articles, filing a GitHub issue, and watching a show on Netflix… what was I building? Judging from the compile times, Gentoo?

Probably just "hello world" for an fpga :>

Re: Stop looking at HN and go work that thing you promised yourself you'd work on

#34
post #6

I'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?

Anyone have any tips for a productive way to deal with long compile times?

Re: Stop looking at HN and go work that thing you promised yourself you'd work on

#35
Or just tweak things for high signal:noise ratio. Scan the front page for only things relevant to your work/research/etc, ignore the clickbait. Read only a selection of your favorite commenters. Etc. This works on other social media like Twitter and Reddit too. You can minimize time spent while extracting max value.

Re: Stop looking at HN and go work that thing you promised yourself you'd work on

#36
post #34
post #6

I'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?

Anyone have any tips for a productive way to deal with long compile times?

[deleted]

Re: Stop looking at HN and go work that thing you promised yourself you'd work on

#37
post #34
post #6

I'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?

Anyone have any tips for a productive way to deal with long compile times?

1. Write documentation while things are compiling.

2. Finish other work.

3. If you iterate a lot, maybe just reading the code figuring out your next steps.

4. Maybe figure out why it's taking so long, and figure out a way to speed things up.

5. Write more tests.

Re: Stop looking at HN and go work that thing you promised yourself you'd work on

#38
post #34
post #6

I'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?

Anyone have any tips for a productive way to deal with long compile times?

ccache[1] works for me.

http://ccache.samba.org

Re: Stop looking at HN and go work that thing you promised yourself you'd work on

#39
12 years ago, I have decided that I would forever change the way people communicate.

Today, nothing has been done. I'm struggling to get people to relate to this need for a better communication system and language. I am convinced that this is very important, but I fail to get the positive feedback I've always expected.

Should I ignore people and blindly trust my guts? Taking on such a massive task is very difficult for a single person.

Re: Stop looking at HN and go work that thing you promised yourself you'd work on

#40

12 years ago, I have decided that I would forever change the way people communicate. Today, nothing has been done. I'm struggling to get people to relate to this need for a better communication system and language. I am convinced that this is very important, but I fail to get the positive feedback I've always expected. Should I ignore people and blindly trust my guts? Taking on such a massive task is very difficult f…

> fail to get the positive feedback I've always expected

I don't know what your idea is, but that statement makes me think "confirmation bias". Start looking for something people really want instead, and build from that. Otherwise you're effectively just building a product for yourself, and trying to convince yourself that others will want it.

Post reply on HN