I'm perfectly comfortable with concision, thank you.
Clearly one can interpret the Golden Rule two ways depending on whether you take into account the other person's different values or not.
For example, you're probably patting yourself on the back for being "concise" despite using more words to praise your original comment than it would have taken to clarify it, whereas I'm resenting you for the way you've ostentatiously foregone social niceties at my expense.
Is that really what you would have wanted in my place? Despite your ability to parse it, I don't think you understand the Golden Rule very well.
SF is (or used to be until recently) the West Coast's banking center, and everyone in that industry has to be ready when markets open on the East Coast at 5am Pacific.
> In the US system ... everyone else is promoted and then assigned
It's worth pointing out that one of the reasons this system works in the US army is that non-commissioned officers are trusted with a great deal more responsibility than their Soviet counterparts were. The mechanical promotion of junior officers would be impossible without 15 year veteran NCOs taking care of a lot of the grunt work that Soviet officers got stuck with, simply because the system wouldn't trust NCOs with it.
Wouldn't this only apply to neural networks as used for classification? I mean the general paradigm of deforming curves until they're separated by a hyperplane seems pretty obvious now that I see it in front of me, but what about neural networks used to approximate continuous functions?
This is basically what VxWorks (real-time OS) started doing in their 6.x series - the MMU is active and all memory addresses are virtual, but no two processes get access to the same virtual address range. That way you can debug with virtual addresses turned on and see page faults instead of whatever hilarity ensues from overwriting the operating system itself, then turn the MMU off and stop taking the execution speed hit of translating addresses. It turns out that almost everyone just leaves memory protection on all the time anyway, since duh, it's the only sane thing to do.
Fun fact, the most reliable indicator that you have this kind of setup is whether the Unix emulation layer (if present) offers fork() - if only one process can access a given address then you obviously can't create a copy of a process that uses pointers.
That's true but I think the bigger reason is that a single address space makes system calls as cheap as regular function calls, since there is no kernel boundary any more.
Ironically, VxWorks's latest major rev was all about turning memory protection on since overwhelmingly people prefer the performance hit of kernel calls over the heisenbugs that come from stomping on the kernel's code and data structures.
> Lagrange interpolations are only distantly related to Legendre/Hermite/etc polynomials
Actually ... take an nth degree polynomial from your favorite orthogonal set. For each of its n+1 zeros, construct by Lagrange interpolation the polynomial which is 1 at that zero and 0 at the others. Then that set of n+1 interpolating polynomials has the same relation to the orthogonal polynomials of degree 0 through n that (periodized) sincs have to sinusoids, i.e. you can decompose an n degree or lower polynomial in either basis, and the two representations are related by something like a Fourier transform.
"Signal" has always bugged me because it has the connotation of a function of time, whereas historically the Fourier series were first used to represent functions of space.
Everyone says that, until they're put in charge of babysitting an old HPUX or AIX box and it's time to install something. Then no one complains about Autoconf again (though they can't bring themselves to praise it, either).
> Years ago David Cheriton at Stanford taught me something that seemed very obvious at the time -- that if you have a network link with low bandwidth then it's an easy matter of putting several in parallel to make a combined link with higher bandwidth, but if you have a network link with bad latency then no amount of money can turn any number of them into a link with good latency.
You can tell it's dated from this little tidbit:
> The Cable TV industry is hyping "cable modems" right now
Unlike the iPad, the iPhone, Dropbox, and "The Web," credit for this metaphor may fairly be given to David Gelertner. Although he applied it to naming files rather than servers.
> If you have three pet dogs, give them names. If you have 10,000 head of cattle, don't bother. Nowadays the idea of giving a name to every file on your computer is ridiculous.
For what it's worth he was also the first to use the metaphor of a cloud, although in his sense the cloud represented your personal data and it drifted to follow you, casting a shadow over pavestones representing computers, as opposed to the usual sense of the cloud being an amorphous body of computers.
Clearly one can interpret the Golden Rule two ways depending on whether you take into account the other person's different values or not.
For example, you're probably patting yourself on the back for being "concise" despite using more words to praise your original comment than it would have taken to clarify it, whereas I'm resenting you for the way you've ostentatiously foregone social niceties at my expense.
Is that really what you would have wanted in my place? Despite your ability to parse it, I don't think you understand the Golden Rule very well.