News for hackers. Stuff that matters.
Re:Dynamic Programming for Technical Interviews by jonsen on Friday March 15, 2019 @03:56AM (#19397557)
Formatted for mobile:

According to Richard Bellman, who came up with the name:

An interesting question is, Where did the name, dynamic programming, come from?

The 1950s were not good years for mathematical research. We had a very interesting gentleman in Washington named Wilson. He was Secretary of Defense, and he actually had a pathological fear and hatred of the word research. [...] What title, what name, could I choose?

In the first place I was interested in planning, in decision making, in thinking. But planning, is not a good word for various reasons. I decided therefore to use the word "programming"

[...] it's impossible to use the word "dynamic" in a pejorative sense. Try thinking of some combination that will possibly give it a pejorative meaning. It's impossible.

Thus, I thought dynamic programming was a good name. It was something not even a Congressman could object to.

Re:Dynamic Programming for Technical Interviews by matt-snider on Friday March 15, 2019 @05:13AM (#19397953)
Thanks :-). This comes up so often! Is there a reason HN doesn't use a more mobile-friendly format for preformatted text?
Re:Dynamic Programming for Technical Interviews by stan_rogers on Friday March 15, 2019 @05:51AM (#19398139)
The feature is intended for code, note block quotes. Auto line wraps would be less than helpful.
Re:Dynamic Programming for Technical Interviews by jonsen on Friday March 15, 2019 @06:10AM (#19398238)
Problem is when some text copied and pasted here incidentally starts paragraphs with two or more spaces. And maybe the the commenter does not know why it formats weirdly.
Re:Dynamic Programming for Technical Interviews by frosted-flakes on Saturday March 16, 2019 @01:00PM (#19408792)
Yeah, but code blocks are still limited in width on mobile. At least let them flow to the edge of the screen before scrolling.
Re:Dynamic Programming for Technical Interviews by mafm on Saturday March 16, 2019 @12:30AM (#19406358)
Thanks. (I have now looked up the correct way to quote).