30,328 karma · joined August 18, 2007
technologist
addiction
solving puzzles
building things
"victory!" moment
impose will on electronics
These things are done and felt for their own sake and not as a means to an end, like a paycheck. Perhaps that's the main difference.This presupposes that the emotions cannot be a source of true information.
To me, "culture fit" is another way of saying "chemistry". It means that people work well together, and is what you want if you are forming a band, say, or any other creative endeavour.
https://hn.algolia.com/?q=picasso+eliot#!/comment/forever/0/... eliot
The line that elliots (not to be confused with T.S. Eliot!) quoted turns out to be authentic, though—or at least there's some evidence for it:
http://books.google.com/books?id=OJTKZeXaUvkC&lpg=PA53&dq=%2...
I think the defaults should be "all" (not story) and "forever" (not past week). I searched for something that I knew existed and when it didn't come up, my first thought was that the search was broken. Better to show everything at first and let the user decide how to narrow it down if they want to.
I think you'd be better off if the design looked like HN itself, especially the comment rendering. Not that what you've got is bad, but the user is almost always going to go from HN to search and back to HN. Any context switch is already a speed bump, and visual changes, which take time and mental energy to process, add to that jolt. Anything you can to do minimize these cognitive hurdles will serve the #1 goal, which is to get the reader the info they're looking for with minimum overhead. In this respect, the old HN Search is more usable, precisely for being unoriginal.
Thus, if I were you, I would drop the thumbnail pictures of the stories (it's cool that you can do it, but they don't really add anything and are distracting); would not include the story info with each coment (rather, I would do just like HN does and have a bit of text that says "| on: the-story-title-linked-here"), would make the text rendering look much like HN's, and would follow HN's lead in having a text- and information-density-centric design.
I'm not saying that HN's design is the global optimum (though it is better than most attempts to improve on it), but rather that HN search is an extension of HN and therefore not the place to innovate on its design. You're in a counterintuitive position for a startup with this project, since calling too much attention to yourself in this context is bad. You want to be unobtrusive and have the thing just work; the HN community is smart enough to figure out who you are from that and like you better for it. (That said, you shouldn't obliterate yourselves. For example, I like the visual cues that say "Page 1 of 10, got 237 results in 3 ms" and "1,244,896 stories and 5,289,181 comments indexed". They are unobtrusive and impressive.)
Lastly, a bug in Chrome: if I search for something, scroll to the bottom, click on "about", then hit the back button, the original results page freezes (i.e. refuses to scroll).
Sometimes it's even perverse, as he loves nothing better than to champion the obscure and take the famous and well-established down a peg. So I suppose it's fitting that basically no one has heard of his work.
I discovered him years ago on a long bus trip with a layover in Salt Lake City, where I went to a used bookstore. His book--actually an earlier one called "Who's Who in 20th Century Literature", smaller but still massive--was on a shelf in the basement of the store. I looked someone up in it and thought "this is interesting", sat on the floor and looked someone else up, and then another and so on. Hours later I woke up and realized that I was sitting on the basement floor of a bookstore in a strange city. I remember I had to run to the bus station and barely made it. That book, and then later the astonishing one I described above, became my companions for years, the sort of thing where the author is your mentor and friend and you feel vividly that you know him. Thank you Martin Seymour-Smith!
If it works, it will be useful.
The key to the Unix joke name genre is that the jokes are encoded laconically into the name and only the name (e.g. "less") and then have the good taste to immediately expire. They don't get old because they don't overstay their welcome.
Edit: I reworded this to be less judgmental.
I fear that the humor in it, much as I like humor, is a mistake. First, it comes across as a gender troll. Any technical attention the tool receives will be smothered by that avalanche. (Exhibit A: this thread.) More importantly, it impedes how the tool needs to work: get to the point immediately and cut everything else. Man pages may be Byzantine, but they do this well.
If I need examples for curl, examples for curl are all I want to see. They should be laid out readably and minimally (a nontrivial design problem). The last thing I want is a joke repeated everywhere. I'd say the same about the upvoting and downvoting stuff that appears in there: it's extraneous and distracting.
When I'm stuck on a shell command, it's usually because I have a specific task I'm trying to do. All I want is for the light bulb in my head to switch on so I can go "Oh I get it!" and go off to do the task. The best way is to see an example that's close enough to what I'm trying to do that it's like a magnet that attracts my specific task and snaps it in place. That's why I like the idea of this tool. It should focus on getting the user to that moment as quickly as possible.
Symbolism has its own logic, and the thing that becomes emblematic usually is not the most important one physically or rationally.
It can be overstated; you've overstated it. In contrast to the careful research described in the article, you've just made a bunch of stuff up. Your rush to assume race as the dominant factor is another example.
By default we should use functions: it is inelegant to use a macro where a function would do. We should use macros only when they bring us some specific advantage.
I understand from a language marketing point of view why someone might say, "Oh, those other Lisps made wild and crazy use of macros. It was really bad! But we are enlightened and have restricted them." But it's a bogus way of playing to a bogus criticism. It would be better to just say that there's a tradition of how to use macros correctly.
When I say "evidence" I'm not asking for formal studies; that's too high a bar for our field. But one can at least ask to hear about specific real-world experience.
Of the two arguments, the "too-powerful" one has the disadvantage of being prima facie absurd, so I think the "large-project" one is more harmful. So, where are the large Clojure and Common Lisp projects that have been harmed by this alleged language weakness? Let's find some practitioners who actually ran into this.
For what it's worth, I haven't. Since the best thing for a large project is not to be so large in the first place, applying language constructs to make codebases smaller is a great strength when the language lets you do it—and Lisp lets you do it.
Edit: [deleted off-topic bit]
Thanks, I enjoyed that article. It gives a vivid picture of the gap between the array languages niche and mainstream programming culture.