Evernote rival Springpad is announcing support for Android Honeycomb tablets and is also debuting offline access via its popular chrome web app.
Similar to Evernote, Springpad serves as a multi-platform digital notebook. The service allows you to jot down notes, save websites, images and more. Springpad will then categorizes your saved content, and allows you to share your notes, set reminders and more. The app goes a step farther to analyze your content and then serve you alerts to relevant news, offers and deals. The app’s semantic data technology allows you to save products, books, movies, recipes and more, and automatically get enhanced information, including price drops, local availability and coupons.
The support for Honeycomb includes features such as optimized display for the larger screen size and configurable widgets to create, save and view their notes for immediate access on the tablet homescreen. The app delivers cross browser and app sharing making it easy to save information from other sites and apps. Springpad’s Chrome web app, which is ranked as one of the top 20 most popular apps in the Chrome Web Store, allows users instant and universal access to their Springpad account, even when offline.
Honeycomb tablet support is significant for Springpad because the app’s growth has been fueled by mobile adoption. Nearly half of its users are using its Android app and a third are using Springpad via an iOS device.
Evernote has around 9 million users now and SpringPad just passed the million mark so the startup definitely has a ways to go. But the company’s ability to add intelligence to notetaking and possibly monetize off of users with personalized deals, content and more could help boost usage.
Last week I wrote a post about my current investment policy at TechCrunch, and pointing out already disclosed financial conflicts of interest. Our primary duty to readers, as I’ve said many times, is transparency. To that end we will (as we always have) be extremely careful in disclosing any investments I’ve made in startups or in venture funds. And these interests will be disclosed even when other TechCrunch writers are covering these companies.
In that post I said that there would be a lot of criticism headed our way from our competitors. And that’s exactly what happened. AllThingsD calls me “vaguely icky.” The Atlantic Wire says what I’m doing “lowers the bar for journalistic independence.” And Tom Foremski says “It’s best to have a blanket policy of no investments allowed. That way readers can read the news without having to do all the leg work to figure out if there is any bias.”
So, hold on a minute.
We can argue all day about whether or not my policy is a good one. You’ll have your arguments, I’ll have mine. But the really important thing to remember, as a reader, is that there is no objectivity in journalism. The guys that say they’re objective are just pretending. Everyone is conflicted in different ways, and yet the “rules of journalism” don’t require any sort of transparency or disclosure unless it’s a direct financial conflict. I’m going to have to write a longer post about his yet again.
But when you read a tech blogger call a CEO “tough and misunderstood,” should you know that the CEO in question is social friends with that blogger, and leaks confidential information to her? The answer is yes. But you’ll never know. Or when the same CEO is called incompetent by another blogger who was just turned down by said CEO to speak at his conference. Disclosed? No. Conflicted? Yes.
Like I said, that’s a different post. But in putting this current issue to rest, there are some things I’d like to point out.
AllThingsD’s Kara Swisher, the chief whiner about our policy, is married to a Google executive. This is disclosed by her, but I certainly don’t see it as any less of a conflict than when I invest in a startup. And yet she whines. One of her writers, Liz Gannes, is married to a Facebook consultant. She covers the company and its competitors regularly. She discloses it as well, but it isn’t clear whether or not her husband has stock in Facebook. That’s something as a reader I’d like to know. And regardless, it’s a huge conflict of interest. I think someone will think twice before slamming a company and then going to sleep next to an employee of that company. Certain adjectives, for example, might be softened in the hopes of marital harmony.
Foremski, the other chief whiner, is a real piece of work. Despite railing against my policy, he has his own direct conflicts of interest. The man who said just a week ago how horrible I am for investing in startups has financial interests in a whole slew of tech companies – “Disclosure: Current and past consulting clients and sponsors of Silicon Valley Watcher: Pearltrees, Intel, Tibco Software, Edelman, Infineon Technologies, SAP.”
And he isn’t so good about disclosing these interests. If one of our writers pulled this stunt they’d be fired in a second.
Why do the people who complain the most about TechCrunch have these vague conflicts of interest themselves? Why aren’t they more forthcoming in their disclosures? How do they justify their hypocrisy, even to themselves? Seriously, how?
Look, I’m still new to this journalism thing. I treat our readers the same way I’d like to be treated. With full and complete disclosure. I’m really sorry if that upsets the old guard. But the reality is this. The people complaining the most are the people who are the most deeply conflicted. They’re the people who are, at best, vague about their own conflicts of interest. Right and wrong don’t seem to be concepts they worry about too much. Nor do they seem to be overly concerned with hypocrisy or even the basic underlying lack of logic in their rants.
Really, it all came into focus for me this week. A major news publication asked for “my side” after all this complaining. I spent a half hour on the phone with him at his request. And he never wrote. Why? “My editors want to leave Arianna dangling in the wind,” he said, referring to the fact that Arianna Huffington, my boss, was taking heat for this situation. It never occurred to him that he just killed a story because that story might help a competitor (Huffington Post), and how screwed up that was.
I have little hope for this industry until the last of the old guard have finally been put down. They do NOT control the news. They do NOT control opinion. They do NOT get to say who gets to write content and who doesn’t. And they do NOT get to rant about their ethics when they constantly fight against simple transparency.
Swisher doesn’t get to complain about my investment policy when she is married to a Google executive, and when we can’t figure out whether or not one of her writers owns Facebook stock through her husband. And don’t even get me started on the time her employer, the WSJ, killed a story that was critical of its sister company MySpace, and then denied it. Foremski doesn’t get to tell me my policy is unethical when he has financial conflicts all over the place and seems unconcerned with proper disclosure and transparency. And major media doesn’t get to preach to me about their ethics policies when they kill stories because their editor wants to keep Arianna Huffington squirming.
Before I started TechCrunch I never understood how screwed up this whole news world was. It’s ugly as hell out there, people. These people, the tech press, just disgust me.
We’ve all lived the nightmare. A new developer shows up at work, and you try to be welcoming, but he1 can’t seem to get up to speed; the questions he asks reveal basic ignorance; and his work, when it finally emerges, is so kludgey that it ultimately must be rewritten from scratch by more competent people. And yet his interviewers—and/or the HR department, if your company has been infested by that bureaucratic parasite—swear that they only hire above-average/A-level/top-1% people.
It’s a big problem, especially now. There’s a boom on. I get harassing emails from recruiters every day. Everyone’s desperate to hire developers…but developers are not fungible. A great coder can easily be 50 times more productive than a mediocre one, while bad ones ultimately have negative productivity. Hiring one is a terrible mistake for any organization; for a startup, it can be a catastrophic company-killer. So how can it happen so often?
Like many of the hangovers that haunt modern software engineering, this is ultimately mostly Microsoft’s fault.2 Back when they were the evil empire where everyone secretly wanted to work, they were famous for their “brain-teaser” interview questions – Why are manhole covers round? – and, of course, they asked new university graduates about computer science theory; “Write me a binary search.”
Everyone wanted to be like Microsoft, even Google, until everyone wanted to be like Google (until recently); and so that interview meme persisted. Check out these two recent posts on the subject of interviewing, courtsey of Hacker News: one from a would-be employee, one from a Google interviewer. A couple of illuminating quotes from the latter: “I’m not even necessarily saying that this is a good metric” and “If it’s any consolation, at least we don’t ask gotcha riddle questions anymore. Those were especially offensive.”
It’s nice to see that Google have almost sort of realized that their recruiting algorithm is problematic. Too bad they haven’t fixed it. See also Jean Hsu’s “How Effective Are Technical Interviews?” The fundamental problem is that the skills required to pass today’s industry-standard software interview are not the skills required to be a good software developer. Oh, there’s some correlation, but it’s like the Oakland Raiders always drafting the fastest runners available, only to discover to their endless dismay that the NFL is not a foot race.
Actually it’s worse than that. At least wide receivers have to run, whereas I can guarantee you, without fear of contradiction, that no software engineer will ever have to write a binary search after they are hired. It’s like choosing a contractor because they know how to forge and cast steel using coal, iron, an oven and a bellows, when they actually need to know a) the address of the nearest Home Depot b) what to do with the steel once they buy it.
Joel Spolsky once correctly explained that you’re generally looking for two things in an employee: Smart and Gets Things Done. (Academia is teeming with people who are the former but not the latter.) First, though, you have to establish something else: Not Completely Inept. You’d be amazed how many totally incompetent people show up for technical interviews. Google’s binary search is presumably intended as their “FizzBuzz” – a low bar you have to hurdle just to get in the door. But a FizzBuzz should take all of five minutes, before the real interview begins.
So what should a real interview consist of? Let me offer a humble proposal: don’t interview anyone who hasn’t accomplished anything. Ever. Certificates and degrees are not accomplishments; I mean real-world projects with real-world users. There is no excuse for software developers who don’t have a site, app, or service they can point to and say, “I did this, all by myself!” in a world where Google App Engine and Amazon Web Services have free service tiers, and it costs all of $25 to register as an Android developer and publish an app on the Android Market.
The old system was based on limited information—all you knew about someone was their resume. But if you only interview people with accomplishments, then you have a much broader base to work from. Get the FizzBuzz out of the way, and then have the interviewee show and tell their code, and explain their design decisions and what they would do differently now. Have them implement a feature or two while you watch, so you can see how they actually work, and how they think while working. That’s what you want from a technical interview, not a measure of its subject’s grasp of some antiquated algorithm or data structure. The world has moved on.
1Yes, I am being deliberately sexist here, because in my experience those women who write code are consistently good at it.
2I don’t mind that Bill Gates is a megazillionaire; he’s done a lot of really interesting and innovative stuff. I do mind that a lot of unworthy people rode his coattails to minizillionaire status, eg the inventor of Hungarian notation, probably the dumbest widely-promulgated idea in the history of the field.
Like Pinger, Talkatone allows you to make phone calls using Wifi. Unlike Pinger, Talkatone uses Google Voice as a channel to let you make and receive phone calls to and from your phone contacts, for free. While Pinger, using Textfree with voice, gives you a certain amount of minutes free and then charges your iTunes account or asks you to complete tasks, Talkatone, after some jiggering of your Google Voice account, allows you to make unlimited calls without having to jump through any additional hoops.
To set Talktone up log into your Gmail account and select the “Call Phone” option under Chat. Use the “Call Phone” option to make one call to a regular phone number. Then sign out from Google Chat and return to Talkatone. Make a phone call from its phone widget and you should be good to go there.
In order to receive incoming calls, you have to upgrade your Google Voice account to get a phone number and select “Forward to Google Chat” on the Voice Settings page. You can then receive calls to your Google Voice number in Talkatone.
This latest Talkatone release also lets users in the US and Canada send and receive unlimited SMS messages via Wifi, using just their data plans. It includes an audio compression upgrade to improve voice quality over weaker networks.
Talkatone is particularly useful for phone deadzones like TechCrunch offices, but might be a godsend for people who turn off their cell service on trips abroad and just use their data plans. Imagine being able to make calls from French hotel Wifi or even on a plane?
Users of Google Chrome are probably aware of the three channels you can use depending on how cutting edge you want to be (and how much you mind bugs): Dev, Beta, Stable. But ever since last year, there’s actually been a fourth channel as well that’s less publicized: Canary. Sadly, it has been a Windows-only build until now. But it looks like that’s about to change.
Given the talk in the Chromium development forums, it looks as if Google is just about ready to push out a Canary build of Chrome for OS X as well. In fact, it looks to already be working, they just need to add a download link somewhere so that people can actually get it. And that seems likely to happen soon.
Peter Beverloo, a developer who tracks Chrome and Chromium closely (and appropriately will soon be working at Google on the Chrome team) pointed out this morning that Chrome version 13 should be the first one to gain Canary status on OS X. As Beverloo notes:
While it has not been released yet, Google does seem to be ready to release Google Chrome Canary for Mac OS X systems. The browser cannot be made the default browser through the preferences and the release monitor says that the latest version was released today, using the same revision as Windows’ Canary.
Sure enough, looking over the “OmahaProxy” numbers that Google uses to keep track of Chrome progress across all platforms, there is now a “mac canary” build. And yes, it’s 13.0752.0 — just like the Windows branch. Both were updated today.
We’ve reached out to Google about the possibility of Canary finally coming to OS X, but have yet to hear back. But there are even more clues that this in the case tucked away inside threads on the development forums. For example, here you can see a screenshot of the Canary welcome screen on OS X — you’ll note the all-yellow icon, the key visual cue to let users know which build they’re using.
Why care about Canary? Well, if you want to absolutely be on the bleeding edge of Chrome, it’s the place to be. Technically, Canary is a pre-Dev build of the software that gets automatically updated daily (or so) with the best stuff from Chromium. Sure, you could just download Chromium itself, but that is far less stable as it’s updated many times a day. And you have to manually upgrade it. And plug-in and codec support can often be lacking.
Plus, the entire point of Canary is that you can install it and run it alongside another version of Chrome. This means that you could keep the stable version on your system for your real work, and load up Canary when you want to play with the new Chrome features that won’t be released for weeks or months. For example, Google has just released Chrome 11, but Canary is already on Chrome 13.
Of course, Google has been trying to downplay the version numbers now that they’re upgrading the browser every six weeks or so. But this hasn’t stopped them from touting new releases every so often.
And one more thing: looking over the Chromium development calendar, it looks as if the plan right now is to at least get to Chromium version 16 before the end of this year. That’s set to branch in October, which should give Google plenty of time to get Chrome 16 out the door before the new year. For some context, last May, Google unveiled Chrome 5.