Live data from Hacker News

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

news.ycombinator.com

81–88 of 88 posts

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

#81

For me, reading HN is like reading the paper or reading books about subjects that matter to me: it's not time strictly spent on the job I have to do, but it's part of a healthy information diet. Crunching code without taking a look at what's currently happening and being discussed in your professional community is hardly a recipe for self improvement. (It's a thin red line between healthy consumption and abuse, I kno…

Hacker News is the place where I come to learn about new technologies and to see where the industry itself is moving. There is something here for everyone, from CEOs to C++ programmers. Over the years, it has been a very valuable source of news. If you ignore the first 9 links about any new JS framework, it shouldn't take more than than 10min/day just to keep up with what is happening. Or is this just not true in you…

I can spend a whole Sunday afternoon here if I really dig into 10+ articles on the front page, read the top comments, and contribute to the discussion.

On an average workday though, I look at 3-5 posts and skim the articles. I often find more value in HN's discussion than the article itself.

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

#82

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…

I went through your comments history and I'm not sure I quite grasp what your idea is or what problem it solves. If I understand correctly, you have this idea for a new type of human-computer interaction based on a visual programming/interaction language? I suggest you start by writing down your thoughts in a blog/wiki for others to better understand it. I'd also start working on an MVP now because in another 12 year…

I've been practicing something like this myself.

When I have an idea that seems like something people want, I force myself to describe it in a 250-500 word blog post. Most of them I never ship, but it's really about the exercise of conveying your ideas in a way other people can digest quickly and easily.

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

#83

I 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…

Having the article text and comments on one page is a great feature.

I'd also love to see the community move towards in-text annotations directly on the article page, but it's hard to ease into that.

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

#84

I 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…

Having the article text and comments on one page is a great feature. I'd also love to see the community move towards in-text annotations directly on the article page, but it's hard to ease into that.

Exactly. It's inconvenient to read the article and comments in separate pages.

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

#85
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?

Large Scale C++ Software Development

John Lakos

The book explains how to design large systems to contain compile times.

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

#87

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…

I went through your comments history and I'm not sure I quite grasp what your idea is or what problem it solves. If I understand correctly, you have this idea for a new type of human-computer interaction based on a visual programming/interaction language? I suggest you start by writing down your thoughts in a blog/wiki for others to better understand it. I'd also start working on an MVP now because in another 12 year…

I don't think NLP/AI is a threat. Nobody is working on the UI problem.

How are we going to communicate with said AI? Surely not text or speech. Nobody is able to answer this yet. That's why I'm working on it.

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

#88

Earlier quoted context omitted.

I went through your comments history and I'm not sure I quite grasp what your idea is or what problem it solves. If I understand correctly, you have this idea for a new type of human-computer interaction based on a visual programming/interaction language? I suggest you start by writing down your thoughts in a blog/wiki for others to better understand it. I'd also start working on an MVP now because in another 12 year…

I've been practicing something like this myself. When I have an idea that seems like something people want, I force myself to describe it in a 250-500 word blog post. Most of them I never ship, but it's really about the exercise of conveying your ideas in a way other people can digest quickly and easily.

I have described my vision on IRC, Reddit and HN multiple times.

People hate it because they can't understand it.

Post reply on HN