Bulk70

Looks great, can you explain how it differs from say PLEX?

Twitter staff != Twitter Inc

The clickbait is real with this one. Nothing shocking or "secret" here that a 30 second skim of the documentation wouldn't reveal.

As a hiring manager that gives take home tests rather than testing on site, I feel on balance it gives a better idea of what they're capable of than a barrage of on site tests & technical questions. Given the option of spending half a day on site and half a day at home coding, are you saying you'd prefer that over a full day including half a day of whiteboard and programming with people watching what you do?

There isn't a correct answer I guess, nothing will suite everyone.

Edit: changed to a less snarky response.

It's been in a prominent position on the front page of BBC news all morning - not sure how much more exposure you can give it really?

The biggest surprise for me is that they weren't already doing this. Or perhaps they were and this is just adding a way to opt out?

From the guidelines:

"On-Topic: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity."

I'm a hacker. I found this interesting (and sad).

Often the problem being solved by this sort of thing isn't directly about making it easier to work with a language, but making it easier to hire developers. The hiring pool for developers who are very good with PHP is much much larger than a lot of other languages simply by virtue of it being an easy language to get started with.

This is also why Facebook has spent so much time and effort on things like HHVM and Hack.

Why do you want be a UX engineer and GitHub specifically?

Perhaps apply for UX positions at other companies - ones that are actually hiring in that position, and build up some working experience in the field.

I'm a hacker, and I found this interesting. What now?

> How many Jobs/Apple movies do we need?

One good one will do.

I'm very comfortable with the command line in general already, and if I have to I can use git on the command line. I've just always felt a GUI is the best interface for git - personal preference I suppose.

I'm a very visual person when it comes to code, and being able to see a nice history/diff etc inline with a few clicks just sits better with how I view the world & my ideal workflow.

I appreciate I'm probably in the minority on that though, as evidenced by the lack of client from those two big players I assume they feel that way too!