ArbitraryLimits

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.

I don't think so - the whole point is that other don't want the same behavior from you as you would want from you, in their shoes.

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 Ruby, unit tests stand in place of static compiler checks. I haven't heard a strong argument against them nor a replacement for them.

How about static compiler checks? :)

> 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.

I'm a little embarrassed that I never got the word play in "tarsnap" until just now...

Yes, but you have to admit it does need a call-to-action link that's actually a button.

That's a lot of buzzwords in one sentence. Reminds me of the early 90s when everything had to use neuro fuzzy wavelets.

I'm confused, are you saying there's a link between people's beliefs and actions or not?

No one's going to rag on the post's author for labeling himself "Christian" right at the top? He might have donated to Prop. 8 after all.

Edit: That's sarcasm, people.

> 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.

Except that EEs like to explicitly restrict the word "signal" to mean only the known inputs, and call the rest "noise."