jjoonathan on Oct 6, 2014 on: Glut of postdoc researchers stirs quiet crisis in ... https://news.ycombinator.com/item?id=8416875, "For most people it's not, but some people subscribe to the notion that choice implies consent/endorsement/approval ..."
scardine 12 months ago on: Ask HN: My company plans an ICO despite my opposit... https://news.ycombinator.com/item?id=16126082, "Like almost all problems in life you have only 4 options: ..."
graycat on Mar 28, 2015 on: The FedEx Problem https://news.ycombinator.com/item?id=9282104, "Yes, at FedEx, we considered that problem for about three seconds before we noticed that we also needed: ..."
Animats on Nov 21, 2015 on: How a little bit of TCP knowledge is essential https://news.ycombinator.com/item?id=10608356, "That still irks me. The real problem is not tinygram prevention. It's ACK delays, and that stupid fixed timer. ..."
And discovered that Animats is in fact John Nagle...
https://news.ycombinator.com/item?id=4509934
How Do I Start Being a Consultant?
https://news.ycombinator.com/item?id=4245960
Bane's rule, you don't understand a distributed computing problem until you can get it to fit on a single machine first.
https://news.ycombinator.com/item?id=8902739
Edit: Thanks detaro for telling me how to link to individual comments.
Click on the timestamp next to the username
Also, wow, all those comments of people plugging their level 3 and above startups did NOT age well
The "going deep" post reminds me of the "programmer-archaeologist" role from the Vernor Vinge novels, where a long-running spacefaring civilisation has built up a very large amount of code on which their magic nanotech runs. This provides opportunities to dig for long-forgotten things .. or exploits.
> That reminds me of Peter Thiel's Venn diagram of 'Sounds like a bad idea' and 'Is a good idea'. It's a pretty slim area in the middle and the 'Sounds like' part means it's hard to know until you do it.
For the aforementioned comment about 4-color-map theory, I thought it shouldn't be debunked because the person seemed to attempt to substantively debate (until he apparently gave up). I mean, the comment should have been downvoted to oblivion for being so definitively wrong. I just associate flag-killing with comments that are obviously abusive.
Something can be dead because it is flagged, in which case a bunch of people didn't like it (for valid reasons or not...) or because the user is new and all their stuff is marked dead until someone comes along and vouches.
"My working theory is something like “romanticism/emotionalism vs. abstract rationalism”; if you’re writing something that benefits from immediate experience and emotional input (e.g. Kafka writing about nightmarish bureaucracy after working all day in an insurance firm) then it is better to write at night, after the events of the day have happened and your mind has been operating for 12+ hours." https://news.ycombinator.com/item?id=18369337
"Classes get in the way between the programmer and the problem. They force you to reify your thinking into "things" (classes) that demand names and citizenship rights, so to speak, in the system. These "things" don't really exist, but we act like they do, and so increasingly see the problem in terms of the classes we've defined." https://news.ycombinator.com/item?id=3717715
"One thing that I find sorely missing in many teams is onboarding documentation. So when you come in, document everything that you need to do (required permissions, development environment setup, mailinglists, subscriptions) and how to do it." https://news.ycombinator.com/item?id=17353854
"The real value of Flask is that it makes you appreciate what Django does by default. When I first started learning Python / web frameworks, I went with Flask because it was smaller and "simpler". As my project grew however, I had to organize it. I was basically imitating what Django gives you by default, though less cleanly." https://news.ycombinator.com/item?id=16935441
That thread is a classic example of why the most capable people aren't necessarily the ones you should want to work with.
I considered deleting my comments, but decided instead to keep them to remind myself to behave better.
https://news.ycombinator.com/item?id=1487605 (2010)
https://news.ycombinator.com/item?id=3996652 (2012)
https://news.ycombinator.com/item?id=12496558 (2016)
https://news.ycombinator.com/item?id=16846229 (2018)
(possibly more)
It’s upvotes that are private to each user.
comment by comment you could sense the earth shattering awareness slowly setting in, or how the HN crowd suddenly went from unquestionable faith in big government to "oh lord what have we done".
Currently, we have the option to click on 'favorite' to add submissions or comments to a publicly visible list. Occasionally (a couple times a month?) I do this for comments that I think are excellent: https://news.ycombinator.com/favorites?id=nkurz&comments=t
Some other users do the same, but I don't really know how many, because there isn't really an interface to explore this. It looks like about half the top of the "leaders" list make use of this feature, although in some cases these might just be accidental clicks.
Anyway, it would seem like there should be some great way to make use of this information, but I don't know what it would be. A simple list of recently favorited comments? Marking on the comments that have been favorited? Just more prominence to what a user's favorites are?
Probably there is some even better way: How can we make better use of HN's 'favorite' feature?
(Mind you, easily fixed on personal level by simply bookmarking them in browser itself instead, but doesn't help HN)
https://alvinalexander.com/scala/fp-book/how-functional-prog...
“What're the best-designed things you've ever used?”
"Did you win the Putnam?"
Yes, I did.
> Humans are very good at holding lots of exceptions in our heads and, in the absence of clear rules, doing reasonable things. Computers are shit at both of the above.
https://news.ycombinator.com/item?id=18281465
Funny and very well written.
Edit: pasted a wrong link, fixed the context