skysight-inc/HackerNews huggingface dataset:
There was more discussion of this in the submission about Facebook's overhaul of their account takedown process a couple weeks back[1].

1: https://news.ycombinator.com/item?id=9664948
No, I don't do them at all. Stop telling people to code on the whiteboard for god's sake
> there is no way you can make a real-time system using CORBA

It seems the military uses CORBA frequently for such systems.

"the Navy has specified the use of the Common Object Request Broker Architecture (CORBA)—the military's favorite mission-critical middleware model."
http://arstechnica.com/information-technology/2013/10/the-na...

and

http://www.ois.com/Markets/military-and-aerospace.html

The military has control of the allowed CORBA implementations so they don't suffer from different runtimes that plauged it's usage in Internet scenarios, and get all the typed benefits and speed benefits.

Not that I think CORBA is necessarily a great protocol in general, but then again I don't have any idea what tradeoffs are appropriate for the military either.
I understand the PIC technique, but I'm having a hard time understanding how this is different from what a trace might do. That is, inline the impl of method_missing and then optimize the most common path with guards included. Or is it that I'm being too optimistic about the tracer -- and with a generalized PIC one isn't relying upon the tracer to get it right, but forcing a cache on meta-object protocol boundaries?
> - The most surprising result for me is that across all the traits they compiled, the heritability is 49%. Which is much much lower than I would have expected.

But much much higher than almost all people would believe.
Mom is in tears of joy when meets ellen
It is possible to achieve that in SVG more precisely (than HTML).
The README answers this:

To learn Rust.

Edit: It also mentions not being tied to UNIX and appears to claim it will run on Windows. That's certainly something.
Really? I think some of them are actually quite appealing, in particular the last several. I wouldn't frame them as art in my house, but terrifying isn't where my mind goes.
The biggest problem with a procedural/explicit query is a dynamic system. Without a query planner, you don't have the luxury of a system rewriting your queries. When Table A ~ Table B, but then Table B >> Table A, your queries are going to be radically suboptimal.

Of course, if you're never joining, maybe that's not such a big problem, but you'd have the same issue of a specific range in your table grows disproportionally to another range in the same table and the index you are using is incorrect.

With SQL you can often be very explicit using Common Table Expressions as well in DBs that support it. Otherwise, using subqueries, GROUP BY with HAVING, and several other features often, but not always, prevent radically rewritten queries.

Finally, with SQL on many DBMSs you can still get the explicit wiggle room you need using optimizer hints. No, it's not very portable, but neither is ReQL.

Edit: A few examples of being explicit in SQL (a lá Oracle):

SELECT /*+ INDEX(name) */ *
FROM users
WHERE users.name = 'jorge';

WITH users_by_name AS (
SELECT /*+ INDEX(name) */ *
FROM users
WHERE users.name = 'jorge'
)
SELECT *
FROM users_by_name
JOIN profile using (user_id)
ORDER BY age;
> France lost a region called "l'Alsace et la Loraine" and it leads to WWI.

I know quite a bit about the events that led up to WWI and I'd never really heard of this before. The events that led to WWI are very complex.
Wow! That is impressive. I appreciate the tip on those.

" I still look around for Sun Ultra kit now and then but the wife has other ideas because it's noisy and expensive to run."

The battle that never goes away. Haha. This is why you need a basement or soundproofed room for that stuff. That's on my todo list for next house.
From a learning perspective, reimplementation has key advantage versus other kinds of projects: the design is completely done, so you can focus exclusively on the mechanics of implementation.
The British Army's Bowman radio system suffered from similar troubles: https://en.wikipedia.org/wiki/Bowman_(communications_system)...

I think credit should be given for the standards-based, open architecture approach. I believe that is the right approach for a procurement project like this. The problem appears to be with the manner in which the requirements and delivery were managed.

It's easy to scoff at such failures but three-person startups and MVPs are a world apart in terms of the scale, time horizons and practical challenges faced by military hardware.

It's a pity the armed forces don't make better use of commercial talent when they're undertaking this kind of procurement project. They may be at the cutting edge when it comes to the technology they're looking to reply but the management techniques they're using are about 60 years out of date.
I don't do whiteboard interviews but something similar (I'm in marketing). I'm not looking for people to ace the interviews, though obviously, it doesn't hurt. Instead, I'm looking for people who will be able to perform with training. They don't need to be perfect already and I don't expect them to be perfect. Instead, I expect candidates to have the basics down so that once they learn how we operate, they'll be able to perform.
Navy-Red Team Moves to Business
Those with severe health issues are not obligated to fast. Those that do have health issues but are still able to fast notice an improvement in health if they fast in the recommended way. If they continue with their poor diet at the prescribed eating times then nothing changes.
SQL is declarative: you tell the RDBMS what you want and its job is to do it. That's how SQL is and how it's always been. A better RDBMS will optimise the execution plan for you. The point about indexing is somewhat valid, but that's an integral part of schema design and something one should define from the outset based on the data's intended use.

By 'explicit', what I presume the author to mean is 'transparent'. I agree that development processes should be transparent, but I don't necessarily agree that imperative is better than declarative. Indeed, the use case for SQL is data manipulation and analysis; arguably that doesn't come under the remit of 'development', even though programming is involved. Hence the prerequisite of a properly setup schema by someone who knows what they're doing!

Declarative languages definitely have their place.
In many cases distributed computation is needed when there is BIG data, which won't fit on a laptop like in that example. I.e. distribution is needed not only because computation can't be done on one node (i.e. it would take too long), but because data can't possibly fit on any one node.
More/earlier HN discussion here: https://news.ycombinator.com/item?id=9736598
My two cents: (not hiring for a well known west coast company, but still)

This is how I rank candidates. Let's say for a common question such as lowest common ancestor in a BST.

1. if they know the solution already and tell me they know it - major points, most interview prep books include it and they came prepared and they are also honest. I let them implement it still (and add some twist of my own)

2. If they don't know the solution and still figure it out, might even score higher, but people can "act" that they know it and some interviewed will fall for it. I want to believe I catch bad actors but can't say I can catch good ones. In any case if this is a question that appears in an interview prep book, I would expect them to know it (most people don't)

3. If they don't manage to implement it correctly, this is the biggest turn off. You CAN write correct whiteboard code if you WANT. I'm not with a stopwatch. If you don't then I consider it as sloppiness (more than "you can't code")

4. How you talk and behave - most important. If you can't figure it out yourself but ask me questions, if you try a simpler problem first, if you talk and explain what you are doing, if you run your ideas with me asking what I think, if you are determined to figure it out, ask for hints and immediately understand them and get this "aha" moment of how didn't I think of it rather than oh sucks I didn't think of it. If you are excited about the solution more than the fact I gave you hints for it, then I'd like to work with you. Asking questions is so important. Also not arguing with the interviewer and being a nice person really helps. I prefer shyness to overconfidence. Arrogance is an immediate no. Asking questions leads many times to a yes. Even if you didn't ace.

Bottom line with the existence of books courses and forums that list so many interview questions (some are on algorithms that took several years to develop) so knowing the solution is likely to be known from a book means you are not tested on your academic algorithmic development skills, you are tested on implementing something you read on CtCI with a twist perhaps. If anyone reads CtCI then interviews will just become harder.
Are these jokes?
And they didn't include a direct comparison to more common IF: the control in the mice and human was both one's normal diet. So the exact causal claim established a little ambiguous.
Sorry if I wasn't clear, but I am looking for a more general answer! I would like to know in which case it is useful (to other people) and discuss it's value comparatively to writing interfaces to other languages.
>Also, protein as a nutrient creates a similar insulin response as carbs.

If you look at graphs comparing them you will see protein is greatly blunted compared to carbs.

The body being in ketosis is primarily medicated by the availability of liver glycogen, temporarily insulin spikes will at worst only pause ketosis. Protein can be converted to glucose via gluconeogenesis, but (compared to felines) the human body can't do much of this and its usually only an issue if someone exceeds the standard recommendation of 0.8g of protein per lbs of lean body mass by x2 or more.

Any diet that keeps your ketones high, ie keeps you in ketosis (assuming you are healthy) is a ketogenic diet by the scientific definition.
You are right, with a tracer, you get most of that for free. For a meta-object protocol, you'll need however still a little bit help to avoid creating too many guards. And, the PICs or `dispatch chains' are very useful in the interpreter, which avoids enormous warmup penalties.
We have an HOA. For years, I've been getting crap from them about not parking one of our two vehicles in the garage. I work from home, so IMO the best bet for me is to keep my car on the driveway.

We had a house a couple doors down burglarized twice within 6 months. I'm still being stubborn and keeping one of my cars on our driveway whenever I can.
Eh, it varies. The apollo program was pretty good. There was some stuff with networking that seemed to take off a few years ago. The human genome project was pretty spiffy.

The win rate isn't real good though.
it is going to be very hard to be price-competitive with "not eating"
Here's a lot of prose that reduces to "the place my line is drawn is more legitimate than yours".
In this case, it's a learning exercise. Sometimes, it's because there are other benefits, such as making it easier to distribute or easier to tie into specific parts of the algorithm than may be possible by calling a library that provides a high level interface.
It probably was, difficult to tell as it is extremely clean HTML, but the referencing seems to hint at bibtex (a referencing system for latex), with class names like "bibitem" and "biblabel".

>and if so how
How is easy, they are many different programs, here are a few: https://enc.com.au/docs/latexhtml/. Which in particular is a bit harder, there is no
<meta name="generator" content="...
that some Latex->HTML converter leaves in, but I suspect you could turn that feature off. I think this page uses custom CSS too, as its using Google Fonts.
"So, what do you think about Swift?" followed by whatever questions it takes to elicit a real opinion. Any iOS developer should have a solid opinion on the language, either of the form "I'm sticking with Objective-C because X" or "I love it because of Y." Either is a great jumping-off point for an awesomely insightful technical conversation.

If they don't appear to have an opinion or clearly haven't thought/read much about Swift that's going to raise a serious flag.
I haven't used Node.js in ~3 years (thank god!) but if I understand this correctly, Node.js doesn't have an internal way to stop receiving data which in turn prevents Node.js from signaling backpressure on the client by way of the client's buffers being full (assuming the client is using TCP).

That seems odd given how easy of a feature this is to implement usually. I know Node.js doesn't allow its users to use threads in their programs but they should consider carefully using threads in a few more places internally to implement necessary functionality like this.
I don't agree with the essay's premise.

>Having your query language be explicit means that you've hit at exactly the right level of abstraction: not too much, but not too little.

I don't like the label of "explicit" as if it's an objective indicator on the continuum between low and high abstraction. It comes across as a value judgement that we'd all agree on and I don't think there's obvious consensus on architecting a data access language.

>If we wanted to dig deeper into this query, we might want to know if the "WHERE" is getting executed before the "ORDER BY". Can we tell from the query if this is the case? No, we can't. You'd have to look it up.

Not knowing the internals of execution is actually a deliberate design feature of SQL. The SQL is meant to be a declarative statement that expresses an algebraic set of rows. (But sometimes, the mathematical purity of this abstraction "leaks" and DBAs/Devs have to add HINTS or do SQL EXPLAIN PLAN to dig into what's happening under the hood -- but that's a separate issue.)

I suppose if one really wanted to affect the order of operations at the SQL syntax level, one could write a VIEW or a subquery with the ORDER BY and then write the outer query with the WHERE clause. I haven't tested this to see if any of the major SQL engines would rewrite this type of convoluted SQL of ORDER BY -then- WHERE clause.

Yes, with UNIX command line, you have different execution characteristics of "ls | grep | sort" vs "ls | sort | grep" but one can't translate that explicit-sequence-of-execution mental model to SQL.

* Does this increase cognitive load? Yes, it does. But this is outweighed by the ability to understand how your query is being executed.

I'm not convinced of this conclusion.

Also, I'm not sure RethinkDB works like this as a deliberately engineered advantage. The RethinkDB devs can clarify but it's possible for their engine to work like this because it's more straightforward to implement the parser and not because there is overwhelming inherent superiority to this approach. With traditional SQL (e.g. Oracle, MSSQL, etc), the query rewriting engines are very mature and can be more aggressive and thereby fulfilling the goal of a declarative mathematical purity. However, it takes lots of programmer man-hours to translate declarative SQL into optimal execution plans.
Sourcepoint: Former Googler Will Sell Tech to Punch Through Ad Blockers
Docker 1.7 Released
I don't agree with this conclusion. I've worked with Postgres, MySQL and Oracle, and found that it is important to have a good understanding of the possible execution plans for a query. I will sometimes construct a query very carefully to achieve a particular plan. And when things go wrong, I run EXPLAIN PLAN, examine statistics, etc., and tweak my query to do what I want. You really have to do that to obtain good performance in some cases. It does undercut the claim that SQL has to being non-procedural, but that's life.

I do NOT want to have to construct the query execution plan manually for every single query. Usually, the optimizer will do a fine job, assuming the database designer has made good choices regarding indexes and other physical design issues. But there are always a few complex, tricky queries where you do have to understand internals. The "cognitive load" is the same, and having a high-level query language means that when you do make your subtle and deft change to rescue performance, you often just tweak a query, instead of rewriting a detailed query plan.

(Extending this position a little: I have come around 180 degrees and consider ORMs to be a bad idea overall. When you do need to be very careful about writing a query, the ORM adds a layer of complexity -- not only do you need to control the SQL, but you now need to ensure that your ORM can produce that SQL.)
Apple Music Radio is almost live?
"I don't want to be politically correct. But it looks like they only way to survive is to be that."

It is the only way to survive. If you say the wrong thing, even if you aren't attacking anyone, you could have your career or life ruined.
Just look at the ex-Mozilla CEO for a good example of this. He donated a small amount of money in a cause he believe in, but because it didn't go along with the community narrative, he was bullied online until he was forced to resign.

If it had been the reverse and he donated to a pro gay marriage fund and the company was extremely religious, the same community would be on the side of the CEO. This is what tells you it's all about politics and has nothing to do with what people tell you (freedom, etc).

I just don't understand why we can't just live and let live.

In the end, it means that people like me that ordinarily just want to live and let live now have to resort to under-handed tactics (like getting people fired and ruining the lives of people) to make the world right.
IMA.js – stack for developing isomorphic applications
> I think credit should be given for the standards-based, open architecture approach.

True, but then the decision to expose FPGAs as part of the programming interface was absolutely wacky. FPGAs are some of the most proprietary devices on the market, usually requiring a vendor toolchain to even produce working bitstreams for the devices.

They defined the interface at the wrong level. They should have developed something like an MII interface and focused on open framing and message protocol formats rather than on open source waveform generators.
I assume these are release codenames? I see "Thumb Tacks and Bailing Wire" before this...

Clever names, but without context it's sort of confusing.
I don't understand. Does SVG = scalable vector graphics? Is so, how is that related to positioning text on a page?
If Apple holds any patent regarding Swift, there will be lots of strings attached. You just won't see those in the license itself.
People are different, and I'm pretty sure "I'm just teasing" is nearly never the appropriate response if the other person is upset. Either a serious conversation or an apology are likely the right approach if the person does not like the way that you're interacting with them.
Daala decoder in Rust would be neat.
Inductive Logic Programming: Techniques and Applications (1994)
That's probably closer to the truth. My 9 year old nephew was more mature than his sibling and cousin because his interaction was almost entirely with adults, but his 2 year old brother is WAY ahead verbally at the same age because he interacts with his older brother ALL the time.
I'm very curious how your workflow is for putting together this paper! I put together https://github.com/Hoverbear/acm-pandoc-paper for my own purposes but there is some work to be done.
Aside from project's reason, there's one very good reason to re-implement a bunch of stuff in Rust: testing whether it delivers. It's being pushed as a safer, better systems language. So, let's take many different C/C++ apps, rewrite them in Rust, and see what the results are across many metrics. By the end of it, we should know Rust's strengths and weaknesses in real-world coding.
I have never met a Muslim that didn't put on 5 kilos during ramadan from ridiculous iftars and judicious day light napping. I suspect that may cancel out any benefit fasting might have.
How to Make Your First 10 Sales for Your ECommerce Business
Not posting anonymously because - I think - my opinions on this matter are well known by those who know me.

1) There is a sexism problem in tech. I have seen it first hand.

2) It's not present in all companies all of the time, and gender balance is not evidence, in and of itself, of the problem existing in a given workforce.

3) Sexism is not unique to the tech industry. My wife is a qualified helicopter pilot, and was told (in 2008!) "sure, send in your resume, but I should warn you that we run an unofficial no-chicks policy" by one outfit she applied to as a junior pilot.

4) The issues about which you're complaining - bullying, harassment, restraint of trade etc. - are not in any way related to either sexism or the tech industry. It's about power. Groups who have in the past been marginalised and oppressed are now becoming powerful, and are abusing that power in exactly the same way as their erstwhile oppressors. It's seen as okay by them and their supporters, because it's targeted at 'bad people'. I used to work for a University nearly two decades ago, and saw the same pattern play out there in fields unrelated to tech. It's just taken a while to get rolling in our industry.

As Rand once said: "every infringement of human rights has begun with the suppression of a given right's least attractive practitioners". Mencius Moldbug is the example who springs to mind here.
"Memories of the Napoleonic Wars were still quite fresh in the 1870s. Right up until the Franco-Prussian War, the French had maintained a long-standing desire to establish their entire eastern frontier on the Rhine, and thus they were viewed by most 19th century Germans as an aggressive people."

https://en.wikipedia.org/wiki/Alsace-Lorraine#From_annexatio...
I did something similar with a briefcase when my car was being broken into multiple times. Except it also had pepper spray rigged to spray when it was forced open.

Yes, it worked.
Even if you're not doing any joins, the selectivity of your data matters. It's more efficient to perform a table scan than using an index if the selectivity of your filter is low. I wouldn't want to have to manually rewrite a procedural query when my data changes.

I feel like this is one of those "X is categorically better than Y" or "X is better than Y because Z" articles. The problem with these types of articles is that they tend to take an extreme position when the reality is much more nuanced. For the subset of relatively simple problems the author has encountered, perhaps the procedural query is easier to reason about, but there are vastly complex SQL queries that wouldn't benefit from an explicit query like this.
Reference to "Macy Gray - I Try" perhaps?
Back in the days of the 8-bit micros there were some games that were absolutely incredible for what they could pack into a tiny machine. Elite on the BBC micro (32k) was one, but being poor I had a Spectrum 128. There was a helicopter simulator by Digital Integration for the 48k Spectrum called Tomahawk which was particularly good, and another 3D game called Starglider, which was originally for the Atari ST but there were ports to the Spectrum 128 and 48k Spectrum! I seem to remember an article in Sinclair User where they interviewed the developers who explained how they got it all to fit into such a small machine. Self-modifying code and using parts of the frame buffer to store code and data IIRC...
Automated Pandoc Markdown to PDF and HTML, Powered by Travis and GitHub
If you have any other crash snippets, I'll be happy to include them.
Node.js is not bad.
what type of work are you looking for?