It probably doesn't make a difference, so cheers.
Stop looking at HN and go work that thing you promised yourself you'd work on
31–40 of 88 posts
Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#32I'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?
Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#33Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#34I'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?
Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#35Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#36Re: Stop looking at HN and go work that thing you promised yourself you'd work on
#37I'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?
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
#38I'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
#39Today, 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
#4012 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 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.