hurtmyknee

This is terrific, thank you for sharing!

Additionally, it's the hypocrisy of a global icon. There is a cinematic in the video game NBA2k that truly puts it into light [1]. James' production company helped write and produce it, they're his words.

It hurts, and is terribly disappointing.

[1] https://streamable.com/jxkz0

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.

I like to keep things modular, if you're looking for API development Falcon is a lightweight DIY solution (https://falconframework.org/).

Flask-RESTful worked out for me, I like how easy it is to define routes. I'm eager to try Falcon next: http://falconframework.org/

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?

Building a CPU in a circuit simulation framework[1] was one of my favorite, and most illuminating, projects I've done.

A great book to learn more: http://www.amazon.com/Computer-Systems-Programmers-Perspecti...

[1] http://tams-www.informatik.uni-hamburg.de/applets/hades/webd...

It's not as boolean as good/evil, but certainly there are ethical challenges to be faced in this particular field. There are many roles to play, so this comment isn't necessarily directed at the parent comment or risk management.

We all know the incredible power of technology. Applying engineering practices and automation to financial markets can be a dangerous game, where the full scope of risk is not yet clear and the repercussions can be disastrous [1][2].

With very few peer-reviewed academic entries and in the wake of the financial crisis of 2008, I would be very uncomfortable applying my skills in this domain. I feel that engineering, if it is to be applied to financial markets, should be centered around bolstering security and reducing risk, not profiteering.

The recession was triggered by a clever system of alleviating risk [3]. When this architecture blew up, financial executives testified before congress citing the "highly complex" nature of the industry as an excuse. I personally do not want to work for this class of people, let alone implement or analyze their trading strategies.

Software is supremely flexible, it can be applied in nearly any industry. We have the ability to wield and program the electromagnetic force of the universe. We can push bits around to genuinely create a better world. That, to me, holds so much more value than a digit in my bank account.

I apologize for the off topic discussion, just wanted to get this out.

[1] http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1695041

[2] http://en.wikipedia.org/wiki/2010_Flash_Crash

[3] http://mitworld.mit.edu/video/861

Edit: formatting.