Why not? Can we not think outside the box even when we've been outside the box? Or am I missing something?
4,866 karma · joined October 7, 2008
Why not? Can we not think outside the box even when we've been outside the box? Or am I missing something?
def factorial(x):
return x * factorial(x-1) if x > 1 else 1http://code.google.com/p/pylevenshtein/
However, I've found the Jaro-Winkler distance to be more useful than the Levenshtein. You can find good implementations for Jaro out there as well.
The motivation for the App Store is simple: consumers want an easy way to buy apps, and developers want an easy way to sell apps. If you want to take advantage of the payment processing, bandwidth, store interface, and marketing provided by the App Store, you have to adhere to their ToS. I'm sure Yahoo! Store has ToS as well.
However, if you want to roll all that on your own, go right ahead. As pointed out in this article, no one has done more to support you in that endeavor than Apple -- including a lot of support in WebKit and iPhone OS specifically for web apps on these devices.
It's not just a question of web vs. native, either. Even if all iPhone apps were HTML5/CSS/JS, you'd still have to adhere to Apple's ToS in order to sell through the App Store, and you wouldn't have to adhere to them if you sold through your own store.
Feedback from testers is great, but I've found a bigger reason why I love our QA team. For whatever reason, it's hard to implement something and test it at the same time. It's just hard to make my brain think in both modes at once. It's also hard to test something that I've implemented, because my brain is biased by the thought processes it used during implementation. Trying to think in both modes (implementation and testing) means I'll probably end up doing neither effectively. If you have a great QA team, you don't have to think in both modes. It's great.
That hints at his point about letting incompetent programmers do QA. I completely agree with him. A tester thinks differently than a programmer. Hire great testers. So many companies make that mistake.
I'm glad to see Joel take a public stand on automated tests, too. Automated tests have their place and their value, but his criticisms of them are completely valid. No amount of automated testing can obviate the need for good human QA. For some applications, automated testing can be such a pain to get right and maintain, that it's often more work than it's worth.
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-Jun...
Patents are playing a large role in ensuring that what could be a wonderful thing for the web will almost certainly not be.
This is a fair question. We feel confident that we are looking at the tablet device for two main reasons, that I can share with you. Also note that, as a company, we have experience tracking new Apple hardware devices in the past.
1) If this were an iPhone we were looking at, the hardware would tell us when we ask it (via the software). So we can rule out that this is an iPhone. Also, we already see verified iPhone devices testing OS 4.0 and these leave (Apple's Cupertino, CA) campus, whereas this device does not. This makes sense given the secrecy around the new tablet device as the launch event nears.
2) The apps being tested match up to what the devices is supposed to feature (e.g., news, books, etc.). We cannot share further detail here due to Terms of Service agreements we have with customers that use our service, but feel that if you were able to see the data we see, at the level of granularity, it would be clear to you as well.
Of course the truth will be revealed on Wednesday, but we wouldn't publish such a report without a high level of confidence.
Flurry is not interested in building a business on rumor, but rather authority, credibility and accuracy.
Point (2) seems less than rock solid, but (1) lends a bit of credence, especially since they've already seen iPhone OS 4.0 devices. It could just be that they're doing less testing of apps on 3.2 iPhones, however.
After that short period, though, I became very comfortable communicating in Russian. I realized that there's probably no way to learn a language without going through that painful period. I think the same is true of programming languages. You're going to have to stumble through a couple thousand lines of horribly written code before you become fluent. You might as well start writing those now and get it over with.
I just started in a new roller hockey league this week. I still can't skate backwards well. I know that if I want to learn I'm going to have to fall on my butt a bunch of times. As long as I stay cautious and don't allow myself to fall, I'll probably never learn.
The fact that it's run on a server machine and not on a desktop machine has little effect on performance, and it probably doesn't make sense for Dropbox to provide the resources for good search when your desktop should be able to do a fine job of it.
If you're being hired as a C-level executive, you might expect up to 2% - 3%. If you're being hired as an engineer, expect more like 0.25% - 0.5%. I'm sure it varies quite a bit, but that's what I've seen personally and heard from friends.
As you point out, Wave's UI is horrible for chat. That's why we're building http://shoptalkapp.com; it's similar to Campfire. We use it every day and couldn't live without it. It's like a virtual office.
Why does he need anyone to switch? This competitor has just launched their product. That means they have very few users and almost no brand recognition. 99.9% of the world will have no idea who launched first and won't care.
You don't need to convince anyone to switch from your competitor's product. You just need to convince people to use your product, which is a problem you already had. In that sense, the launch of a competing product shouldn't affect your roadmap at all.
Longer term, you should be worried about the huge imbalance in resources. That's solvable, though: if you get any traction with your product you can raise funds and hire a team.
That's why we've focused on reducing the latency for ShopTalk. Even using HTTP and comet, we've been able to give it a real interactive, rapid-fire feel. Chat isn't as sexy as newer trends like microblogging, but it's far more useful.
I see two big features here: 1) Recognizable URLs, and 2) analytics.
Do all HTTP requests need to go through bit.ly to achieve these features? Nope. http://nytimes.com is a pretty recognizable URL, if you ask me. I'm sure their server logs provide all the analytics they need as well.
Someone should "cut out the middleman" and invent a world wide web that doesn't require URL shorteners. Oh wait, Tim Berners-Lee already did that.
The insurance company is paying his salary because it costs them less than would the care that he manages to deny. If he didn't exist, the insurance company's costs would increase. This means that insurance premiums would have to increase. Whether you buy your insurance directly, or it's deducted from your paycheck, or your employer pays for it in full, that increased cost of insurance premiums would trickle down to you in the end.
This article was originally published on the User Interface Resource Center (UIRC). For more info, please see http://uxmag.com/uirc
Just FYI...
The simple truth is that people like the interviewee in the article just don't work on nearly as hard of problems as do Google engineers. Being an engineer myself, I've never had a finance job, but I've had plenty of friends and roommates who have. They need to know some math and have some Excel skills, but most of their time is spent on phone calls and Powerpoint decks. That's why even an easy first question in an interview for an engineering position (e.g. write a C function that reverses a string) is more difficult than the questions asked of these guys. Just look at the example of the most grueling question in the article. Describe the process of a leveraged buyout? That doesn't really require any analytical skills, creativity, or problem solving.
I really think it's suboptimal to have finance people running our businesses, Wall St., and our economy. In my experience, they have a hugely inflated sense of self-worth, which is based mostly on their hugely inflated salaries.
I've never been a fan of this kind of blind arrogance in the finance industry. I hoped the recession would at least have some effect on that, but it probably won't. Engineers don't have nearly enough power in this society.
He asks, "Which of the following ways would you think gave you the most valuable feedback?" He submits that almost everyone would agree the real hammer will provide more valuable feedback than the paper or foam ones. This part is true. The next statement is false. He states that UCD practitioners would have chosen differently had the product been a web site instead of a hammer. They would have chosen the paper prototype, he says. That's just not true. UCD advocates the use of paper prototypes, not because they provide more valuable feedback, but because they are much easier to build. This means that you can test more of them in a shorter period of time. That's a very important distinction.
His graph of the UCD process essentially depicts it as a waterfall process, where there are several design steps with big Implement and Deploy steps at the end. That's also usually far from the truth. UCD is very iterative and, if done correctly, involves launching early and using data from real-world usage at each iteration.
It's easy to criticize something if you fabricate its weaknesses. The title of this post is pretty ironic.
Edit: Sorry, I know HN doesn't encourage one-liners and jokes, but I couldn't resist this one... I guess you had to be at Startup School to appreciate it.
I also like the application of these thoughts to addictions, in all forms. Any addiction is an incredible loss of power.
Spend that money (and more) on getting everyone a MacBook Pro as well. As anonjon points out, if you don't give out laptops you might be discouraging working outside the office more than encouraging working at the office. An important part of startup culture, imho, is to not require face time at the office.
Shameless plug: I agree with you that encouraging collaboration is key. Since lots of teams are working in a distributed fashion these days, we think they need some other way to collaborate effectively. This is why we're building http://shoptalkapp.com . We've found that it even encourages more collaboration for those that are in the office.