anameaname

12 ms·

31.
by anameaname 9y ago
That isn't reading the graph correctly. The saw tooth pattern means that memory is being allocated, but not that it's slow. The CPU usage graph tells you if it's slow. Object pooling is generally considered to be the worse
32.
by anameaname 9y ago
Pike is totally wrong here, and trying to explain his way out of a poorly thought out error type. > In contrast, a stack trace-like error is worse in both respects. The user does not have the context to understand the stack trace, and an
33.
by anameaname 9y ago
At these kinds of speeds, why would we use it for just video? We could make server interconnects extremely fast.
34.
by anameaname 9y ago
> Because her blood and the blood of the baby mix, she carries cells from the baby for many years afterwards. This is not true. If the baby had AB blood and the mother had A, then the baby's blood cells would be attacked by the mot
35.
by anameaname 9y ago
Agreed. I think the reason is because the programming mindset for data science is different than for normal software engineering. In data science, you write a program, find the answer, write your paper, and throw the program away. Pyth
36.
by anameaname 9y ago
Some of these answers are not great, and wouldn't stand up to interview scrutiny. For example, the "Check if linked list is palindrome or not" problem says copying the list would be too expensive. The proposed answer (recu
37.
by anameaname 9y ago
A thought experiment that comes up in Kernel design classes is what should happen if the OS was running the flight-control software for an Airplane you are on? If there was a bug in the kernel, perhaps a double free or a memory leak, what
38.
by anameaname 9y ago
Not a statistician, but this still seems flawed. The pretend votes need to be related to the person seeing the list of items. These normally come from the population (i.e. if you were ranking Netflix, the pretend votes would be the sum o
39.
by anameaname 9y ago
Source for those interested: https://github.com/torvalds/linux/blob/master/lib/refcount.c I'm kind of surprised that the authors went with compare-and-exchange for their ref count, rather than