501 karma · joined February 2, 2011
- There are circumstances where talking as if you know what you're talking about when you really don't can do more harm than good, both to you and to your audience.
- The idea that we should stop learning before we get so deep into a subject that we can't immediately communicate our insights to a layperson (which is not very deep at all) smacks of anti-intellectualism.
And problem sets of course, because typing in physical constants and converting units is annoying.
Oh, and http://news.ycombinator.com/item?id=3521445 ("orbital velocity of ISS in mach").
Anytime I need a result that requires knowledge of some quantity, I usually try Wolfram|Alpha first.
But it is...
1) We test theories with experiments to see whether they fail for that particular "input", we don't prove them correct.
2) One of our two best theories (QFT, the other being GR) doesn't even make sense, mathematically.
In fact the great challenge of physics today is that we have neither experiment nor mathematical rigor to stand on: http://groups.google.com/group/sci.physics.research/browse_t...
A theory that gives correct results for a limited range of phenomena but isn't absolutely correct or mathematically consistent is still useful. Same for programs, I would think.
Did not know that.
http://floatinguniversity.com/files/Great%20Big%20Ideas%20-%...
This might be the stupidest sentence I've ever read on HN.
"They ALL appear to be utterly lazy ways of supposedly helping people whilst top slicing cash and creating tech jobs, management jobs and evade a chunk of tax."
Speaking of utterly lazy, why don't you tell us what you think after watching this clip of the 19 year old girl you just insulted: http://vimeo.com/26638815
1. good programming is probably beyond the intellectual abilities of today's "average programmer"
2. to do, hic et nunc, the job well with today's army of practitioners, many of whom have been lured into a profession beyond their intellectual abilities, is an insoluble problem
3. our only hope is that, by revealing the intellectual contents of programming, we will make the subject attracting the type of students it deserves, so that a next generation of better qualified programmers may gradually replace the current one.
The above implications are certainly unattractive: their social implications are severe, and the absence of a quick solution is disappointing to the impatient. Opposition to and rejection of the findings of programming methodology are therefore only too understandable. We should remember that the conclusion about the intrinsically mathematical nature of the programming task has been made on technical grounds, and that its rejection is always for political or emotional reasons."
EWD611 (http://www.cs.utexas.edu/users/EWD/transcriptions/EWD06xx/EW...)
As someone who appreciates autonomy, I would rather be given an objective with advice on how to attain it than rules to follow. Even if the content is the same, it shows more respect.
In this case, the objective is simply situation awareness (http://en.wikipedia.org/wiki/Situation_awareness) for both parties. The advice is to ask, debrief, and warn.
Dan Pink gave a good 10-minute talk about this sort of thing: http://www.youtube.com/watch?v=u6XAPnuFjJc
image :: (R, R) -> Rhttp://www.youtube.com/watch?v=Fo8v7juSgRw#t=54m55s
"The machine is a beautiful, wonderful piece of hardware. The orbiter system, the most complex system ever built by man to fly has never [...] had a failure that would have prevented that machine from landing safely."
I'm not sure why this is though.
Can anyone elaborate?