hurtmyknee

This is terrific, thank you for sharing!

Great post, could you expand your thoughts on Nim? With Cython/PyPy I can get things done when resources are more restricted.

Never seen Nim in prod, but it has caught my eye and I'm curious.

There are seven questions in this article, and topics like machine learning and program verification are in quotes.

I don't think a competent engineer was consulted on this article.

Perhaps as a community we should elucidate in a more formal fashion to the press.

To be blunt, this article makes me sick. An admission essay is one of many ingredients to the meal that makes a great candidate.

If all the other metrics are aligned, why does one need to hire a professional writer?

This is great advice that took me quite a bit of time to learn as well.

Most of our meetings are held in a room with a whiteboard, and it has become standard to start by writing "GOAL: {{goal}}".

It prevents tangents, encourages us to use the scratching space so we can diagram the high-level components involved, and helps educate the folk who aren't up to speed (technical or business).

> The T42’s touchpad is hardly usable for productivity. Disappointingly, so is the iconic red nub.

I agree the touchpad leaves much to be desired, but I've found the nub to be fantastic. With one index finger on the nub, and two thumbs on the mouse buttons, my hands never leave the keyboard.

I understand your concern, but I agree with the advice whether just out of college or not. Interviewing is a skill just like any other, and if it has been more than a year since the last one, chances are you'll be rusty.

If a candidate is in the interview, there must be a modicum of interest, and is a great chance for the employer to sell it's position. And of course, as an interviewee, it is mutually beneficial to avoid wasting both parties time by expressing disinterest as soon as possible.

While true for the aggregate, there are always exceptions. I know someone who had a GPA <= 2.3 from a mediocre state school that went to medical school in the Caribbean.

The person did so well on Step 2 that s/he was invited to transfer back to the US at a fist tier medical school, and is now the director of cardiology at a prestigious hospital.

I recently had a phone interview with the CTO of a startup. I checked out his blog beforehand and read an article describing his approach to debugging. I brought it up and it led to a great conversation, which I believe got me to the second round.

"You can tell when someone 'gets' it and when someone doesn't."

Can someone explain this in more detail please?