I am brilliant, and I could have done a way better job of building healthcare.gov for 0.2% of the cost. Unfortunately, I was too busy working on all my other awesome projects that have nothing to do with big government systems or the healthcare industry.
Also, that stock chart was ridiculous. At any given point on the x axis where the value was higher than the previous point, you could cut it off and say "look, we're at a peak!"
Are all Business Insider articles glorified Buzzfeed articles? Just change the title to "10 Signs That The Tech Sector Is In A Massive Bubble" and it could be on Buzzfeed.
Here's why this needs to pass: we need bold changes, and we won't know what works until we try it. So here's a bold plan, which seems to work on paper. I wish Pennsylvania would try something like this, or at least something better than the "slash public education funding" plan.
I think the definition of bold may be what is causing the disconnect. The two things I saw on the website that stood out were reduced class sizes and the reinstatement of cancelled programs. I can see how this benefits teachers, but am not sure how this improves reading, math and reasoning skills and increases the number of kids that are job/college ready.
> In a normal situation this would have been fixed simply by adding a wait primitive to the language which would schedule the events when the result is still being fetched... 80 percent of the programming is about doing one motherfucking thing with another motherfucking thing and you need both of them to complete the action.
I get the best results from just asking them to describe something they've worked on that they're particularly proud of, or was particularly difficult. And keep prodding for more details to get a real feel for how the person works. Basically, pretend you have just taken over a project and are trying to get more information on it from one of the developers on your team. You'll find out a lot about the person in a conversation like this, far more than from purely theoretical or "the answer is B" questions.
This. A thousand times this. Each candidate is different. You should be asking questions to figure out what they know. Requiring specific experience is often a bad idea, because, for example, I can train you how to use our custom codebase, but I don't have time to train you on basic coding skills. You should be able to fully describe a project you built, from start to finish, discussing problems and obstacles and their solutions.
I also think it's perfectly okay to say "I don't know off the top of my head, but I can find out" when asked a question. Or alternately, "I don't know off the top of my head, but based on what I know about other things, I would start here..."
I like this a lot. You can ask a lot of follow-ups that tie more into the skill set while staying inline with something they're passionate about. Good stuff.
