skysight-inc/HackerNews huggingface dataset:
Quick question from a clueless Linux person: are codebases of FreeBSD, OpenBSD, NetBSD diverging over time, or actively reusing each others code?
Decades ago, the single most useful Japanese learning resource for me was Mangajin, which explained Japanese comics and concepts in excruciating detail:

https://en.wikipedia.org/wiki/Mangajin

http://www.thespectrum.net/features/mangajin/

https://tinyapps.org/blog/windows/201605280700_mangajin_soft...
The way I see it is SVG is a format for humans (that's why it got all those shapes and tricky formats) and its main use-case is browser (so CSS and JS support is not a problem, because it's already there). There should be another simpler vector format for machines, IMO.
That's a great suggestion. I'll definitely set this up.
The precision is in cm, so HORIZ PRE will be 5e8 or 500000000cm = 5000km and VERT PRE is more likely to be around 1e5 or 100000cm = 1km although I'm not sure about this value - maybe 5km or 5e5 would better account for the height variation in the US?
Don't forget to add "Managing disputes and handling difficult clients" and "managing scope creep"
I moved from Stockholm to Edinburgh about a year ago and I definitely use cash a lot more here. Sure contactless is more widespread, but a lot of places don't accept cards or have a minimum spend amount for card transactions.

When I lived in Stockholm I believe I went 6 months without handling any cash, here I can barely last a day without it.
The One Skill I Kept Practicing to Save My Life
Make IoT personal again
It's an integrity issue for sites that you trust. Some people's personal trust model is such that they trust no one and nothing published on the web sways their opinion; if that's indeed true then no amount of MitM content injection is going to influence them one way or the other -- but neither is truthful content. For these people, everything on the web is 'entertainment', and none of it is 'staying informed'.

For people who do use the web to stay informed, reputation, ie. trust, matters. I might think that CNN publishes clickbait alonside real news, but I trust that CNN won't put blantaly false breaking news warnings above the fold about made-up events. Or, if I don't trust a single source in isolation, I trust that if several news outlets are posting breaking news warnings about the same event at the same time, that event must be real. How else would you find out?

In this day and age, refusing HTTPS means that the site author has done a cost-benefit analysis and decided that their content is not important enough to be verifiably originating from them, and that their reputation is not valuable enough to be protected from malicious tampering. In that case, why host a self-hosted website at all?
Steemit Bridges Blockchain and Social Media, but How Does It Work?
NASA Systems Engineering Handbook (2008) [pdf]
Cornering the market is outright illegal.
People don't join a professional army to be a cook - without the large number of cheap conscripts to fill a lot of the unskilled tail it makes sense to hire in non military contractors.
Just curious, why is a warranty a hard requirement for you?
They port code from one codebase to the other, and often it's the same dev doing the work for more than one OS, but there isn't any principled coordination of effort to keep a unitary codebase for anything.
Its the other way around why do you think the Foreign Legion existed
In my experience, closures are a topic that always comes up. It is also important to know how to handle a closure inside of a for loop. I've been asked about "this" binding, coercion, and CSS specificity. I've had to solve problems that required me to know about how to use stacks, trees, and nested for loops. Other topics that have come up are how to architect an app, concurrency, memoization, building out and handling api endpoints, and pass by reference vs. pass by value.

You may not think databases are a front-end topic, but I have been asked about them on more than one occasion. Prepare to talk about sharding, natural primary keys, what your favorite database is and why, etc.

Something that has been extremely useful for me is to have a project that I've built myself to show and talk about during the interview. Although I have had one interview where I was asked to talk in detail about how I built some of my projects that are in my github, I like to respond to general technical questions while referencing something I've built. A lot of times the interviewer will then use my app as a starting point into a discussion for how I would scale it. Here's an example of an app I built quickly and have used for discussion in interviews: http://moviemap.xyz/ More here: http://valeriemettler.com/
We make mobile games for iOS and Android, and we've mostly switched to HTTPS because of people injecting garbage (ads, mostly) into our content.
I live in Stockholm and haven't used cash for several years. I have no cash on me ever, no coins, nothing. It's liberating. I get very annoyed when travelling and I rediscover the cash-based society and the need to always predict how much cash to carry.
50% storage efficiency and 87.5% survival is not an option for us. We store medical images by the petabyte and drives fail much too fast at scale.
I don't think peer review is one of the foundational ingredients. Scientific work should be repeatable and falsifiable, IMO that is all that really matters. These two properties are already hard to muster though.
If the anecdotes I read here are correct, you should be prepared to implement a red-black tree in C, followed by an A* pathfinding algorithm on the whiteboard.

I think the best preparation you can do is to spend several hours reviewing your old projects.

For each project, recall and be prepared to explain in depth:

- The biggest technical challenge you faced and how your team solved it

- The technical tradeoffs your team made in the implementation, and whether you would make the same tradeoffs today

- What your specific contributions were to that project.

- If you can bring code that's great; if not then have the high-level design in your head and be ready to outline and explain it.

If you're anything like me, for three or four projects that represents a couple days or more of preparation.
> almost nothing is manufactured anymore in the West

It's a myth. See this for example:
http://www.marketwatch.com/story/us-manufacturing-dead-outpu...
I have noticed that about DC. I've met plenty of quality engineers but the salaries seem surprisingly low here. It would almost be better to take a slight pay cut but live in Richmond, VA where the cost-of-living is much lower.

Either way I have major doubts about having an engineering career in DC.
>The idea that software is inherently safer because it's released under an open-source license is overly simplistic in the extreme.

Well, no. No it isn't. A higher possibility of more people seeing the code translates into a higher probability of bugs getting fixed. Of course, there's no guarantees, but more eyes means more chances of bugs getting caught. And that means safer.
Maybe I'm doing something horribly wrong. My setup was:

- 6x4TB HDD

- 2x120GB SSD

- OSD per disk

- k=4,m=2 erasure coded HDD pool

- 1 copy replicated (not) SSD pool

- SSD pool writeback cache for HDD pool

I was consistently seeing the SSD writeback cache fill up then the disks thrashed at 100% IO utilization, limiting incoming writes to ~40MB/s from memory.
I find this approach really curious. All the transactions can be monitored by third parties anyway as all the pos systems are networked and subject to even lesser legal scrutiny than banks. Random adverisers can and do build comprehensive profiles. A company is us claims to have full profiles of all Americans. And yet, if there's a chance a citizen might benefit either via less hassle as in the cash case or via better gov services, everybody goes "but think of the privacy". As a result, societies get downsides of both: there is no privacy whatsoever but no value generated for the citizen.
I saw a couple of post by people complaining that they couldn't get their Steem tokens out of the Steem system and into Bitcoin - has this been resolved?
Lobbying from what I understand is a more polite form of corruption for the most part. I think in the parts of the world where corruption is more direct (bribes) you actually have to pay a lot more to get this kind of returns.
"Good IT talent is really hard to find," he says. "And if you’re a superstar, are you gonna work for Delta because you get free flights now and then, or are you gonna work for Google or Facebook, or a billion dollar startup that is giving you stock options?"

Delta made $4.5 billion in net profits on $41 billion in revenues in 2015[1]. If IT talent was the key to their ongoing profitability, surely they could attract some top-notch talent if they were willing to spend a couple of billion dollars on higher salaries. (If you have billions of dollars to spend, you can match the total value of Google's compensation package. The value of Google stock options is easily matched by giving Delta employees extra cash that they can invest in the tech stocks of their choice.)

[1] http://finance.yahoo.com/quote/DAL/financials?p=DAL
As an inherent phoneme, the kana don't really "need" separate names, their pronunciation already works in sentences, although the columns (based on consonant) and rows (based on vowel sound) do have their own designation, being 行(ぎょう) and 段(だん) respectively.

For example, if you wanted to "precisely" talk about し, you could refer to it as さ行のい段 ("the i-dan entry in sa-gyou"), or even さ行のい段の「し」 ("the 'shi' that is the i-dan entry in sa-gyou")
Hooray for Scitland!

[wherever that is?]
That is a lot of work compared to just adding a disk and rebalancing. No need to replace every disk in a vdev just to increase disk utilization to the entire disk when using Swift. No fear of losing a pool when losing a vdev.
One curious thing I've noticed after completing my master's degree in maths is that the jargon of maths sometimes lets mathematicians communicate with far fewer words than non-mathematicians. Irritatingly, I can't remember any off the top of my head, though I know I've experienced this a few times. Here are some contrived and ineffective examples, where I put context in [square brackets]:

- "To first order, [the intervention turned out badly]"
- "Modulo [this error, everything is going fine]"
- "[The situation is] symmetric on interchanging [me and you]"
- "[They are in] the same class under the equiv. rel. of…"
1,2,3,4) You target a specific version of Debian during development and your software will be easily deployable for 5 years without requiring Python-specific knowledge and its dependencies will receive security updates from the distribution.
That's cool, I'm glad to learn that.

Regulations on some things, for example driver's licenses, private mailboxes (and maybe bank accounts?), got tightened up/federalized with the passing of the Patriot Act/Real ID Act in (2004?). For example, to open a private mailbox, I have to fill out a federal form now. Additionally, I can no longer use that mailbox as a registered address for a bank account.

Did you use any kind of federal identifier, for example an EIN (something you can apply to the feds to get, often used for businesses), or did you use your passport/passport number, or none of the above?
Besides that, the article is talking about 100% global adherence to the vegan diet. As long as there are some vegetarians, the non-human-only farmland will have use.

And even with 100% veganism, assuming no miracle crop is invented to use that additional land, it was still a pretty slim gap between the vegan diet and the "optimal" ones.

Really, the article kind of buries the lede when it puts veganism under the microscope considering that its numbers show how moving away from the modern meat-heavy diet would like triple the food supply.
Nice list here, but by no means exhaustive: https://github.com/h5bp/Front-end-Developer-Interview-Questi...
Especially with the long resilver times necessary to achieve a good ROI from the investment.
I agree with you, but there's a caveat: not every passion can be monetized easily. Some passions are so difficult to monetize that nobody has yet found out how to monetize them. Simply because everything can be monetized does not mean they can be monetized by everyone. So telling people to follow their passion is not a solution if their passion is beyond their capability to monetize.

Put another way: everyone is free to set up their own planet if they don't like this one, and it's undoubtedly possible with infinite knowledge and ability to set up your own planet. But it's not good advice to give someone today for obvious reasons.
"profound dislike for humanity" seems unfair.
From 2013, for those who remember it the first time it went around and thought this might be a new finding.
Recursions without names: Introduction to the Y combinator in Ruby
Yes, those people can get IDs. I'm just saying that they, for whatever reason, by choice or chance, haven't done so.
Most people in most startups are not "working on what they want to work on" they are working on what their boss wants them to work on.

Heck, I would wager that >50% of startup employees are not even doing the work they think is most important for the success of the startup. They are doing the work their boss (who by definition is further removed from the facts) thinks is most important.

Heck, I wouldn't be surprised if >50% of startup employees are doing work they know is not important for the success of the startup.

That's what happens when you run a command and control organization. You lose >50% of your output, in exchange for guaranteed alignment of whatever is leftover. As long as you pay people <50% of what they are worth you can still make money.
Just curious, what pissed you off about the Windows 10 Anniversary Update? That update hasn't made it to my PC just yet.
At This Zoo, People Are Put into Cages and the Animal Roam Free
Keep in mind that there is a distribution in the quality/experience of MBA students even in the top 5 schools. A large percentage of them went to very good undergrad schools, got reasonably prestigious (at least from the outside) jobs after graduating, then decided to go for their MBA in their mid-20s. It makes for an impressive resume, but one still wouldn't put them in a CEO role right out of their MBA.

An even smaller group are the students who did truly impressive things pre-MBA. People who joined a PE firm out of undergrad and were very quickly on the partner track. Or people who started a successful company pre-MBA and didn't really need to go back to school, but wanted to. There are usually a handful of these folks in every class. These are the ones where it makes sense they got a C-level role at a company right out of their MBA. Again, it wasn't the MBA that got them the role, but rather what they did before they got in.
The author of this post is right, to a degree, but his arguments are really weak. Here's it simply:

-With OSS, your bugs are more likely to be caught.

-Therefore, it's harder to maliciously hack the vehicle.

-Therefore, it's less likely the software will fail and kill someone.

-Therefore, not opensourcing your code is a liability, because not doing so makes your product killing someone more likely.

Or the auto companies could just admit the real reason why they don't want to OS their code: They're afraid of losing control of their product. Of people, even if they've voided the warantee, using their product in ways they didn't explicitly allow. Of losing their monopoly on support.

If you're going to be evil, at least give it to us straight...
What Makes a McMansion Bad Architecture?
I'd rather use docker over venv in that case. My host python is for horsing around, when something is to be deployed I document and isolate the dependencies in a dockerfile. venv would only solve half that problem and only for python, not including outside delendencies.
As an adult student of the language, my experience is that I was glad to start without the crutch of romaji, for a simple practical reason - Japanese quickly becomes tedious to read Romanized. Kanji + kana are much more compact, and things like the conjugation of a verb and doubled letters which are common in the language are immediately obvious - because the writing system is designed to accommodate them.

Learning 2500 kanji from the beginning is a major cognitive task that shouldn't be a primary focus, nor is it in native Japanese language pedagogy. But learning the kana is simple, again I learned them as an adult and had them down cold in a few weeks of active classwork. My kanji retention is terrible, but learning materials almost always give the reading of kanji using furigana, and there are useful tools for annotating web pages, etc. with furi readings.
There's a pretty good repository of potential questions for front end developer interviews on GitHub[0]. I'd suggest skimming through the list and making sure you've got a decent grasp on most of them.

Ideally you'll get mostly questions that are relevant to what your job will be, but I wouldn't be surprised to see some CS stuff in there as well (basic data structures & algorithms). Good luck!

[0]: http://h5bp.github.io/Front-end-Developer-Interview-Question...
Golang: channels implementation
What is your goal? https://en.wikipedia.org/wiki/Think_tank has extensive coverage, and starts with:

> A think tank or policy institute, research institute, etc. is an organization that performs research and advocacy concerning topics such as social policy, political strategy, economics, military, technology, and culture.

What more are you looking for?
> That's why I believe that this can't be a sufficient explanation. A far better explanation is that there is a trend that vast amounts of people don't see any future for them in this society and the decline in formation of traditional and lasting families is to me an obvious reason.

Another reason is the proliferation of high-quality at-home entertainment (compared to what was available say in the fifties) which allows you to get through life without much human connection (and not feel totally empty and lonely).
Japanese is surprisingly easy to get into, and hard to master. You don't need to know all the grammar in this book to make your way around Japan, you can get a basic amount of grammar down in a few weeks and simply working on "knowing more words" is then all you need.

But, much like English, if you want to know all the subtleties and intricacies: strap yourself in, we're in for a rough ride. There are lots of finer details you can get lost in, just like any established language.

It's much easier than language like Finnish or Russian in some respects (lots of things like needing to match genders, modes, plurality, etc. simply don't exist in Japanese), but then there are also things that are much harder (like knowing which level of politeness to use when talking to someone).

It's all about what you consider "knowing Japanese". Microsoft could never hope to come up with something as convoluted as Japanese, or even modern English. They're both waaaay more nuts if looked at in their entirety =P
There are a surprising number of ISPs that will happily inject content into users' data streams - we've had to go HTTPS with our apps to prevent this on several occasions.

Who's to say it won't be ads next? Who's to say they won't be serving exploits to clients? One lazy ISP trying to make a quick buck could serve untrustworthy ads to millions of people and have it show up on other sites, making it difficult initially to determine the source of the exploit, and preventing browsers' 'untrustworthy site' warnings from protecting users.

The same thing happened years ago with RBLs, where ISPs would return fake DNS results for sites which didn't exist, breaking RBL lookups completely and severely hampering spam detection for any users using those DNS servers. Worse yet, some of them prevent you from accessing other DNS servers directly, making it impossible to avoid their breakage.

If there's one thing we've learned in the last ten years it's that we can't trust ISPs to stay in their roles as providers of connectivity and services; they all see the potential for more money and never seem to grasp the downsides until it's too late.
“If you don’t want jazz to change, you are putting a pillow over its face, and it’s going to die."

Truer words have never been said. Jazz wasn't meant to live in the shadows of Coltrane, Ellington, Monk, Bird, or even Miles Davis forever. Sure the history is important, and technique and the theoretical rigor will always be a necessary ingredient, but the moment Jazz stops innovating and expanding is the moment it dies.
Omg, people go and find out how agriculture works if you only have that primitive view of it. Field, truck, my mouth… my ass.
No cash removes individual volition? Will everyone get a list each month of what to buy?
> Not to me... to me it would be a distraction

Other people might say the same about the graphics, or the interactions.

The point is that it's not zero-sum—no one loses out by the presence of other channels, if the document is dynamic. But if some people do benefit, then there's a value proposition.
Same goes for the field I know well, Poetry.
I tried to use SVG on a recent project and did not have a good experience. The project was converting PDF building plans to SVG and then I had to do some transformation UI to align them to a map.

It worked, but the performance was terrible for non-trivial documents. Anything over 10 MB started to get unstable and provide for a bad UX in the browser. There's no way to get any kind of incremental rendering, you have very little control over the rendering process in the browser once you've handed it off to SVG (terrible API), and there are all kinds of security restrictions that make lots of hacks necessary if you're loading SVG from some place like S3 (due to same origin policy, but there are some additional hoops to jump through unique to SVG as well). Especially bad was the inconsistency across browsers and different implementations. When something goes wrong in the SVG engine internals, you get cryptic error messages (no stack traces or indication of where to even begin -- most of the time the location of the error referenced in the SVG document is wrong as well, or just at the root element). Opaque "out of memory" errors, or the browser tab just crashes. It very much felt like dealing with a black box.

For non-trivial use cases, it makes it very hard to debug. The goal of using SVG was to standardize to a neutral vector format that we could use anywhere, client or server, and leverage a lot of the tools that can deal with SVG or can convert to/from SVG without having to write our own drawing "engine".

In the end it wasn't worth all the hassle and we ended up implementing our own drawing using canvas primitives. Too bad.