skysight-inc/HackerNews huggingface dataset:
Where, when, and how.

Where: The school that you attend.

When: Straight out of college, or after working for a while?

How: Online or in-person?

In my neck o' the woods, there's a general sentiment that the MBA degree is more valuable (i.e., marketable) if you get it after already establishing your success in the business world. The route of going to business school directly after college is associated with the suspicion that you couldn't get a job, and still need to come up to speed in a business environment.

The people I know who have done this are mostly techies of some sort, and the conventional wisdom seems to be that business school is "hard" because of the math involved (finance and also some basic statistics), so if you're good at math, then it's not very hard.

From what I can tell, online programs from prestigious schools are gaining acceptance.

I don't know if the rule of thumb about graduate education applies to MBA programs: Don't attend grad school unless somebody else is paying for it. A benefit of getting an executive MBA while working, is if your employer is willing to reimburse you.
High anything is probably not wise. However a somewhat different story from that to which we're accustomed, is emerging.

Am J Clin Nutr. 2010 Mar;91(3):535-46. doi: 10.3945/ajcn.2009.27725. Epub 2010 Jan 13.

Meta-analysis of prospective cohort studies evaluating the association of saturated fat with cardiovascular disease.

CONCLUSIONS:

"A meta-analysis of prospective epidemiologic studies showed that there is no significant evidence for concluding that dietary saturated fat is associated with an increased risk of CHD or CVD. More data are needed to elucidate whether CVD risks are likely to be influenced by the specific nutrients used to replace saturated fat."
Nice photos but low on detail. Here's a more interesting account of Myodes lemmus from August 1877 edition of Popular Science:

http://en.wikisource.org/wiki/Popular_Science_Monthly/Volume...

To give you an idea of just how massive these population explosions are here is an excerpt from the article:

"Mr. R. Collett, a Norwegian naturalist, writes that in November, 1868, a ship sailed for fifteen hours through a swarm of lemmings, which extended as far over the Trondhjems-fjord as the eye could reach."

The 3-5 year cycles drive the whole arctic ecosystem. When there are lots of lemmings there are lots of everything. More lemmings means more food for predators so tundra-nesting birds do really well, fledging lots of chicks since the predators can stuff themselves senseless with lemmings. In years with low numbers of lemmings then the birds get hammered hard until the number of predators crashes also.
A great example of a useful article that keeps me reading HN.
My point still stands. If this is true there is an enormous opportunity for you to get rich. Try it and let us know how it goes.
It's worth pointing out that since FreeBSD 10, there is a new binary package manager, "pkg", which works pretty well and makes package management much less painful.

It makes the experience in this regard not much different from any apt-get based linux distribution. The old way of having to compile everything makes your system very configurable, but it gets brittle on systems where you have to make big upgrades.
Also, given that touchscreens on laptops and even desktops seem to be a thing now, this could well be a starting point for a Linux operating system which can scale seamlessly from smartphone to tablet to laptop. Obviously it's not for everyone, but it could be good as a kind of 'tablet plus', for watching videos, checking emails/facebook etc.

Although Sailfish OS and Ubuntu seem to be much more serious in that respect.
@sama said: "there are now 27 YC companies worth $100 million or more!" - I wonder how many there are for TS?

@Grabcad was sold for ~100m, I wonder what the other major successes have been?
A very interesting article.
For me two key statements come toward the end.

"Did you know that at high altitude, the brain goes through metabolic changes, and some people can adapt while others can't, based on their DNA?"[Renshaw]

"Renshaw, too, is confident his findings are beyond the realm of a fluke, but he isn't willing to dismiss other explanations for the suicide-altitude connection, including studies on gun access. Multiple overlapping factors, he says, are likely in play."
Zfs, to take one example, does do approximately what you want - the file system (or rather, the underlying block storage) has a tree structure, and changes to files are propagated via copy-on-write rewrites up the tree, so that earlier snapshots still get to see the original file.

This does make rolling things back trivial.

It doesn't give you dedupe for free, though. Think about what would have to happen: every modification would mean rehashing the modified block (not a problem, that should happen anyway to verify integrity). Let's say we dedupe at the block level rather than the file level to avoid the need for more expensive hashing operations, and to increase the likelihood of actually sharing stuff. Now, to determine whether we can deallocate the new block, we need to look up the hash. So we need an index of every block on the file system by hash. That necessarily involves either a big chunk of memory or a bunch of random I/O. Both are at a premium for a filesystem - the former for cache, the latter for throughput.

If you just want file dedupe, it's a smaller problem, but is less likely to create gains - most people don't store many copies of the same file, unless they're in the third party file storage business. So it isn't really suited to a general file system. If this is something you want, you could periodically go through your file system, hash all files with only one link count in the inode, and hard link them using the hash as a file name, into an set of directories fanning out by hash prefix. There may be some wrinkles with permissions; I believe btrfs has a different kind of copy with copy-on-write semantics that might be useful here.
But JSON doesn't support comments which are pretty nice in a config file. You can do the ugly comment as property stuff, or strip them out, but you're getting away from the One True Format.
This is a fundamental in FPGAs. The mode where the bit is unstable is called metastability. Most FPGA tools can automatically infer gray code for state machine states, and pretty much all cross clock domain FIFOs will use grey code to indicate where the read and write pointers are located.
Thanks for sharing your story. This is part of why I love HN: I can learn from the experiences of people who're interested in similar things to what I'm interested in, but who're much further along in life.

Also wow, well done on shielding your junior engineers from the worst of the death march. Did you suffer much from burnout during your heroic effort? How did you cope?
But that's what the CIA does. Which one is redundant then?
Does this include startups that were incubated by another accelerator which was bought by TechStars?

Excellerate Labs in Chicago comes to mind..
MRI is multi-threaded, even for CPU-bound tasks - it just doesn't run those threads in parallel.
Qt most definitely won the toolkit war. Multiple applications are switching to it from GTK.
Great piece! I enjoyed it.

The author comments: It's possible to generate Gray codes without this restriction (though to be honest, I can't understand the value of this, as the step-change on the warp around would experience the exact problem we are trying to solve!)

Linear encoders seems to me a perfect application.
Contracts are not a matter of take-it-or-leave-it, they can be changed and amended before signing. As long as you can back up your reasoning, and are fair to them, a reasonable employer should be ok with changing it. If they're not, you may want to reconsider working there, because companies that are overly concerned with having the legal balance tipped way in their favor over their employees tend to be kind of hellish to work for eventually.
do you know about data.gov?
The 3-Word Tweet That Cost a Politician Her Job
I absolutely love the bsd.*.mk system. It's not just that the tool is simple, but that the average makefile is very short and simple. Here, a few examples:

(netcat) http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/usr....

(inetd) http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/usr....

(ntpd) http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/usr....

(httpd) http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/usr....
If you write a C extension to do CPU-intensive stuff, you can release the lock.
A phone-optimized site will have less content, usually, so why send the extra data to phone that don't need it, especially when those phones are running at lower bandwidth and are often billed per gigabyte?
Ask a lawyer if in doubt. Fwiw though, non-competes are often written in such a way that they're unenforceable in court, on grounds that they're too broad (you can't find work) or one-sided (no compensation).
> Runs most GNU/Linux apps via ports or jails, sometimes better than on Linux

Jails is containers like Solaris Zone, or LXC and OpenVZ on Linux. So it doesn't have any relation to FreeBSD ports.

FreeBSD does have binary repositories though (pkgng), so perhaps that's what you meant?

Another interesting point worth noting is that FreeBSD also has "Linux compatibility" modes for supporting Linux ABIs and virtual file systems (eg /proc). Though these are often outdated and generally it's better to run something native to FreeBSD instead.
There are many, many, other cool articles on the site.

http://www.datagenetics.com/blog.html

Once you start reading, you'll spend the rest of the day!
I am "able" to do lots of things, but running a reverse proxy just so a command line script works is outside the bounds of "willing".
>I for one think it's time we saw bold and ambitious attempts at changing the desktop.

I'd ask what problem we're trying to solve. I think desktops should be out of the way. I don't really use "a desktop" for anything. I just need a way to launch and switch between applications, and that's a solved problem in my opinion.
Hence the "effectively" in the parent comment; Ruby's interpreter lock can be very problematic in threaded apps that use I/O functions from C-based gems that forget to release the lock.
If it's Ruby, then it didn't even stand around DSL.
If you liked this, google "single track gray codes".
FreeBSD user since 2.0.5 (1995) - Linux since 0.95

I have always found that FreeBSD has had a much cleaner and more orthogonal feel as a system than any of the Linux distros and was always much more familiar for UNIX 'old hands'. If you come from the school where UNIX systems shouldn't have displays or the frippery associated with PCs and should be interacted with from a terminal you will probably be comfortable with FreeBSD. It shines as a rock-stable server O/S and in most cases trying to use it as a desktop is going to be fairly frustrating - the easiest way round this is not to bother and buy a MacBook Pro.

My view is that in the late 90s early 2000s adoption was impacted fairly significantly by two rather flaky major releases (3.0 & 5.0) where major bits of the system (SMP/Giant lock) were upgraded and took a long time to stabilise. These felt like a step back from the previous rock solid releases (2.2.8 & 4.11). Realistically the next really good release was the 8.0 series but since then the pace of development has really taken off and the 9.0 and 10.0 series are outstanding.

My view is that it is a great choice as a server O/S - with the significant commercial backing as an embedded O/S looks to have a strong future. I know that there will continue to be an interest in getting the desktop bits working but to be honest I think that this is a lost cause and should be dropped (though I acknowledge that the PC-BSD team doesn't agree)

One other point is that there is probably a chunk of the Linux userbase who probably shouldn't try FreeBSD as it really isn't aimed at them.
I disagree, there are instances where having a completely different website for a smaller form factor is beneficial to the user.
Will KDE support systemd on platforms where it makes sense? Of course. Will KDE drop support for non-systemd systems the way Gnome has? I find that virtually unimaginable.
This error pops up for me:

This site or app is sending too much traffic to
rawgit.com. Please contact its owner and ask them to use
cdn.rawgit.com instead, which has no traffic limit.
Yeah, I'd be interested too. I code PHP, Ruby, Python, C#, js and all of them have quirks and stuff. But Python and Ruby are almost identical other than some syntax sugar. PHP is PHP. $needle, $haystack gets me everytime. JS is just evil. Fucking hate that language. Dog turd. C# is nice, a bit verbose.
Your own monitoring and bash scripts
That's certainly possible. I don't control what goes where, I only made the proposal.
It saddens me that this tool does not fail elegantly. It should deny access to the resource rather than mess with the browser.
That's called copy-on-write (CoW) and is supported by a few modern filesystems (including ZFS). In fact ZFS does do some very basic deduping in the way you suggest (ie you copy a file instead of move it, and ZFS will just issue a pointer).

However full deduplication could never be free simply because of the overhead of keeping a table of all the duplicated data and scanning new content for duplications.
Rural areas tend to have more risk factors -- social isolation; elderly population; poor population; access to means and methods (In England farmers have access to shotguns; vets have access to meds); etc.

Risk of suicide in rural areas tends to be higher even if the total numbers are smaller.

http://www.worldlifeexpectancy.com/california-cause-of-death...

That site has some nice data to noodle around with.
On the expressiveness and universality of fold
Ask HN: Sails.js or Loopback?
Which one is better for creating an Angular app with Android and iOS clients? Both claim to offer some level of automatic websocket support. Do one of these frameworks do a better job at that? Is one more 'production ready' than the other?
Systemd is starting to show the signs of feature creep which IMHO is good. Failing early means the ship can be turned around if there's enough will, or at least (newer) replacements of systemd(in case it goes really off the rails) will learn from others' experience.
Pyfin, option pricing in Python
You should start with getting your head out of your ass, and actually doing some research, then.
Ask HN: Best stack for secure API?
I'm soon going to be leading a large team developing a highly-secure, high-volume web API. What stack should we use? Please give concrete reasons, preferably from extensive personal experience.

The best stack for the job needs bulletproof cryptography, a mature ecosystem, and strong appeal to developers. It also needs to be difficult to introduce errors while coding quickly.

It doesn't matter how good I am personally with the stack, which is why I'm asking for input.

(And don't say Node, because it fails almost all requirements...)
Why, FreeBSD is an advanced UNIX-like system for servers, derived from original BSD sources I don't remember exactly when. My first experience was with FreeBSD 2.0

It confirms to recent UNIX standards, such as various POSIXes (pthreads, rt extensions), UNIX98 (I guess), etc. and obviously don't have any Linuxisms, like udev, systemd (thank god!) fuse, you name it, which aren't that important for a server. So you could compile as a port or install as a pre-compiled package almost everything you want for a server.

It runs on pair with Linux on network and application performance, in some cases even slightly better. Notably, nginx prior to version 1.0 has been developed on FreeBSD.

Nowadays here are a few obvious disadvantages.

1. Driver support is fair - it runs on standard modern hardware, but cannot be compared to Linux with tens of thousands of contributors, it has very small core-team.

But it considered much less "marginal" than, say, OpenBSD (which is very clever in its own way) or NetBSD.

2. Vendors doesn't support it, so basically you wouldn't run, say, Oracle or DB2 on FreeBSD (while there is a possibility to install some Linux binaries with emulation). Notably, there is no that "certified, safe Oracle JDK" for FreeBSD, only "unofficial" OpenJDK port.

Not long ago it has a reasonable share of all Internet servers and the recent decline isn't due to any quality or reliability issues with FreeBSD, but because "too many Linuxes everywhere".

It has some clever technologies of its own, like netgraph, jails+union-fs (which is you could call "chroot-based containers before Docker") native ZFS support, etc.

Lots of sane people ran FreeBSD in production, Yahoo is the most notable example. Russians love FreeBSD too - many early ISPs and hosting services has been built on top of it. Lots of developers and contributors are from Russia.

So it is modern, reliable UNIX for servers. But not that popular, of course.
Fantastic. Not sure how I missed that.

Edit: There are plenty of crates not categorized, and that must be how I didn't see this feature.
This starts off looking like a reasonable criticism of systemd, or rather that systemd claims to do more that it (or any alternative) actually can guarantee. It quotes the author of systemd to prove that the claim is made, but it does not give a link or say from where the quote was taken (so we don’t know the context or age of it, i.e. we don’t know it is still relevant).

But then it veers off: “This whole observation is not original, in the comments of the systemd author's blogpost, the same argument is made by Andrew Wyatt (two years earlier). The response from the systemd author was to block him.” No links are provided, so we can’t know what any of them actually said or did.

This smells like deliberate character assassination. Especially the fact that no references are provided seems fishy to me.
I'd like to point out that the linked article links to its own blog about 20 times, but not once to the actual study, which is here: http://www.plosone.org/article/info%3Adoi%2F10.1371%2Fjourna.... Epic.
It is circular, but that's actually a good thing. It just means that large open platforms (like the web) eventually catch up to proprietary systems.

It's a democratizing force. Something that two years ago took an experienced team of professional developers may today take a single novice developer reading a simple tutorial.

Both in the web and in native there will be people pushing the limits of what's possible, but what's exciting is when fringe technologies hit the mainstream and become available for everyone. IMHO, at least (author of the post here).
I used Sails.js for about an hour one time. It was completely broken. The docs were just plain wrong, the code was a mess, and the core developers were clearly swamped. Lots of unanswered issues. It was a nightmare.

I haven't used Loopback, but I can emphatically say "no" to Sails.

If you need websockets, check out http://socket.io
When you restrict to men between 21 and 65 you find suicide is one of the leading three causes of death, and often the leading cause of death, in many places.

California has better than US average rates for death by suicide, but that is because the death rate in older people is unusually low. When you look at rates for younger people you find california does slightly worse than the US average.

Suicide is, sadly, very common.
OpenBSD solution has been to use "pf format" config files for as much as possible. They're all different, but immediately intelligible to anyone who's seen any of them before.
Two basic strategies apply:

(1) Sign the ridiculous agreement, knowing it is completely unenforceable, and plan to completely ignore it when you leave. If you consider this strategy, you MUST consult with a lawyer to confirm that it is unenforceable, and you MUST be willing to pay a lawyer after you leave to deal with the nasty letter they may send you and your next employer. Ask the lawyer how much that might cost, and build it into your compensation expectations. Also, be aware that even if you know it is unenforceable, the nasty letter may scare your next employer into revoking your offer, so be prepared to be upfront about your situation with the next employer, and consequently to expect it to take longer to find the next job. Build that into your compensation expectations for this job as well.

(2) Negotiate an agreement you're actually willing to follow to the letter. Personally, I wouldn't agree to anything that doesn't compensate me for time sitting out, and I wouldn't care much what the restrictions are during the time period. I would be looking for at least 75% of total comp for periods up to 3 months, 100% of total comp for periods up to 6 months, and 120% of total comp for periods longer than 6 months.

IMO option 2 is the far better choice, if at all possible. Two factors would make me consider option 1. If the company is a large or inflexible organization, where you can't negotiate with a person who actually has the power to change the agreement, option 2 might not be realistic. Second, you should try to find out if the company actually has a habit of sending nasty letters to people who leave. If they actually do that, then I would guess they already know that it's unenforceable, but don't care because it's still an effective way of bullying people. I would take this as evidence that they would not be amenable to negotiating the non-compete, and go with option 1.
The answer will be in the videos somewhere. If I recall it was primarily discussed during the Day 2 performance panel, maybe give that a watch.
My attorney once told me that NCAs are very hard to enforce because it's essentially illegal for a company or anyone to prevent you from working for a living is the way he put it to me. My attorney also said that if an NCA becomes a legal matter in court, the authors of NCAs are typically more in the hot seat because because they drafted the agreement to begin with. INAL but as I understand it from my attorney, the author of legal agreements is the party that typically in the "hot seat" to explain themselves in court. Perhaps a layer can chime in and fill in the gaps.
Not yet. So far, email hasn't been a primary channel of communication to clients for organizations we've worked with.

I see it being valuable though. I'm not sure what the best way to implement it would be. An in-app email interface? An add-on to an email client like gmail?
Typeof.dart
And speaking of HR, it's good to always remember: HR works for the company's management, not for the employees. They routinely do things that are not in employees' best interests.
An automatic location-based search would be cool. Btw, how did you populate the database?
It's not a case of 'effectively' or not. MRI is 100%, totally, unequivocally, multi-threaded.

The fact that those threads do not run in parallel is an entirely unrelated issue. Parallelism is not an essential quality of multi-threading.