skysight-inc/HackerNews huggingface dataset:
Why thanks Jordan! You've just now confirmed that I, and probably many other developers, would actually never want to work for you. Thanks for lashing out!
Delusional Startup Story
The Price 20-Somethings Pay to Live in the City
Small point: the syntax of .ssh/config doesn't use equal signs; the actual format of that stanza would be

Host example.com
User someweirduser

Another subtle point about SSH config -- only the first matching entry (in top-to-bottom order) for a given parameter is taken from .ssh/config. If you have multiple Host entries that match for a given hostname, the first matching User, Port, etc, entry will be the one that ssh uses.
Let's be careful here.

I'm happy to argue about graphic design and will concede up front that I'm not an expert.

My criticism of the OP's resume, though, are about the resume infographic as a resume infographic. Like many, many people on HN, I'm certainly qualified to "elaborately bash" a bad resume.

Next, while I respect that you might disagree about the Feltron annual reports, it's certainly not a personal quirk that I like them; I learned about them from the Kottke/Gruber nexus on the web, and other people (notably, the New York Times, the Wall Street Journal, Wired, Creative Review, Print Magazine, Slate, and AIGA) have called the reports out as well.

Finally, I hope you understand that I'm addressing the "style" part of the "style vs. substance" issue with this resume by citing Feltron.
> Bing didn't weight Google ahead of a single other source of information, so I don't think this really comprises evidence of high weighting at all. To make that claim, someone needs to run a controlled test like the one you describe here.

Strictly speaking, I think you're right, but it was interesting that it would accept mappings that didn't exist elsewhere, rather than requiring the same mapping from at least one other source. But you're right that a more complete test is warranted. And Bing may have already adjusted things to prevent this, so we may never know.

> Although I don't really know what half the fields do, so there could be something clever going on in there.

True, but the mysterious parts I see appear to be constants (I may have overlooked something, though, so feel free to point out any mysterious dynamic bits I'm ignoring). Those should be out-and-out harvestable from actual Bing toolbars. With constants, I strongly suspect that we only need to harvest valid data, rather than figure out how to generate our own.

Worse for Bing, my experience in removing viruses says that "people who install lots of toolbars" and "people who get viruses/malware/joined to a botnet" are sets that overlap so a significant degree, so it might become hard to separate actual user clickstream data from forged clickstream data when they're both coming from the same, infected, computer.

Finally, I'm sorry I forgot to give you credit. If it's any consolation, I think I did give you credit last time I posted your link. Thank you for doing a better technical analysis than I've seen from anyone else on this story.
Seeing multiple comments of yours in here (all negative) I can't help but wonder if you have some kind of axe to grind with her?

Yes, her infographic isn't flawless. But it isn't bad either, it is in fact pretty damn good. And most certainly good enough to stand out in a pile of standard-resumes, which is about as much as it can possibly accomplish.
"No reasonable employer cares about college credits earned in high school, the age you were when you coded your first website, or what platforms you tech-supported in school, and yet that material consumes more visual weight than the number of years the candidate has doing Rails development."

I think this is a ridiculous statement, but we almost certainly have a different definition of what makes an employer (cough) reasonable.

My priorities in a resume read are passion, then applied intelligence, then experience. The information you're ignoring here is valuable with essentially no additional variables (doesn't matter much where they went to high school, or what the website did). How long someone I don't know paid you to write code in whatever technology is almost useless information to me.
A RedLaser and Lupe Fiasco Collaborative
Possibly this joke gets even better after DNF comes out. If they can make even Duke Nukem Forever real why canMt they ever release HURD.
They can also be used to do the actual optimizations. For example most formulations of the register allocation problem are NP-complete. SMT formulas can be used as a very powerful abstract domain in abstract interpretation.
The question a resume should answer is "would I interview" not "would I hire." And my answer here, were I looking for a designer who is creative, who could implement designs in HTML and CSS, and who could work with Rails, would be absolutely.

She is applying for a design / developer job. This is a phenomenal resume because: it shows that she can present things attractively and, most importantly, can be creative.

Lastly, it would appear that it's interactive, but we only have a link to the static image. I think it would be a lot more appealing if you could hover and learn more.
Thanks, and good feedback on the need for a demo -- we're revamping the website now, it's long overdue.

In regards to your question: I was intimately involved in the fundraising process, having already known Sequoia Capital before they invested. So I knew those guys. When they invested, the former CEO was still CEO. About 5 months into their investment the CEO and the company parted ways and I immediately took over in an interim role.

After our first board meeting when I took over as interim CEO the board already seemed pleased with the immediate changes I had made and reminded me that all CEOs are interim CEOs and I should just continue to operate as CEO -- there would be no replacement search.
I've seen it mentioned somewhere that facebook has been having a problem finding self-directed developers. They want the good ones to be mini-ceo's, and they're having problems finding that. Instead they're getting lots of hotshot coders who flounder around.

I think they'll have a difficult time finding those mini-ceo's without changing the culture quite a bit. This is what happens when you hire straight out of school.
Actually it's a constantly updated article- they keep on adding new startups... the most recent one was just added yesterday
(a) I am definitely being very noisy on this thread. Sorry. I'm procrastinating.

(b) Instead of simply saying "you're wrong!", why not tell me some things you specifically like about this infographic as an infographic? I am seriously interested in what stories you think this graphic does a good job of telling.
I wanted to use Arduino for a project, but gave up on it because it has such a tiny amount of memory. http://www.arduino.cc/en/Tutorial/Memory
Hurd/Linux and Xanadu/WWW are classic examples of worse is better, minimum viable products, and perfection being an enemy of goodness.

Imagine what kind of world we would be in today if we had had to wait for Hurd and Xanadu?

Shipping is always a feature, and sometimes perfection at the cost of depriving the world of goodness is just the vice of excessive pride dressed up in other clothes.
What's interesting is she just glosses over the programming aspect. This got me thinking. The C language presents a pretty big barrier to entry for young tinkerers, who have never heard the word "integer" before.

I learned to program when I was 6 or 7 years old, using Logo. Unfortunately, Logo is all but dead, but I still think it's the greatest educational programming tool ever. We even had a version of Logo that could interact with Lego motors and sensors called "Lego Logo."

So why can't you program the Arduino in Logo? I posted a quick proposal for such a system at http://github.com/74hc595/Arduino-For-Kids and hopefully I'll get around to implementing it soon. Feedback is welcome.

aside: Yes, there is a version of Scratch for the Arduino, but I personally think the merits of visual programming languages are questionable...
I definitely think there are certain people who are born with negotiation skills, and those that are not. You can always get better of course, but some people have a natural ability (a specific form of empathy) to know what exactly the other party is thinking, feeling, and expecting, and can exploit it as much as possible. Its just as much a skill as a talent, and can be used for both good and evil.
Both were(are) homepages that list your likes/dislikes/memberships and have a stream of comments. It was friendster et al that tried to do the real hard CS graph theory stuff. Facebook /still/ doesn't do those things - though they talk about "the graph" constantly.

Just try searching for everyone within X miles in your network.
Entrepreneurs need to realize success in business is an anomaly.
The following page (indirectly linked to from the Wikipedia page) has more in-depth information:

http://www.st.cs.uni-saarland.de/dd/
I was posting about a similiar system around a year ago.

Ended up standardizing clusters of only 3 nodes. Initially I wrote a Paxos+Dynamo but it was a dead end for me for our needs. I did not need a massive data store, but a cheap highly available / scalable enterprise service that consistently gave the same answer. e.g. an eCommerce pricing engine. 3 commodity box nodes is all you ever need. I've done over 500,000 prices per second with ~ 9 unique way of pricing ~475,000 skus, based off the equivalent of 100's millions of data rows.

Use IP multicast for cluster/leader election configuration. Much faster. All a server needs configured to boot strap into the cluster is a single IP. Opted to not use Zookeeper though it came out when I was writing my system.

I tried a Dynamo/Cassandra approach on the updates but abandoned it as too slow early on. I ended up using something more like Linked-Ins Kafka for the "log" shuttling. In Kafka parlance, one topic with 3 partitions one for each node. Each node mirrors all three partitions but is owner of 1. One other diff is I do push/push while Kafka a does push/pull. This makes sense as each node is both a broker for and consumer of the other nodes.

Node 0 writes incoming updates to partition 0 and does a 1 out of 2 push to partition 0 on nodes 1 and 2 (third auto drops to async as we have 2 of 3 durable stores)

For update application Paxos is used to then only for consensus of the highwater mark of message Id (the kafka offset). Analogous to Spinnaker's LSN.

Consensus updates to the message high water mark are "batch" applied by a single thread, and only a single thread, to the in-memory store which uses a special array based hash map (Compact Hashmap). The single thread with a ReaderWriter lock give transactions for free with a "database lock" being faster row locking as its all in mem. I have the equivalent of 100s millions of rows in mem all synched between the three nodes.

One final optimization is the observation that if the overlaying application is REST based then updates commute under PUT semantics (version with a vector clock). For this type of application the total ordering of the application of the updates across the nodes is relaxed as it is guaranteed to converge (eventually consistent).

Since all update are batch applied, in mem, on a single threads with a reader/writer lock a client always views only the converged consistent state though each nodes path to convergence may be different.

I had looked at using a Dynamo/Cassandra like Spinnaker but after coding it found it too slow. When I went with a log shuttling push/push similar to LinkedIns Kafka performance of updates jumped quite nicely. I note one of the authors works at LinkedIn.

Wrote the thing in Scala which was also sort of new at the time. But turned out to be a good choice.
To be fair, I've hung out with some of the folks in the business school here at the UChicago, and there are some really bright and useful folks that I would be delighted to work with again. Participated in their new venture challenge thing with the bump folks and I found my teammates and many of the other folks there to be smart, motivated, and very skilled at necessary things that I never, ever want to become good at.
Even if you don't ultimately become a programmer, just knowing enough to know how hard or easy something is will give you a large biz dev advantage. Lots and lots of tech execs (especially in silicon valley) are either former programmers or electrical engineers. It will also help your own due diligence efforts when evaluating partnerships or vendor technology.

Also, just knowing enough to fix problems in an emergency will make you look like a super hero to customers.
> This joke has an expiration date of May 3rd this year.

Call me Thomas, but I'll believe it when I see it...
I've never understood this argument for always including braces in one-line if-blocks. Won't this error be immediately obvious? I mean, after making the change, won't even the most minimal test catch the mistake?

If developer #2 isn't doing the most basic test to verify that "statement2" runs when "conditional" is true, then you've got way bigger problems than your style guide.
The problem is not the semicolons, it is the newlines, and there is little you can do about that. The newline/semicolon issue is the most ridiculous language design decision ever.
I think they're trying to be funny. It certainly does not come across as funny, however. So, if they really seek a sales and marketing person, they should avoid using loaded words like monkey, droid, etc.

See the satirical post about the terms rockstar and ninja, as it refers to employees. http://news.ycombinator.com/item?id=2180233
Why Apple’s iPhone is still not coming to Verizon [2009]
I’ve never personally minified JavaScript, with or without semicolons, but the article “Semicolons in JavaScript are optional” linked to in the page says the author minified jQuery without semicolons with Google Closure Compiler, and the test suite passed. Is that article wrong? Did minifying semicolons use to work, but they removed that feature for some reason? Does no one actually use Closure Compiler, and the other minifiers don’t support missing semicolons? Or is the reason the plugin you found “blows up” simply the error described in “Semicolons in JavaScript are optional” in the section “The only real pitfall when coding without semicolons”, which is starting a line with “(d + e)” instead of “;(d + e)”?

That article says that if a minifier doesn’t understand JavaScript that an actual JavaScript interpreter can understand, the minifier is buggy. I agree with it – if your minifier messed up the semicolon-less jQuery plugin, and if none of the situations I mentioned above was the case, then your minifier needs fixing, or you should start using a different one.
Really good points, though I see benefit in the existing pull request mechanism also. It'd be interesting to consider merging the concepts of opening tickets and making pull requests.. For instance, if I could 'pull request' a conceptual feature, before there's code written and then we could discuss, add patches, and eventually merge a solution. It'd allow each project and issue the opportunity to do what's appropriate for the particular change.
I hope you understand that I'm addressing the "style" part of the "style vs. substance" issue with this resume by citing Feltron.

Yes and I don't agree with this apples vs oranges comparison, which is why I pointed out how unsuitable the Feltron infographics would be for a resume - no matter how well they may work in the context of an annual report.

The goal of her infographic is to catch attention and force-feed information while glancing. If that resume landed on my desk then I would look at it longer than at most others, simply because it's visually pleasing and interesting (read: different).

I agree that I wouldn't want to receive such a resume for the position of, say, a security researcher or for a (wait for it) infographics designer. But for the position of a web-designer or rails-developer I don't think this deserves the flak you were giving it.
This site is also a must-have for iOS developers who want to see the glossy/rounded edges version of their icons:

http://www.midnightmobility.com/iphone-icon/
Fun with Numbers
Anecdotally I've seen smart and capable developers make this mistake numerous times. It usually gets caught by code review, automation etc. But not always.

It's basically the birthday paradox. You take the probability of a very unlikely event and raise it to a big enough power (enough people, enough lines of code) it becomes a non-negligible outcome.
+1. I wanted some deep answers, not a bunch of fluff. That stuff is pretty self-explanatory and not all that surprising. Oh well.
You know I'm a Rails developer, right? That we're hiring Rails developers? Stop saying I'm not qualified because I'm a "security researcher". :)
I had a MySpace account before I had a Facebook account. When I first joined MySpace a lot of my friends were on the site but soon after a lot of them started to leave and move over to Facebook. MySpace allowed users too much freedom to design and customize their pages which resulted in a horrible user experience for most users, while Facebook offered users a more clean design and professional experience.
Any halfway decent tech team manager or sysadmin should make a very clear company-wide policy against passphraseless SSH keys for developers.

Github compares it to leaving your password in a file on your computer for attackers to find, but it's MUCH worse than that. Such a password file could be anywhere on your computer and an attacker would have to search for it and may never actually find it unless it was clearly labelled.

SSH keys are defined in your SSH config file and attackers know exactly where that lives. Using a passphraseless ssh key is more like leaving your password on a sticky note attached to your monitor.

This article is spreading bad advice here to users who don't understand why, and the author should update his post and retract it.
Would the Paul Graham of Columbus please come forward
A search engine performs the task of narrowing 1 trillion URLs into the 10 that are most likely to be what you are looking for. Associating a query with those 10 results takes teams of software engineers and datacenters full of computers. A user could not reasonably do this on their own.

Quite irrelevant to the discussion here. A user could suggest specific pages be indexed by Bing, no? If so, why can't a user let Bing automatically listen in on the pages they are visiting and index them if Bing wishes to? That's what Bing did.

Contact data is a list of the people you know. I had that list in my brain before I ever visited Facebook. If I am on different social networking sites, that list is mostly the same, because it is information about me that I already knew.

Again, pretty irrelevant. If we are talking about data ownership, both your contacts data and your clickstream data belong to you. You can do what you want with it. Some users choose to share it with Bing. That's their prerogative. I don't think even Google disagrees with that.

They just don't see the hypocrisy between this and their stance on Facebook.

Google does not access Facebook's social graph, because Facebook has not allowed them to.

Correct, and yet, Google's stance in the Facebook episode has been that Facebook should open up that data because it does not belong them, it belongs to the users. To be consistent with their stance on Bing, Google should never have created a big fuss about Facebook not opening up the data.

Similarly, clickstream data does not belong to Google. It belongs to the users.
Actually now you have VBA in Office 2011 for Mac, I don't see the reason to post a 4 year old link, especially when it is not applicable anymore, see for example:

http://www.microsoft.com/mac/products/whats-new
Dude, did you even read his entire one line post, or did you just rush straight into 'witty put down mode'?

Edit: also - people who voted this guy up - what the [redacted] is wrong with you? Reading comprehension: it's not that hard.
Gmail Tests Image Ads
The real keys to Facebook's success:

1) Prior campus projects made him locally famous.

2) An upper-crust seed population.

3) Exclusivity during expansion.

4) A clean interface which appealed to something other than the rebellious, "express myself" teen (i.e. not MySpace).

5) Timing. He hit the right audience at the right time.

6) Luck.

I don't doubt that there is a lot of skill at Facebook these days to keep it riding high on the social wave, but if you want to talk about what made Facebook successful, it's mostly the above.
These are really cool and understanding how magic is implemented is great, but when you are searching for the "tell_ape" method for 10 mins only to realize that method_missing is doing the magic, it really is a bit of a piss off. If you are going to do these tricks please for the nonwizard ruby coders out there make it blatantly obvious in your README or comments or tests.
I GREW up in Del Mar, Calif., north of San Diego. I got my first job the summer after eighth grade at a small Internet service provider. I called the owner, Christopher Alan, one day and asked if he had a summer internship or a job, and he took a chance on me. My mother would drive me to the train, and I’d take along my skateboard to go from the San Diego train station to the office.

Reading stuff like this is so surreal because it nearly mirrors my own experience starting out. I got my first job through a local linux users group mailing list (CEO took a chance on me to do sysadmin and scripting work) - my mom had to drive me to work after school and pick me up in the middle of the night after I was done.

Now I run a business and when I look back, it's astonishing how large a chance it really is to hire a kid who can't even drive to write software for your business. The 1990s truly were crazy.
Dyson's original concept was basically to completely obscure the star in a cloud of satellites. It would be a little inefficient, insofar as some satellites would obscure others at any given time, but it's at least physically possible.

There's been some speculation that the integrity of a Dyson shell (the thing most people know as a Dyson sphere) could be maintained by basically running large masses in orbits along the shell. Again, it would be a little inefficient (you're using some of the star's energy to power "not collapsing"), but we don't necessarily know it's impossible.
It's not something I did per se, but one former employer had mandatory pre-checkin code review. This is a controversial practice but in my experience, only with people who haven't really tried it.

Not only does this help find bugs, it will force you to write code that isn't embarrassing. You will end up communicating much more with colleagues; before, during, and after the code review process. I believe it will clean up, or at least address, almost every bad habit you have.

If you can't get this at work, try an open source project that has a similar review process.
Classic mistake: having someone else implement the site. How can you pivot, adapt, and make good use of feedback if you can't work on the site without having to pay money?
If you learned something from this, be sure to read http://www.jedi.be/blog/2010/08/27/ssh-tricks-the-usual-and-...
The article is making a valid point, but there is an equally valid counter-point that I think is being obscured. Many technical co-founders expect that coding is the entirety of what they will do, hence the shopping list of a non-technical co-founder who will do 'everything else'/'all the boring bits'.

If the only thing you - as a technical person - are bringing to the founders table is programming skills, then you're at the wrong table. Get yo bitch ass over to the 'low digit employee number queue'.

You might be one of the first employees, but you're not co-founder material. Technical people who only bring coding skills are just as worthless as non-technical people who only bring an idea.