HNHacker News
TopNewBestAskShowJobs

codyrobbins

1,168 karma · joined January 30, 2009

Former CTO of a few venture-backed startups and advisor to others. I’m trained as an engineer in both computer science and electrical engineering and later as a research linguist specializing in theoretical syntactic models. I have a strong technical background in modern web and mobile technologies and extensive applied experience in the product and business side of startups.

     Email: cody@codyrobbins.com
       Web: codyrobbins.com
   Twitter: twitter.com/codyrobbins
    GitHub: github.com/codyrobbins
 AngelList: angel.co/codyrobbins
  Facebook: facebook.com/codyrobbins
  LinkedIn: linkedin.com/in/codyrobbins
submissionscomments
codyrobbins··on In defense of the Google chef
Disclaimer: Only having read the WSJ article and knowing nothing more, I think it’s more or less a form of blackmail—the employees are unfairly being put in a no-win situation.

That being said, my takeaway was that they had thrown around equity so liberally that they’ve exhausted their employee options pool and it’s going to interfere with their ability to recruit going forward. Is that the wrong interpretation?

If it’s not, and given such a situation, do you think it’s fair to say that a startup should generally be trying to allocate its options carefully such that a chef doesn’t end up with $20M worth of equity?

codyrobbins··on In defense of the Google chef
Sure, not everyone can be a chef—I completely agree. I spent my summers working in restaurants growing up, so I’ve seen firsthand just how brutal the work is and how much skill it takes. But certainly there is no doubt in my mind that more people can be good chefs than can be good software engineers.

And, as somebody else pointed out, the chef's existence -- and the supreme quality of his work -- was one of the big draws for tech talent to come to Google. And, furthermore, by freeing the tech talent from having to worry about food or leave work to get it, he contributed to the value they created.

I didn’t set up a straw man, but I did draw some hyperbolic distinctions for the sake of exposition. (In fact, I worked as a line cook one summer and I wasn’t very good at it—so not everyone can even be a line cook.) There is obviously a spectrum, and if we’re going to point out fallacies then you’ve set up a false dichotomy: that there’s either things everyone can be or things few people can be. This isn’t true, and I’m simply saying that software engineers are a scarcer resource than chefs. I don’t disagree that the chef at Google legitimately contributed to the value the company created, but I think there are plenty more chefs that could have done so than there were software engineers who could have built the core technology the company was built on. My point is that the salaries are, broadly speaking, a reflection of supply and demand and not difficulty of work.

codyrobbins··on In defense of the Google chef
It’s good to be reminded of this from a standpoint of empathy, but at the same time I think it’s missing the fact of the matter: we don’t get paid more money because we work harder. That’s just a remnant of the Puritan work ethic. The economic fact is that we get paid more money because there are fewer people available to do what we do. Generally speaking, anyone can be a line cook, a bricklayer, or a janitor. When (more or less) anyone can do a job, it doesn’t pay as well because the available workforce is ample. If a software developer got paid as much money as a line cook, then software developers would be deployed at tasks that don’t warrant their more valuable time given their (relative) scarcity in the workforce. Deploying scarce resources in a suboptimal fashion is bad for everyone in an economic sense. It’s like using copper during the war effort to make brass bathroom fixtures instead of wiring for airplanes—it’s a poor (and potentially disastrous) use of the resource.

You can see this at work in NYC right now: the relative ease at acquiring financing means there are a lot of really dumb startups here right now with stupid ideas and no real market that are tying up valuable engineering talent which makes recruiting harder for legitimate startups that are genuinely creating value. Imagine if all the engineers who worked at Google during the early days were instead tied up working for Pets.com and Webvan such that Google was never really able to get off the ground and folded. That would have been bad for everyone, because Google ended up creating a lot of real value and Pets.com did not.

This same reasoning, I think, applies to the question of why CEOs get paid such astronomical salaries. The answer is that the kind of people with the skills to run a large company are extremely few and far between. Sure, a lot of them do fail at their jobs despite getting paid so much money; but that's not a reason for a hew and cry about how much they’re paid—it’s (usually) simply a testament to how hard the job actually is to pull of successfully. (Incidentally, it’s a common lament that the people at the top get paid disproportionately more than everyone else. But that’s just because the scale doesn't increase linearly—it grows exponentially. I'm not sure what the outrage against such a fact is—if you’ve taken differential equations you’ll remember that myriad complex mechanical, electronic, chemical, astronomical, biological, economic, etc. systems have nonlinear characteristics.)

So the idea is that salaries for scarcer resources are generally higher such that only enterprises creating sufficient value (i.e., profits, or at least a general confidence in future profits) to pay for them are the ones who get them. It’s certainly arguable whether this is what occurs in practice; and—while there are always exceptions, transients, and outliers—I think by and large it’s a good approximation.

This is kind of tangential to @jacquesm’s point, I know, because he’s simply pointing out that we should be cognizant that we get paid more for arguably easier work—but all the same I think it’s important to keep in mind that making things more ostensibly ‘fair’ may not always be in everyone’s best interests in a larger sense.

codyrobbins··on The mobile app is going the way of the CD-ROM: To the dustbin of history
I think the current popularity of web apps over desktop apps is driven by two different motivating factors: social and centralized storage.

The nature of the Web makes it well suited to building social apps on top of it. It would be hard to build social apps on an application layer that didn’t transcend physical platforms, because then there would be platform-induced delineations between the social groups that could congregate.

But the other motivating factor is that web apps by definition are a centralized container for the data you put into them. You use Freshbooks and you can access your invoices from anywhere. I think this will become far less important as cloud-storage-on-the-desktop services like iCloud mature and largely eliminate this advantage of web apps. Given this, don’t you think think we’ll actually start seeing a resurgence of non-social desktop apps that would previously have been built on the Web for centralized storage reasons?

codyrobbins··on The mobile app is going the way of the CD-ROM: To the dustbin of history
No. Somebody please stop this guy. After reading this I feel about him like the machines must have when they sent the Terminator back in time to kill Sarah Connor.

Web apps are to native mobile apps as Java apps are to native desktop apps: ploddingly slow with clunky non-standard UIs—a degraded, lackluster experience.

With some notable exceptions I think they can be a pragmatically motivated stopgap step (in regards to either bottlenecks in time or money) on the road to building a full native app. But saying simply that because they cost less time or money to produce as a sole justification for creating them, and ignoring all their shortcomings, is like suggesting everyone buy a circa-1998 Samsung flip phone instead of an iPhone simply because you can get one on eBay for $5. It doesn’t matter, because the flip phone sucks and the iPhone doesn’t—economics aren’t the only factor to consider.

If you need any more proof, remember what happened when the iPhone originally launched and there was no support for building native apps. Apple’s professed solution was for app functionality to be provided by mobile-optimized web apps. There was literally a sustained caterwaul by developers and users alike for the ability to create native apps on the platform, so much so that Apple did a complete 180 on their original stance.

codyrobbins··on Comcast begins IPV6 deployment
Does this mean I’ll finally, finally be able to get a static IP (albeit an IPv6 one) for my apartment? Or are they going to ultimately pull some obscene perversion out of their hat whereby you have to pay stratospheric business-class rates to actually get an IPv6 address, and their justification is because it comes bundled with an infuriating potpourri of cut-rate “business-class” nonsense that no one wants (web hosting, email, etc.)? The fact that I can’t just pay $10/month (or whatever) for a static IP on my residential broadband connection is so exasperating.
codyrobbins··on MongoDB 2.0 Should Have Been 1.0
MongoDB is on its way to becoming the default datastore for web apps.

In my experience there is no way that this is possibly true.

codyrobbins··on Google threatens to cut ties with Chamber of Commerce over Protect-IP lobbying
Orthography and lexical choice are two different issues. Spelling has to be standardized to facilitate written communication—word choice doesn’t because words inherently have semantic content.
codyrobbins··on Google threatens to cut ties with Chamber of Commerce over Protect-IP lobbying
It’s not nonsensical, and neither is irregardless. People use them for a reason and they’re both incredibly heavily attested usages.

But this argument has already been had before in a million places, including on HN: http://news.ycombinator.com/item?id=853100. Specifically, see my comment about why it’s hard to say that could care less is incorrect: http://news.ycombinator.com/item?id=854042.

codyrobbins··on NYC isn't catching the Valley anytime soon: Reflections on Startup School
I just have to say, the best coffee in NYC is actually La Colombe on Lafayette and Prince. I will buy you a cup if you haven’t tried it ;)
codyrobbins··on Why software patents are not fixable
The problems he’s discussing arise from the fact that litigation is expensive, and those with lots of legal resources can use their superior position to assert their will against those who can’t afford (or may not be willing) to defend themselves. That’s a valid issue, but a broader one that exists outside the context of patents. It’s not a valid argument against the patent system itself. A powerful chemical company that poisons a town’s water table can do precisely the same thing. Does that mean we should outlaw chemical companies? No, of course not. His argument is only valid in the context of arguing for wider reforms to the legal process in general that make this sort of abuse less feasible. And that’s a different discussion entirely.

This is precisely the point the other article today by Nilay Patel—which was so lambasted here—was trying to make: the arguments being made about patents don’t necessarily point to tearing down the system, but simply fixing the things that are wrong.

codyrobbins··on Large-scale Amazon EC2 Outage
I’m glad to hear that you didn’t lose anything critical. But snapshotting EBS volumes are not backing them up. If, by definition, it’s stored using the same service, and therefore susceptible to all the same catastrophes that might befall the service, then it’s not a back up. I always set up a local read slave of the database server which has hot-swappable hard drives that get rotated out of a safe deposit box or fireproof safe. The only way I can properly trust that things are being backed up properly are to do it myself.
codyrobbins··on The Moment Of Truth For Airbnb As User’s Home Is Utterly Trashed
This. I definitely think this entire situation calls into question the feasibility of Airbnb’s continued success and their business model in general. They’ll need to find some way to address these problems to maintain confidence in the site, and as the site’s audience grows it may not even be possible to do so.

I don’t dispute any of these things—my only real point was that it’s completely off-base to call Airbnb immoral for not compensating the woman.

codyrobbins··on The Moment Of Truth For Airbnb As User’s Home Is Utterly Trashed
Well, you haven’t addressed any of my points, but that’s fine. To answer your question, just because the transaction was consummated doesn’t mean she had to let the guy into her house. If the dude was suspicious or ungoogleable, she could have called Airbnb and explained the situation or she could have simply not left her key. Instead she just got on an airplane without thinking about it. That’s not Airbnb’s fault.

And you’ve just illustrated my point perfectly: if she hadn’t used the service, she would be fine now. But she used the service of her own volition; nobody forced her to; and she made the decision herself. Airbnb might have made the gun the guys used to trash her apartment with, but Airbnb isn’t the one that fired it: she pulled the trigger. Again, the people who trashed her apartment committed the crime here, though.

This is a business problem

I never said it wasn’t a business problem—that’s exactly what it is. But it’s not an issue of morality.

in what universe can you trust a service like Airbnb now?

I would never in a million years use Airbnb. Why would I leave a complete stranger alone in my house so that they could trash it and go through my things? You realize how insane that is, when evaluated outside the reality distortion field of the startup craze we’re in right now, right?

I think the genesis for your arguments is your desire to live in a world where you can trust a service like Airbnb. But if you just think about it for five seconds you realize anyone could do this and Airbnb in no way prevents it from happening. Just because Y Combinator funded it doesn’t mean it’s magical.

codyrobbins··on The Moment Of Truth For Airbnb As User’s Home Is Utterly Trashed
The utter destruction of your home at the hands of a service that aims to help you monetize it is ipso facto a bug.

Again, Airbnb didn’t destroy her home. Are you under the impression that someone from Airbnb itself was the one staying at her house?

Intent: create value. Result: destruction of value. Bug!

You’re basically defining what you want the responsibilities of Airbnb’s service to be and then faulting them according to those responsibilities. But those are not Airbnb’s responsibilities. Again, Airbnb doesn’t claim to prevent things like this, therefore it’s not a bug.

If they want to be the "Ebay of spaces" then they need to provide for some basic level of safety and security

No they don’t. There will be business consequences for not doing so, but they don’t have to. They can define their service to be whatever they want it to be. As it currently stands, their service is not meant to prevent this from happening.

They're incompatible, so we won't ever work together.

This came through loud and clear the first time you patronizingly said it.

codyrobbins··on The Moment Of Truth For Airbnb As User’s Home Is Utterly Trashed
You’re patting yourself on the back for not selling a buggy app to people? That's a completely different situation than that in the story at hand. Airbnb worked precisely like it was supposed to—there were no bugs. It’s just that Airbnb is in no way supposed to prevent things like this from happening.

If you do harm

Again, you’re not addressing the simple fact that you’re working from the assumption that Airbnb itself did harm here. They simply didn’t.

Doing the right thing is more important than making money.

Clearly Airbnb does not believe that doing so would be ‘doing the right thing.’ You’re simply calling them evil instead of recognizing that they have a different—and quite defensible—point of view concerning their responsibility.

codyrobbins··on The Moment Of Truth For Airbnb As User’s Home Is Utterly Trashed
Give me a frigging break!

I don't care what the long-term implications are

Clearly you’re not a business person if you wouldn’t care what the long-term implications of your company’s response to this were. They have responsibilities to investors, employees, and other users—they’re (rightly) making a decision with those stakeholders in mind, not the woman who had her house ruined.

I don't care about cost

Again, clearly you’re not cut out to run a business if you don’t care about cost.

If my business does this to someone I make it right.

Airbnb didn’t do this to her. The people who did it to her did it to her. Airbnb provides a marketplace for these interactions to occur—nothing more. The users cannot abdicate their personal responsibility not to use the service carelessly. I mean, we’re talking about letting people into your home here.

Is a car manufacturer liable when a driver runs over a jaywalker because they were texting on their phone? No. Is the phone manufacturer liable? No. Should I be sued when I recommend my accountant to my friend and the accountant defrauds him? No. Should Craigslist be liable if precisely the same thing happened through Craigslist? No.

Anything less is simple villainy. This is a test of human decency.

Calling this villainy is one of the most hyperbolic statements I’ve heard in living memory. So is declaring, as if it were agreed upon fact, that Airbnb is evil if they don’t reimburse her.

If you are going to enjoy the rewards of your business, you have a moral obligation to ensure that you make things right when that business harms someone else.

If your company actually does something to somebody, then sure—but not when you’re company doesn’t. Airbnb didn’t do anything to her: she let a stranger into her house for a week without thinking about it! I’m not blaming the victim, I’m blaming the people who did it to her—but I’m certainly not blaming the middleman.

What happened to this girl sucks, but your post is overly emotional and absurd. It’s not Airbnb’s moral responsibility to do anything about this. They may choose to from a pragmatically-motivated customer relations, reputation, and corporate image standpoint—and sure, it would be an all-around charitable and nice thing to do—but I completely disagree with the claim that they have any moral responsibility to do so. Airbnb can do whatever they damn well please and what they believe is in the best interests of their business.

What I think is indecent is creating an artificially high and illogical holier-than-thou moral high ground divorced from the realities of running a $1B business that you then use to drum up a public crucifixion of a company that doesn’t live up to said standard.

codyrobbins··on Introducing BrowserID: A better way to sign in
What bearing does the fact that Google and Yahoo chose shitty hard-to-remember OpenID URLs have to do with the overall fact that OpenID uses URLs for authentication? That’s like saying using email addresses for authentication is a terrible idea because mail administrators can assign really hard-to-remember email addresses. The solution is simple: set things up so they’re not hard to remember. Again, there is no reason why your OpenID login can’t be ‘name.my-open-id-provider.com’.

I would be willing to bet Google and Yahoo made their OpenID URLs hard to remember because they already had single sign on products that they wanted in the limelight preferentially over OpenID. However, cursory support of OpenID made them both look like supporters of open standards even if their implementation (hard-to-remember URLs) doomed it to underuse.

codyrobbins··on Introducing BrowserID: A better way to sign in
To this day I still do not understand how this inane argument happened to be the single thing that killed OpenID. How is ‘cody.my-open-id-provider.com’ more confusing as a login than ‘cody@my-email-provider.com’? Hint: it’s not. I’m not one for conspiracy theories, but the whole URL-versus-email argument against OpenID seemed like the excuse various people used to put a nail in OpenID’s coffin when they didn’t like it for other less defensible reasons.
codyrobbins··on The Problem with the iPhone's Home Button
It’s likely because we read from left to right. And bear in mind that ‘right’ being correlated with ‘forwards’ is a cultural convention—other cultures may code such relationships differently.
codyrobbins··on Diver Snaps First Photo of Fish Using Tools
The real source of the ambiguity here is the lack of what’s known as a complementizer [1]—such as the relative pronoun that—to delineate the relative clause boundary, as @xtacy implies with his last option. English happens to allow this slot in the syntactic tree to have no overt realization [2] [3], but when it goes unfilled with anything but trivial relative clauses it can introduce ambiguity.

As an aside, this particular sort of syntactic ambiguity happens to largely arise in the context of newspaper headlines—just as has happened here—since complementizers are generally dropped in telegraphese. These ambiguous sentences are so common that they have their own term: ‘crash blossoms’ [4].

Here are the two potential parse trees with an empty complementizer:

  1)   [Diver snaps [first photo [of [fish using [tools]]]]]
  2)   [Diver snaps [first photo [of [fish]]] using [tools]]
The incorrect parse is (2). In any event, disambiguating it is simple—just add an overt complementizer: ‘Diver snaps first photo of fish that’s using tools’. You can see why this disambiguates:

  3)   [Diver snaps [first photo [of [fish [that is [using [tools]]]]]]]
  4) * [Diver snaps [first photo [of [fish]]] that is using [tools]]
Here (4) is ungrammatical because in English snap isn’t a verb that accepts a clausal complement (unlike a verb such as, say, think or persuade), thus you don’t parse the sentence that way and (3) is the only possible interpretation. Cf. (5, 6): there’s nothing I can come up with to put in the relative clause that would make the sentence even remotely grammatical. My interpretation of (7) is that it’s marginally acceptable (perhaps in a specific context: ‘What do you snap with your camera?’ ‘Oh, I snap that flowers bloom.’) but snap in (7) is intransitive whereas the snap we’re discussing is transitive.

  5)   I think that Hiroki Narimiya is awesome.
  6) * I snap photos that flowers bloom.
  7) ? I snap that flowers bloom.
@ggchappell: The parse where the photo is the one using the tools (shown as (8) below) may from a purely tree-parsing standpoint be theoretically possible, but from an actual linguistic point of view I doubt you could typically elicit such an interpretation from an actual speaker. An actual syntactic distinction is often made in language between animacy and inanimacy [5]. In traditional syntactic theory, the verb use has an argument structure [6] requiring an agent; but since a photo is inanimate it’s not marked as an agent and thus cannot provide the verb with a subject, violating various hypothesized syntactic rules and making the parse unacceptable.

Compare (9) below, which is acceptable. The relative clause is passivized, and thus the subject of the clause (the photo) is the theme rather than the agent and there’s no problem.

  8) * [Diver snaps [first photo [of [fish]] [that is [using [tools]]]]]
  9)   [Diver snaps [first photo [of [fish]] [that can be developed]]]
See, I always knew that graduate degree in linguistics would come in handy for something!

###

[1] http://en.wikipedia.org/wiki/Complementizer

[2] http://en.wikipedia.org/wiki/Relative_clause

[3] http://en.wikipedia.org/wiki/Reduced_relative_clause

[4] http://en.wikipedia.org/wiki/Syntactic_ambiguity

[5] http://en.wikipedia.org/wiki/Animacy

[6] http://en.wikipedia.org/wiki/Theta_role

codyrobbins··on Google to Retire Blogger & Picasa Brands in Google+ Push
I know absolutely nothing about marketing so I may be wrong, but the problem I immediately see with this is that one can only make so much money selling aspirin or soap. I assume that at a certain point these brands realized that the brand name was more valuable in terms of the credibility and instant recognizability it could lend a larger array of products than its value attached to a single one, even if the name is affected negatively in the context of that single product.
codyrobbins··on What every programmer should know about time
Ugh, I feel that this is one of the single poorest time-related pratices—from a UX perspective—short of not displaying the time at all. Please don’t follow this advice. It makes it really easy for the developer because there’s no need to deal with time zones and things like DST. However, showing a relative time in many situations is completely opaque. If something happened ‘14 hours ago’, did it happen at lunch time or 3 PM? A lot of times people want to know the time of day something happened, not just how long ago it occurred. Here you can do some arithmetic in your head to figure it out, but that’s a major annoyance. And once the relative time flips over to ‘X days ago’ the time information is completely lost. Similarly if it says ‘About 3 months ago’ it’s impossible to know if that means March 15 or April 1 or April 15 or anywhere in between, never mind the time of day. At the very least the full date and time should be displayed in a tooltip so that it’s available if needed. Ideally relative times shouldn’t be used alone except in situations where the relative time is absolutely, unarguably the only information that could ever need to be known.
codyrobbins··on Electronic Arts Hates Strong Passwords
Yes, I was just going to mention banks as well. I have dealt with multiple online banking systems for major banks that enforced ridiculously low maximum password lengths and alphanumeric-only restrictions. It's one thing for Electronic Arts to have not thought through this stuff, but another entirely when you're talking about a banking system.
codyrobbins··on What we learned from putting a ridiculous billboard on 101
Are more billboards coming in the future?
codyrobbins··on GitHub for Mac
Agreed—the concept of porting UIKit to OS X is insane to me. The Mac desktop is not an iPhone! I don’t want to interact with a desktop app as if I were on a phone—especially not an app that I’m ostensibly supposed to use for development.

That said, creating a desktop interface for GitHub is a brilliant move. Bravo!

codyrobbins··on Redditor Explains Why Apple Continue Making Frail Power Cables
I think it’s completely wrong to say there’s no user experience on cables. What about the fact that my sofa has to be a full four inches away from the wall because of the strain relief on the cord of the lamp I need to plug in behind it? There is no reason the cord actually needs that four inches of horizontal space—it’s just poor, thoughtless design that results in a poor user experience. Whoever designed the lamp should have put as much thought into the cord as they did into the rest of it, but instead it’s just an afterthought. To my way of thinking at least Apple has the guts to experiment with a different approach and see what happens instead of just applying the same good-enough solution everyone else mindlessly does.
codyrobbins··on What happens to all the Asian-American overachievers when the test-taking ends?
The word mediocre is subjective and this just devolves into an ontological or semantic argument surrounding the meaning of mediocre. What’s mediocre to you may very well not be to lots and lots of other people. Or—if you prefer—in the form of an aphorism: ‘One man’s trash is another man’s treasure.’
codyrobbins··on What happens to all the Asian-American overachievers when the test-taking ends?
First of all, this is a false dichotomy—you’re presenting an example with two fantastic iOS developers who don’t self-promote and one mediocre one who does. In reality, it’s probably more likely the fantastic iOS developers who self-promotes gets noticed over the fantastic iOS developers who doesn’t self-promote.

Ignoring your rhetorical feint, though, I think it’s completely reasonable to say that—by definition—you cannot be a fantastic iOS developer if you produce things that nobody knows about or uses. I would call the mediocre apps that get usage the product of a superior developer than the good ones that don’t. Software that exists in a vacuum with relatively little adoption is more or less useless. (At least, if we’re talking about a consumer-focused platform like iOS.) It doesn’t matter how elegant your apps are if no one uses them.

codyrobbins··on Ask HN: Help, Investor wants money back in 7 days "Or else"
Ah, I see what you mean. When I read it, though, it didn’t strike me at all as though OP went out of his way to use gender neutral terms. I guess it didn’t strike PG that way either, if he assumed it was a guy too?

I think they may be better described as a referentless third person pronoun rather than a genderless one in a lot of circumstances. The genderlessness is more of a consequence of having no referent.

← PreviousPage 2 of 7Next →