wikyd

This is not a well-known fact. What makes it the "right" time besides your opinion?

I'm not sure about Nokia's service specifically, but in general these kinds of services do more than just zipping files. Some things they do: * resize images large images to match the screen resolution * limit the number of HTTP requests the phone itself is making

Looking at the response headers, the powered-by header says "Food" (x-powered-by: Food). Is this a new web framework or just a little joke?

Are they ignoring the "long-term externalities" or is it just impossible to actually know what they are? Or maybe they just disagree and are putting their money where their mouth is. To even expect a non-programmer to consider this issue strikes me as pretty crazy.

I bought an iPad and I don't think that it's going to affect distribution of software in any meaningful way, besides making it easier for developers to reach users through the app store. For one, anyone can deploy an app to Heroku for free. You can host plain html, css, and js for free. You can learn how to program an iOS device for free with tons of great guides and materials online. When you want to distribute it, there is a hurdle to clear, but (and this might be a cultural thing), $100 as a 12-15 year old is not such a wild sum. It also makes my experience browsing the app store better.

I'm really excited by this idea. I know many first-year and second-year teachers who spend so much time lesson planning. It seems like a lot of duplicate work repeatedly done by teachers that can be saved or cut down with shared lesson plans.

I've seen other sites in the past attempt to solve this problem, but using the SourceForge model. Just hosting lesson plans and providing search and ratings isn't enough, though. I think the GitHub model is so much more successful because of the feedback provided by forks, watchers, and recent activity. This implicit measurement of activity is much more interesting than a star-rating when judging a project's quality.

How does Baydin's Boomerang handle these complexities?

Use the up and down keys to page through the results. When a result is highlighted, you can press the right key to show the preview.

San Francisco, CA -- InternMatch

InternMatch is looking to hire a software developer as employee #1. We are looking for an entrepreneurial developer whose next job description will likely read "Founder." More details at: http://www.internmatch.com/about/jobs

Contact us at jobs@internmatch.com

Sorry, I thought you were just asking is it possible to see the context. I wasn't looking to defend the product. That said, though...

I don't think Circles intends to aid in setting social context for other people. It's intended to help the sharer set context for who will see their content. Google is betting that people will share more information if they can limit it to the right groups of people.

As a commenter on this content, I don't get to reset the context or modify it. I can either trust the initial poster's choice or I can dig in further. The mental model is pretty simple: I trust the poster or I take a look around the room and see who else is there. I think when people do dig in further, they will either see a small group of people that they recognize or a large group of people which will set them in "public" context mode for commenting.

Interesting, I was definitely able to use a different account for my invite link. My original email was also tied to a Google Apps account with a custom domain. I can't seem to find the option to enable profiles in Google Apps, so I ended up registering with an old gmail account.

G+ posts have a link in the top right corner that says: "Limited" or "Public." If you click on limited, you can see everyone who can see that post.

Their standing is that they sell you a ticket on the condition that you will not record the performance (or that you're not allowed to have a recording device on your person).

Curated does not just mean "people look after it." It also means that people make editorial choices about what belongs and what doesn't.

I bet that expectation applies to writers, designers, and other creative jobs. I'm not sure what you consider the line is for "professional career."

The test probably does weed out good engineers, but I would rather have a test for employees that yields more false negatives than false positives. I know plenty of people with families that also code in their spare time as a hobby.

Somehow, I doubt the collection of fewer taxes will stop things like war. Instead, it's really you, me, and other taxpayers who aren't getting our cut.

Well, I disagree that you have to sift through it. Normally, I am a "completionist" and don't want to miss anything, but I've come to accept that most content on social networks is transient and I couldn't read it all even if I tried. Even Facebook's "full" feed doesn't include everything.

I think, though, that audience targeting is the weak point of Facebook and Twitter right now. I think many times people post something with a few people in mind or at least a subset of their social graph. For example, when I post technical articles that probably are interesting and relevant to my technical peers, my HS friends and family will see them also. I don't think you can blame users for doing this or chalk it up to vanity. Their posts are probably relevant and interesting, but just for a subset of their graph.

A Googler made an interesting presentation describing this problem: http://www.slideshare.net/padday/the-real-life-social-networ...

I know that Google solicits feedback from their employees who may have worked with you in the past. Is it possible that you pissed off a former co-worker who now works at Google?

You write like everyone who posts to Facebook or Twitter expects you to read everything they post. I don't think anyone posts with that expectation in mind.

When they claim they are the only native browser, then the feature set that defines native better be exclusive to them.

It's not negativity to call bullshit on a claim. There are plenty of things Microsoft could be touting about their browser without making up marketing speak.

I've seen the same for starting salaries in Seattle, over the last four years (graduated in Dec. 06). This is for big companies like Microsoft and Amazon and for some startups depending upon their stage. Anyone 26 and under would see the same.

EDIT: typo

1 isn't exclusive to them, so doesn't add to their point of being "native." 2 comes with a ton of caveats, if I'm not mistaken. Other browsers also take advantage of graphics cards for certain kinds of rendering.

I have no evidence for this, but I think that IE is trying to ride on the positive association people have for "native apps" on mobile phones.

The people that I know that work on IE seem to take my ribbing of them in stride. When I complained about having to fix IE7 bugs, they suggested that I throw up a "get with the times" banner. Also, I think the whole IE6 team was disbanded and the new IE team looks much different, if it even includes any of the original members.

Holy lord is that a lot of risk to accumulate doing a full rewrite and deploying it all at once. I think the hardest part about rewriting an app is knowing about all the edge cases, kludges, etc. that accumulate over the years. It makes sense that the person who knows the most about the product and its dirty secrets would be much more capable of rewriting the app quickly than a newly hired employee.

As a counterpoint, last year I joined a startup as the first technical member. I migrated a PHP application written by an inept contractor (terrible DB layout, SQL queries in the views, most features buggy and incomplete, etc.) to Rails piece-meal. I had very little experience with Rails or PHP prior to this, but was able to rewrite the app in the course of a few months, while adding new features and continuing product development. I simply placed nginx in front of both the PHP and Rails app servers and rewrote the auth system for both apps so that cookies/credentials could be shared. Then it was a matter of migrating sections of the app over one-by-one. There was some hairiness in how the Rails side linked to non-Rails pages, but that code was gradually replaced as the rewrite progressed.

Even despite the abominable DB schema from the original PHP app (which, in fairness, had nothing to do with PHP), Rails was flexible enough to allow me to override its conventions and map tables to models with joins, etc. Overall, it was much simpler than I thought it would be and after the rewrite was complete, it was pretty simple to write migrations to start organizing the DB schema into something coherent.

The timeframe for these internships is rolling. I'm sure most of the startups would accept an intern tomorrow, but will wait for the summer as well.

I agree that communication skills are a great skill to have as a programmer. I'd probably even rank it higher than raw programming ability, personally. (BTW, not all of these startups are only looking to hire developers--a student looking for a marketing internship would probably do very well posting a video.)

I don't think, though, that a cover letter is a great test of these skills. Cover letter templates are abundant and it's very easy for someone to basically copy and paste one in their application. Our team has read every cover letter sent through our site and we noticed some interesting patterns with them. Initially, most students didn't really know what to put in a cover letter and they basically looked like form letters. We created a few resources to educate students on what to write and placed links to them in the application flow. This helped immensely (a lot more than I expected, honestly) and the quality improved.

Still, though, as an employer looking at the resumés and cover letters of students, it's sometimes difficult to distinguish between candidates before doing a phone screen. They have limited experience and skills to highlight. We're trying the blog post / think-of-something-creative application process basically as an experiment to see what students come up with. It's possible that by removing the constraints that students normally perceive on cover letters that something interesting will shake out. You may think it a waste of your time, but you also aren't on the list of companies looking at these candidates :-) Companies participating can opt-in with this expectation in mind.

I actually thought the same thing about the internship cycle last year. At the school I went to, almost every engineer I knew had accepted an internship by December and many had by October. I was actually really surprised to see that many great students from schools that don't have a heavy GOOG/MSFT/AMZN, etc. recruiting presence were looking for internships up through the end of April. Also, we saw a lot of sophomores applying around this time as well.

Startups tend to be less picky about year of graduation and more interested in the capabilities of the student. The best intern I've had was a sophomore who within a month was contributing like a regular member of the team. We had him stay on part-time through the next school year.

I'm pretty confident we'll find good students again this year even in April. If this experiment goes well, we'll probably try another push in the fall to help startups edge in on big company recruiting territory.

We're really excited about helping startups find interns and helping students think outside of the box when applying for a job.

Shoot me an email if you'd like to be included in this: kyle@internmatch.com

Is anybody else actually able to use the app? I got past the "take a picture of yourself", but now I just see blank white screens everywhere.

Interesting. I've worked with a lot of 3rd-party APIs and I liked Netflix's the best by far. They stuck to the REST concept the best of the ones I've seen and it made it very easy to start using it and to write a simple wrapper around it. I actually still use it as a reference when I'm building APIs. I hope they don't lose that.

One thing to consider about unpaid internships is that they can limit the potential candidate pool. Not everyone can afford to work without being paid.