skysight-inc/HackerNews huggingface dataset:
And humans. These things aren't really ultrasonic because phones and computers can't transmit ultrasound (why would they need to?).
That's an interesting question because it's the first time I hear about radium in artificial fertilizers. Will need to dig into these Wikipedia sources.

That tobacco contains lead and polonium had been known for decades, but I used to think that it originated from the decay of natural atmospheric radon and these plants just had some unusual tendency to accumulate heavy metals.

Maybe I should put my tinfoil hat on and run away from non-organic food too?

edit:

From the first source:

Tobacco farmers in developed countries primarily use manufactured fertilizer high in phosphates produced from apatite rock that contains radium-226 and descendant radioisotopes such as lead-210 and PO-210. Tobacco is a unique agricultural crop in that its flavor depends on nitrogen reduction, which occurs through the repeated application of high-phosphate fertilizers. The higher the phosphate level of the fertilizer, the higher the concentration of PO-210 in the tobacco plant. Tobacco grown in certain developing countries has approximately one third less radioactivity than tobacco grown in developed countries, and the radioactivity of tobacco grown in the United States has increased over time.

So maybe you are right.
Call me cheap, but $1 a month seems a little steep for this for me. I'm not planning on dying for another 50 years or so. Even if your site is still around at that point (which, let's be honest, isn't likely), I'll have paid $600 for you to send off a couple email for me.

It's a cute idea, and maybe something I'd consider for a small, one-time fee, but I definitely would never pay monthly for it.
Can't you send an email on a timer? Say a day or two after your birthday or some holiday. Every year on your birthday you reset the timer. It could take some time after you disappear for the info to arrive.
Last time I checked, offline message (storage) was not implemented. Is there progress on this?
It ends up in an infinite loop for me :(
Well, you did say "Solaris zones UX is still unsurpassed"

Still implies that it was always good..

It was absolutely terrible in Solaris 10. Maybe it's better now. Maybe with solaris 11 they fixed it so you didn't have to chose between a full zone that took 5GB or a 400MB sparse zone that would break in fun ways when you tried to do anything.

At the time I was using xen+debian and a 'full' vm for me was about 200MB. Basically base system+sshd+whatever daemon I needed to run. Attempting to do the same thing using zones was a complete disaster.
Also an old email with long-expired passwords etc.
The safest way possible to smoke tobacco is to grow it yourself.

The small yields will limit you to smoking only a few time a month.

You will want to taste that homegrown tobacco so you will most likely invest in a good old wooden pipe. This will make it so that you don't inhale the smoke into your lungs.

You will however still be at risk of mouth and throat cancer.
Of course, we know iOS has way less data mining, since Apple is more transparent in this regard and we can all read iOS source code... Oh, wait...
Although this is true, I've been bitten by issues where the browser 'supports' the feature, but it's still broken in comparison to other browsers, resulting in having to disable the feature for that given browser via browser detection. The most recent issue was `clip-path` in FF; it behaves _very_ weirdly compared to other browsers (Chrome, Safari).
just out of curiosity: where would I be able to get one? they seem to be perpetually out of stock (at the $5 price point).
'large amounts' is probably an effort to cool the rest of the pack and prevent the fire spreading. Not a way to actually put out the cells already on fire?
Not necessarily; the University of Lincoln which has one of the newest engineering schools (in partnership with Siemens) offers undergraduate bachelor of engineering degrees - http://lincoln.ac.uk/home/engineering/undergraduate/
True about the kernel, but I've recompiled many of my tools(for example linux repos sometimes provide outdated versions of packages and I need something newer). I often dig in source if I find bugs, or under-documented areas, sometimes I just want to know what is really happening. True, that doesn't make people who don't do that any less "pro", but it does make me sharper as a practitioner. I earn a deeper knowledge about my tools and my environment and occasionally pick up good ideas, or learn some horrible truth about a beloved tool. Programming is fairly unique in the sense that our tools and our products are made of essentially the same stuff. At the very least I consider this a form of exercise worth practicing on a regular basis. It's not strictly work, and not strictly a hobby.
You are in the least safe position possible. You're on a free Google service. In spite of the longevity of a few of these services, those are shut down all the time.

You say:

> To make sure you are well and sound, Cronu will charge your card a dollar a month.

I would insert "and to ensure your message remains available", as written this feels so inauthentic as to be mildly offensive.

And then take that dollar a month from myself and from a few others, and spin up some paid instances. Pick a couple hosts that are likely to be around for a long, long time, and get a box from each, and make your service redundant. Show that you've paid for service from these providers and have paid up for the next 10? 50? 100 years. Register cronu.com for the next 10? 50? 100 years (this expiry date is easily verified with whois) because you obviously can't send email from cronu.com if your domain registration expired. Right now, your expiry is in September of next year.

Paying for these instances is what distinguishes you from a free monthly dead-man-switch email and makes you worthy of receiving that dollar.
I don't disagree with your or joepie91_'s points in that many (maybe most) open source project maintainers are perhaps more guarded and difficult in accepting contributions than they should be.

That said, even if you submit a pull request or an issue ticket and the maintainer doesn't follow up, or is making the issue unnecessarily complicated to resolve formally and merge into the main branch, at least the record of your findings is there attached to the repo as a rejected pull request or a closed issue ticket, and that can help someone who comes along after the fact who maybe experienced the same issue you did and can benefit from your comments. Maybe that same person who comes along later will have the time to fight for having the changes merged, and can use your comments as further evidence that the issue is worth reconsidering.

I stand by the idea that finding the issue, but posting it on an unrelated forum (like HN) instead of attaching it to the project itself serves no purpose than to tell others who are probably not even users of the open source code "look at this problem I found/solved, aren't I great?"
You are not cheap (cause I think the same) so there is the email option. If you value your one click a month less than $1 then that should work? Thanks!
Don't know why you were downvoted, you're absolutely correct. At first glance your n and my n are different, with mine (n1) being the input to the function and yours representing the number of digits in a multiplicand (n2). n1 and n2 are linearly related, though, since the exponentiation process increases the number of digits in a linear fashion.

It's also worth noting that since the Fibonacci sequence grows exponentially, the number of digits is the result will be linear in n. Therefore, the memory requirement is actually O(n), and writing the result to the screen will be O(n).
> it can cause cancer. Breast cancer. Cervical cancer. Liver cancer.

Do you have some idea of the likelihood here? Are we talking a 10% chance of cancer or a 0.001% chance?

The whole "it can have X side effect" is the same argument anti-vaccine people use without respect to any sort of cost benefit risk analysis.
I would look into Ancel Keys and the diet heart hypothesis.

This idea isn't, and never was grounded in evidence. It's based on very poor science done in the 20th century. The old guard of doctors and health officials will be looked at in the same way we look at geocentrists now. They hold a lot of the blame for the current obesity crisis we have.
> What is he talking about? Microsoft was in the handset and tablet business since the 90s.

I think he means to directly make the handset as the earlier offerings were on the PC model (Microsoft does OS, Manufacturer does phone).

> That's also part of the problem. Ballmer was obsessed with Apple and while he focused on Apple, Android took over the market.

In a lot of ways, I think the crux is they wanted the same profit Apple was getting and forgot that's not how they won the PC industry. Android succeeds in numbers because it is now the default free phone or the phone offered for non-contract folks. Android basically because the dumb phone replacement. Microsoft probably would have better off going for that market and making their money off apps and services. Other than Samsung and Google, the phones I see are the cheapies. I know LG makes a good phone, but the Android LG phones Walmart has are not them.

I still think RIM (and Verizon if the book Losing the Signal is to be believed) made a huge error in the Storm and should have hit the low-end phone market with the messaging (ok, they did need the big software improvement but the Passport looked good from a keyboard UI point of view). Apple really didn't execute its iPod strategy in the phone market and left a lot of room at the bottom.
>Most professionals get more than two weeks. Two weeks of paid vacation is really minimum entry-level stuff. I walked into 3 weeks and negotiated 4 weeks for next year in my review, and I've known people who (much further in their careers) have 5 or 6.

Americans tend not to use all of their vacation time; professionals often end up working remotely while on vacation. There's a fear of losing your job or being overlooked for promotion. This is a largely alien concept in Europe, where job security is much stronger.

http://www.marketwatch.com/story/55-of-american-workers-dont...
I work for a large enterprise 100K+ employees using Docker in production [1]

It's certainly had its challenges (different versions of Docker clients causing havoc with different manifest versions, race conditions in the engine etc etc), but this article takes things a little far.

If you take pretty much any new technology like this make it a base part of your platform, you'll want support from a big vendor. To think otherwise would be naive.

There is definitely a debate to be had about Docker Inc's approach to production/enterprise rollouts though, but as a technology I'd say it's developing pretty much as I'd expect.

I've also seen Docker succeed in production despite the technical challenges. If you don't like the heat...

(1) See my blog: https://medium.com/@zwischenzugs, especially: https://medium.com/zwischenzugs/a-checklist-for-docker-in-th... and https://medium.com/@zwischenzugs/docker-in-the-enterprise-ec...
There's a risk from radioactive elements in the tobacco, from the air which in turn is from the fertilizer used. Maybe growing it yourself doesn't change this risk?
Thanks for reading the article. And no I didn't actually block my Mom.
I wonder if this impacts any features that exist today.

It looks like @supports has been supported by everything but IE, and also the Android browser (not Chrome for Android) for a while [1].

[1]: https://developer.mozilla.org/en-US/docs/Web/CSS/@supports#B...
John Podesta was warned in 2008 to start encrypting sensitive emails
Hmm, if anything that link seems to imply it's invalid - plus it's Quora, not exactly a high quality reference.

The rule is "an" is used in front of a word that starts with a vowel sound[1]. "An hour" is correct because the "h" is silent. All modern (native) English dialects pronounce the "h" in history, ergo "an history" is incorrect grammar.

[1] https://en.wikipedia.org/wiki/English_articles#Distinction_b...
Well, here's the thing - I've been on a lot of interviews, and the majority of them wouldn't be satisfied with the answers you'd be satisfied with. If interviewers were the way you've described, I don't think the whole thing would be such an issue.

Overall, yeah, interviewers want to see that hash map largely written, often at a white board. Minor errors and bits of pseudocode are ok, but it should pretty much work.

YMMV, of course, but it isn't just me.

http://steve-yegge.blogspot.com/2008/03/get-that-job-at-goog...

"Hashtables: hashtables are arguably the single most important data structure known to mankind. You absolutely have to know how they work. Again, it's like one chapter in one data structures book, so just go read about them. You should be able to implement one using only arrays in your favorite language, in about the space of one interview."

Of course, Steve Yegge isn't the final word on prepping for google interviews, and I only had one experience there myself, but yeah, I'd say he's pretty spot on here (in fact, the google recruiter who arranged my interviews forwarded me the Yegge blog post, though I'd already read it earlier).
Well, i also use vim/zsh/intellij as well as all the apps i listed above. Intellij on its own isn't good enough if i can't manage my tasks/calendar/research/notes... Hence I am curious how you do that?
AI Education for Agencies with Siraj Raval aka Sirajology
It prevents the server form matching the url when it has stuff like the session id and username in it, and also helps in not giving those information to the outside.
The only significant modern-ish browsers that don't have @supports are all versions of IE (not including Edge) and Safari 8. In Safari's case, any version of Mac OS that ran Safari 8 would have gotten a Safari 9 update. So IE 10 and 11 do present some challenges in that case, but it will be up to the developer to decide if the amount of traffic from those browsers is worth worrying about.
Specifications You Should Read: The NASA Workmanship Standards
Wait, do you think he's not using data volumes?

I was assuming he was complaining about them even with data volumes.
An accessible iOS Download Folder
Sprint now supports RCS with default Messenger app
Part II of Skiena's wonderful "The Algorithm Design Manual" is basically a 300 page, high-level overview of a wide range of advanced data structures/algorithms, practical insight into when to use them, and advice on which implementations to use.

Even if you already have and are happy with CLRS, Skiena's book is a great addition to your library.
Were you using a vendor prefix by chance?
Really cool stuff, one thing though seems a little odd:

> Even at 2%, you don't notice the difference at this zoom level. 2%!

I'm not supposed to see that major streakiness? The 2% difference is extremely visible, even 11% leaves a noticably bad pattern on the keys (though I'd probably be okay with it in a moving video), only the 30% difference looks acceptable in a still image.
All valid. Then again envelops tend to get lost, misplaced or simply forgotten ...
Err.. did you mean "full-stack(overflow) developer"?
Most of those people don't host their own websites, either.
The first line of Wikipedia's entry states "The Armitage–Doll model is a statistical model of carcinogenesis, proposed in 1954 by Peter Armitage and Richard Doll, which suggested that a sequence of multiple distinct genetic events preceded the onset of cancer."

It's clearly a mathematical/statistical model of a phenomenon and not an explanation of the underlying processes.
@supports will change your life, eventually.
Do you mean 'people's'? That would make 'the people's house' as a way to describe US executive mansions and legislature buildings communist references as well.
Regarding this - "Model here means business rules, like rules for approving loans or adjusting power consumption in data centers. In traditional software, programmers created these rules by hand. Today machine intelligence can use data and new algorithms to generate a model too complex for any human programmer to write."

Isn't it a bit problematic that the business rules generated by the model are too complex for humans to reason about them? How can you rely on the rules to be 100% appropriate for the task if it's impossible to reason about them?
Box has lots and lots of founder and unnecessary executive people

Small pieces of a small pie
Mapping India and the Great Trigonometrical Survey
Sometimes it's just easier to learn the math. (I am not kidding.)
For anyone interested in Fibonacci numbers: Fibonacci Quarterly has been published for more than fifty years.

http://www.fq.math.ca/
Your example seems to assume translation only. I wonder how difficult/useful it would be to identify other kinds of time-varying characteristics (translation, rotation, scale, hue, saturation, brightness, etc) of partial scene elements in an automated way.

Along the same lines, it would be interesting to figure out an automated time-varying-feature detection algorithm to determine which kinds of transforms are the right ones to encode.

Do video encoders already do something like this? It seems like a pretty difficult problem since there are so many permutations of applicable transformations.
Yeah, no system is perfect. If your will cannot be found, that is a problem. Of course, digital documents won't be notarized, so that is also a problem.

Your service has some use cases... but please do not tell me you seriously expect it to replace lawyers when it comes to managing one's estate.
Yes, that is historically true.

Less so nowadays, where HTML is used for layouts closer to say, PDFs.
> In the long run, for readability and maintainability, ORMs win most of the time.

It depends. Anyone working on that code now needs to learn the ORM, the SQL and how to let the ORM generate that SQL for anything beyond the basics.
We are currently moving to using Docker swarmkit (from non-Docker environment). We thought about using tags to communicate environment but it felt like an anti-pattern given how tags work. What we ended up with is the following:

Per publishable branch (e.g. master to prod, dev to QA, shared integration that isn't ready for dev to secondary QA):

- Publish image to private docker registry with tag in the format of <branch>-latest (e.g. master-latest, dev-latest). Also add labels with git revision hash and CI build number to reconcile what is in the image both in CI and in git repo.

- Capture the digest of the published image and put in .txt file as an artifact from CI.

- Add a tag to the git repo with the build number, treated as version number in the form of v<build-number>-<branch> (e.g. v1-master).

- Maintain list of applications' docker image digests that should be running in each environment. We currently have this automatically determined by pulling the digest artifact from the passing-build digest. We do allow for manual overrides, however.

- We have a CI project that updates the docker swarm with these digests and other settings (replicas, mounts, environment variables). We wrote a small tool that does this similar to where stacks/dab files are going but with more functionality.

With the labels and published digests we can go from build to digest, digest to build, etc.

This is working really well so far and we aren't fighting the tools. We may separate the non-master registry later in life, and that's really easy given that docker treats the private registry hostname as part of the tag.
I found these free guided meditations to be extremely helpful: http://marc.ucla.edu/body.cfm?id=22

They are from UCLA Mindful Awareness Research Center.
I guess my link was more relevant than I thought!
There's another false claim like that a bit below. I can only assume that the author is close to legally blind, or uses a VGA-res display to watch the page.
Because tobacco has sticky trichromes, whereas for every other crop the radioactivity just washes off after it rains.
Yup, this is how I wound up with a 45 GB image on my development machine after futzing around with Docker for two hours. Does the same with OS X.
That's only one half of the problem - you now have an alphabet five times the size so you have actually increased the size of the message! You also need to explain how to encode this efficiently to explain compression.
I agree about the matte screen thing. I had one of the last laptops they offered with the matte option, and I used it for 5 years until a month ago, when I bought the rMBP a few weeks before Apple released the crippled new model. (The rumors were extremely accurate coming up to the launch, so I knew I wouldn't be interested in the new model.)

I was skeptical about the haptic touchpad, but now after using it for a while (I got a Magic Trackpad 2 a few months ago) I'm extremely impressed and feel like it is better than a physical click in every way. I think it is better on my RSI as well.
I also have been steeped in Dockerland for the last couple of years. Here are my own Docker pros/cons. Caveat: I am not nearly the power user that thehftguy is or understand Linux kernel issues in any real depth. I’m a lowly high-level language programmer (elisp/Python/Clojure/Java/shell).

Pros:

When Docker works, it’s great. The concept of being able to install software on the users behalf in the container and have the user install the container really does make life easier. The unwieldy command lines are nicely abstracted with docker-compose(.yml). Software upgrades via containers becomes a nearly trivial process.

I work on scientific software that can be a huge pain to install and configuring the packages correctly often times requires the help of the software creator. The fact that you can codify this “dark knowledge” in a Dockerfile is of tremendous benefit. And generally speaking, I like the concept of the Dockerfile. Whatever container technology ends up winning, I hope there will always be something like the Dockerfile.

Cons:

- Docker version upgrades never go smoothly. Firing up docker after apt-get update && apt-get upgrade never works with respect to Docker. You get some obscure error and after spending 30 minutes in Google you end up having to rm -rf /var/lib/docker/aufs. My solution is sometimes to throwaway the VM and start over, but this is unacceptable.

- File ownership issues inside versus outside the container are (or at least used to be) a huge pain in the ass! I am referring to files mounted from the Docker host file system into the container. (And I am also referring to running docker as unprivileged user that is part of the docker group.) The solution I settled on is to enter the container as root, run chmod/chown on the appropriate directories and drop down to a “regular” user with gosu. At that point, you proceed on your merry way by starting your service, process, etc. This work flow solves permission problems inside the container, but outside the container is a different story. At least on earlier versions of Docker, you could lose permissions of files created via the container because at that point they are owned by root as seen from outside the container! More recent versions of Docker seem to solve this problem as I have gleaned empirically and from experimentation but I have yet to see adequate documentation about any of this and I have spent a long time searching! With more recent versions of docker I have observed that the files in question are no longer owned by root (again as viewed outside the container), but by the user that started the container, the behavior I would expect. I’m also not crazy about the gosu solution which seems like a bolted on rather than baked in solution.
Forcing the party line of callback hell as a high quality "Production Practice" is an incredible disservice by not introducing the user to the concept of Promises. It already assumes a basic knowledge of exception handling, so at least they should hint at what is a saner choice.
Don't listen to what people say, watch what they do.