I read that entire article and I honestly have no idea what the point was. I was excited to learn about how a RESTful API was employed in a heads-up application and learned...nothing.

If every /. comment was this interesting and informative I would read /. a lot more.

No no, it's a mad lib. Like has the company underpants.

Yeah, I think you're right though.

Right...he didn't spell it out once.

Otherwise your Discrete Interface Control Knob might fall off.

Thank you, this confirms that the question is in fact as boring as it appears to be.

Seriously, is not writing the acronym out some sort of geek badge to you? Learn how to write like a professional instead of a fucking child.

I didn't say that, I said it wasn't designed by asking users what they want.

And I think understanding how systems will be used is a hallmark of good engineering.

No, lousy engineers are responsible for all that. The products we build are constantly praised by customers for their ease of use and simplicity of design because we spend hours worrying about every little detail. The problem is that you think UI/UX people aren't engineers. And no, the iPhone is clearly a hardware AND software product. Don't draw arbitrary lines around people or technologies, it won't get you anywhere.

The iPhone was not built by asking users what they want. It was built by clever engineers solving a problem. Users don't know what they want or what is possible and there is no way to short-circuit or work around this fact.

I'm definitely not an expert but I wasn't referring to the last nine years, which seems like so small a sample as to be insignificant.

Also, I was under the impression that there was an unexplained increase in the number of cancer incidents in the last several decades. Clearly it's a long-shot but it does seem like it's worth investigating...