robspychala
Joined 18 years ago
Karma
246
Submissions
38
Member since
Dec 9
Recent submissions
Comment · 9 years ago
Comment · 11 years ago
From the employees' perspective:
Take home tests are the worst. Company says take home test will take 3 hours to complete. They never do. Schedule 2x or 3x the estimate. Especially if you want to impress the reviewer.
You send it over, then the company says no or yes, only to move to new stage.
In the worst case you ruined your weekend and received a no. But the company just took 10 minutes to arbitrarily reject your application.
From the company's perspective:
I've seen applicants receive friends'/roommates'/spouse's help on take home tests. Not a good indicator at all even with a glowing submission.
Comment · 11 years ago
this sucks but it's not a new technique
music clubs of 15 years ago didn't pay artists for your "12 free CDs" either
Comment · 13 years ago
also happens when you try to view iTunes movies or shows while controlling your Mac with a remote desktop connection.
super annoying.
Comment · 13 years ago
super cool. we are doing something similar with Birdseye Mail's Smart Actions http://www.birdseyemail.com/developers ... we opted to reuse open graph tags in favor of creating a new JSON / JavaScript syntax
Still really great that Google signed up partners for the rollout. It's a bit of a chicken vs. the egg problem for technologies like this and it seems they have some cool email providers on board to help with the adoption.
Regardless of the outcome, this is great for consumption of emails and for users who have trouble dealing with their high volume of email.
Comment · 13 years ago
That's true. All clients as far as I know strip out javascript for security.
What we do is actually inject scripts into emails to parse information in them.
We've built a bunch or scripts for social networks and retailers like ebay and amazon, but that doesn't really scale. Writing these custom script is time consuming.
So we thought, hey wouldn't it be great if the publishers of the emails annotated their messages with open graph tags (just as they already do with their websites) and that's how the idea. And we just parse those our using some simple javascript (https://github.com/birdseyemail/open-graph-protocol)
It's a bit of a chicken vs. the egg problem. We're hoping other email providers will adopt Open Graph in email so that publishers will have a reason to annotate their content.
And in the end the main motivation is that it's a great thing for consumers to have actions associated with emails. Imagine how much time you would save if you could "add to wishlist" your Groupon email just as easy as archiving it.
Comment · 14 years ago
facebook was 1st I believe
Comment · 14 years ago
East Side Access is another amazing project in NYC. going to bring LIRR to Grand Central in 2019 ish.
i've been somewhat documenting its progress at http://eastsideaccess.tumblr.com
Comment · 14 years ago
BTW, we're using heroku and ironmq for all the backend heavy lifting. Perhaps twitter got spooked by the volume of API calls. A testament to seamless cloud scalability. And of course we soon hope to get the twitter issue addressed so we can be operational and help causes spread their word.
Comment · 14 years ago
agreed. I started http://snaplog.com around the same time.
Comment · 15 years ago
this API is it. no approval process as far as is known. the CB api treats devices no differently than web sites as far as Apple is concerned.
the reason that there are no apps yet is that only iPhone 4S has the heardware for CB and no CB chipsets out there yet in devices. chicken and egg problem which hopefully will be solved with the iPhone 4S adoption.
Comment · 15 years ago
oh man. can you retry? i think it's cause not all the assets loaded (ran out of free quota on GAE) fixing now.
and more people included in your sample, more chance of finding amazing A++ engineers that can help the industry, your dev platform, etc...