The prices are ridiculous. Look up Hennessy Hammocks for something more reasonable and be prepared to insulate a lot from the bottom, especially in moist climates.
Exactly. I've already had to give my fingerprint numerous times at the airport just to enter the United States. I figure the US government must already have it in numerous databases, so it's not a concern if they've backdoored Apple's devices to copy them again.
It's not always obvious if a semantic change that's documented in the release notes will break your code. You might not know you use the code, the particular behaviour might not be covered by your test suite, etc. I like the fact I can upgrade to the latest Go version without having to worry things like that will happen.
In Burnaby, BC we have some pedestrian signals that will audibly count down how long is left to cross the road as well as providing a visual counter on the signal itself.
Even if I know more or less what I am looking for, I'd still rather do it on my own time than have a sales associate "help" me. I always feel like I am pressured in to making a decision faster than I would otherwise. If they are helping me and I do try to take my time to make the decision I always get the impression of mounting frustration at my indecisiveness. That's why I prefer sales associates who say "let me know if you need any help" and then just leave me alone.
A lot of ceiling fans can easily be installed on to an existing light fixture by anyone who knows how to connect a few electrical wires together. I'd say the bigger downside is that it's fixed in one location.
Isn't that the standard way to decide what to optimize? There's often not much gain to be had if you are optimizing things that are not the bottleneck.
Another limitation of quickcheck that's often overlooked is that simply using quickcheck for testing your function does not guarantee complete coverage of your function. The coverage may also differ between runs. So while it's good for doing a "quick check" of your function it's not a replacement for unit testing.
Happens to me from time to time. Usually I get up and do stuff. One of two things happens: I find I don't get tired and so I just get a really early start to my day, or else I get really sleepy again an hour or so later and just go back to bed.
Exactly. I didn't even know there were names attached to TDW stories at all. Is it a recent thing? I haven't been a regular for many years but read the occasional story here and there.
NumbaPro generates CUDA code that runs on the GPU. I don't see how using C++ to do it would necessarily make it faster as the code executing on the CPU end of things is not the bottleneck.
The author states earlier in the article that we don't really understand sleep and that there is no one solution for everyone. He then proceeds to make a list of "top three" concrete and (IMO) questionable suggestions that he thinks we should follow. Not a great article.
The elements of the doubly-linked list are slices. A slice can be thought of as a reference to a backing array. The only things being created or collected by the GC in this case are the Element bookkeeping structures (and possibly some slice headers) which contains the the slice.
The memory that is being recycled in the example is storage region of the slice, the size of which is arbitrary. It seems that by default they preallocate a 100-element byte array.
Actually this outage report is a good example of compounding systematic errors. A among the things that went wrong: incorrect and impossible packet sizes were detected, the rule generator generated rules matching the impossible packet sizes, the human operator who looked at the rules and entered them in to the router didn't notice any problems, and finally the routers responded to the incorrect rules by starting to crash.
Had any of these steps not gone wrong there likely would not have been an outage. It was a combination of failures that caused it.
The trick is having enough skill to be able to evaluate the professional you're going to hire. I've been bitten by this before both in my personal and professional life. If you don't know enough about the field even someone with only a marginal amount of knowledge about the topic can seem like an expert.
I find most of the time I'm using sudo I don't want to type it before every command and so I use sudo -i which pretty much negates the benefit of logging anything other than to tell that I was sudo at some point.