skysight-inc/HackerNews huggingface dataset:
Possible side effects correction:

->
if (a)
else (b)
foo = a+b
The author of this article actually has a pretty good write up on how to do just that http://greenteapress.com/free_books.html
The author said he worked through the gap year as his parents provided no support.
Always, always push back.

When I'm on a call and the customer/prospect* asks for something we don't have, I push to make it concrete. Here are some of my questions:

- How are you doing that now?

- Where is that in your roadmap? Is that required for the current phase?

- When do you plan to implement/use it? Is this 3, 6, 12, or 24 months out?

- Is this more or less important than X? Where X is another project or initiative, because there always is one.

- Is that a nice to have or a must have?

* Until they give you money, they're a prospect, not a customer.
Don't see the reason for negativity around "privilege". The point of the essay seems to be to explain how taking a year to live and work in the "real world" changes the perspective of a young adult, particularly with regard to finances.
Thanks, I'll look into it more closely. I tried the libvirt module and I remember having issues with it. I don't remember if there were no compatible debian boxes for it, or it didn't work properly on windows... something was there.

I see this as a vagrant issue though. It really falls short of its promise of being a dev environment where you "never say 'it works on my machine' again".
Using 'pool.ntp.org' is not cool. Ikea should get a Vendor Zone - http://www.pool.ntp.org/en/vendors.html#vendor-zone
In any case, it probably wasn't that hard to fix and OS/2 2.0 would have been a good time to fix it.
This is a good and important question. Also: while I have a lot of respect for people at Google trying to innovate on hiring, make no mistake: Google's heart is in the right place, but they aren't at the forefront of structured hiring, and their hiring processes are notoriously capricious.

The reality is that generating good questions for a structured interview is difficult. You can't just pose a programming problem. As you've noted, most programming problems have multiple good answers. Differentiating between multiple good answers from different candidates re-introduces subjectivity. Your brain would rather convince you that one valid answer is less good than another, even when it's not, that to admit to you that it can't differentiate or generate a narrative for you. The part of your brain that generates narratives is incredibly powerful and does not care about how accurate your hiring process ends up being.

What we tried to do was create questions that generated lists of facts. "Spot all the errors in this code" would be an example of this approach (but none of the three we used). We went into the process wanting to embrace epistemological uncertainty, generating a historical trail of data that we could retrofit to candidate performance.

In the end, work sample testing was so much more powerful a predictor for ourselves that we never fully got around to analyzing the data. Sometimes we'd get candidates that clearly generated inferior "lists of facts"; I think there may have been 1-2 instances where that outcome actually overruled work-sample testing delivered prior (out of a few tens of engineering hires and probably ~100 interviews).
I've had a teacher in high school and a couple in college that were in the process of writing their own textbooks. They would print out and hand out a half of a chapter or so every other week (probably ended up printing out and handing out about a third of the final book over the entire course).

They were amazingly good. I think that teachers who are passionate about what and how they teach, probably have ideas for what they want to see in a textbook. They're probably a bit too busy to have already finished the book, but they're probably working on it and checking its effectiveness on real students.

But I do generally agree with you that "most students" is not a good metric for what is reasonable today. "most students" put in an amount of effort that rounds to zero. This is not really their fault, they're just going through the system that's set up. The problem is how much pressure and reward there is for just going through the system. Classes where everyone really wants to be there just for interest in the material have a very different quality to them.
Containerized data analytics at Scale
Depends on what you're trying to solve. If you need to use a database, serve or get data over HTTP, run things every hour etc. chances are you'll save time and have a more stable and performing solution by using libraries from other parties. For example Spring libraries.
I've been a programmer for a bit over ten years. I've worked at scrappy little startups, midsized companies, now for a tech giant for a few years. The engineers I work with at the tech giant are consistently better engineers than my other coworkers have been, and I credit the very structured interview process. We're trained to ask specific questions, look for specific types of answers, and each interviewer is evaluating different criteria.

Also, it is quite often not the technical questions that end up making us decide not to hire someone. That's just one area. I know it's the part that sticks out, and candidates give a lot of weight to it in their memory of the interview, but you shouldn't just assume it was that your whiteboard code wasn't quite good enough. I actually don't think that's the most common thing we give a "no hire" for.
I imagine zstd's license will hamper its corporate adoption, especially among the big players.

The license granted hereunder will terminate,
automatically and without notice, if you (or any
of your subsidiaries, corporate affiliates or
agents) initiate directly or indirectly, or take
a direct financial interest in, any Patent
Assertion: (i) against Facebook or any of its
subsidiaries or corporate affiliates...

https://github.com/facebook/zstd/blob/dev/PATENTS
Show HN: Selector.js, a jQuery replacement weighing in at 4.75 kb
Can a startup fail because its product is not a SPA?
I was reading an article posted on Hacker News yesterday about shipping an MVP/premature optimization. One of the commenters stated that a startup of his failed because the entire page was getting refreshed!

I personally despise developing/using heavy SPA apps and prefer server rendered applications with AJAX sprinkled where needed (much like GitHub and GitLab).

What do you guys think about this? Do users really notice the subtle differences between the two?
Once we get to the point where most people have several jobs with separate contracts, interviews become superfluous because you can just hire someone for a few hours at a time and then fire them. The only reason that doesn't work today is we're still clinging to the idea that you only work for one entity at a time. Never mind that most people already manage at least a couple bosses within the same company.
Ask HN: How to disconnect from distractions?
Social media, youtube, whatsapp, surfing internet aimlessly...any tips to get rid of this?
As I said upthread, I think this is not true, at least not in the sense that the author is using. Could you describe some of the structured processes you've seen?
PolarSSL is now mBedTLS
Of course. For example, many of the questions for technical interviews involve knowing which data structure to use in a given setting, and applying it to find a solution.

The interviewee is more than welcome to study data structures and interview questions about data structures. A poor student will just memorize questions and answers by rote without really understanding the data structure in question. The good student will actually learn and understand data structures in the context of the solution.

One would hope that interviewers are able to ask follow-up questions about the solution which distinguish between the two.

EDIT: During the best tech interview I have done, I had no idea how to solve the question asked (that is, I had not studied its solution despite this being a relatively common question). I was able to ask articulate questions and invoked understanding of data structures as I went along. Memorizing solutions is a game of luck, and not recommendable.
It seems to me like this allows some incredible augmented reality once a computer vision system can perform do the user-provided analysis of the scene's geometry and light sources.
This is very similar to my method. The first time I teach a class, I draft some notes. After the class, I fix the problems, or at least flag them for next time. The second time through, I add, remove, edit, refine, etc., based on feedback from students and my own observation (and, often, what I have learned since last time :)

Many of my examples start with code, so the first draft of the chapter is mostly explaining the worked example.

It's not very different from the work most profs do when they are developing a class, but at the end you have a book that has co-evolved to fit your students and the learning goals.
Of course my argument is conjecture. I based it solely on my sample size of a few hundred Facebook friends--clearly stated.

Absent other evidence to the contrary, that is enough to convince me that people sharing fake news mostly believe it.

If you have some other evidence to present--please go ahead. Do the majority of your over 45, conservative Facebook friends and family regularly share fake news just to point out that it's fake?
The same way it works for teachers that give tests. Come up with a bunch of questions and only ask a random subset of those questions to each person. Occasionally evaluate the questions and add/remove some.
Are those topics really needed for (what you're implying) is the majority of jobs at those companies? I'm not sure if there's any way to really test this.
Exactly. Open by search is a great addition to the user experience, and it's how I open apps most of the time on my computer.

However, it is not a complete replacement, and breaks down for several edge cases like the one you describe.
They're not ignoring that value; that's simply not what they're writing about. I don't think anyone is advocating for sight-unseen hiring. The problem is with using interviews as a candidate qualification mechanism, where they simply do not work.
As pg doesn't mention though, statically you won't reap "the rewards of a 30 year career out of 4 years" regardless of how hard you work and whether you "truly believe that you are building something that matters and you are going to win".
How did you feel about your experience using structured interviews for hiring?
>I was fired a few months later, with the main reason being that I usually left the office 9 or 10 hours after coming in and only occasionally worked the 12+ hour days that the rest did.

Such practices are illegal (or at least frowned upon) in most of the civilized world.
This is a great point. There are absolutely candidates who are "good interviewers."

I think one of the most helpful methods of determining a good interviewer vs. a good future employee is taking a structured, situational interview question, i.e. "How would you go about selling a new product to a customer?" and turning it into an actionable work sample that is tailored to your company. "We make this piece of software that does this. Spend the next 10 minutes writing a cold email to a prospect that outlines our offering." As the interviewer, grade the work sample on structured criteria that is important.
> In one experiment, we had student subjects interview other students and then predict their grade point averages for the following semester.

Not sure how using inexperienced interviewers proves anything. Would have been more interesting to have lecturers interview the students.
There are no protections because what you're talking about is investing (=varying degrees of risk). It sounds like what you're looking for is what you're already doing. If you'd rather reduce your risk and reduce the percentage of gains you buy bonds. Even if you took the safest method and put it in a savings account or under your mattress, you'll loose to inflation. At that point you're talking about principle retention. You have to think about this as a long game. Stop timing the market, you won't win. You're young and that's your advantage. When the market drops hard, and everyone takes their losses and runs, you take your bond money and buy up their messes in the stock market. Or a safer route would be to not balance your own accounts and get someone you trust that won't kill you on fees like a Vanguard index fund and let them do the work. I say that mostly because again, you're playing the long game here and second, you're playing a game you haven't mastered. You're 30 and you're investing, you've practically already won. Hats off to you.
This has happened to me in a few courses at Queen's University in Canada
And TLS/SSL, authentication using either LDAP, client-side SSL certs.
Custom filters for REST endpoints (Aspect/J-like).
We build our angularJS frontend against a Java EE backend. Works really well - we use ssh scripts to copy javascript/html changes to the app server instead of redeploying, means its 2 seconds between html/js changes and viewing it on the app (like it should be). Can be done.
Matt Mullenweg advocates audition/tryouts instead of job interviews.

https://hbr.org/2014/04/the-ceo-of-automattic-on-holding-aud...
> Cooking, house maintenance, etc. are (and should be) taught by your parents.

My parents were better positioned to teach us calculus than cleaning.
Just my personal anecdote, but I recently had to port the backend of one of my pet projects away from ruby due to performance issues - parsing around 50MB of string in ruby isn't an amazing idea.

So I figured the natural choices there would be go because it's new and in demand, and java because I have a couple years of java se experience.

So, figured, let's evaluate java... and I just failed to comprehend the spring stack just from googled tutorials. There's such a dense layer of magic going on in there, I'd either need to not understand most of my stack, or spend weeks and weeks reading and understanding.
There few questions that you can learn to answer but it is probably very hard to reach the 5 star answer if you do not understand what you learned in detail. An example question would be: what happens when you type www.domain.com into your browser and hit enter. You can answer this many different ways and levels.
The best part about structured interviews is that it gives you historical data on the interviews performance.
Aging signs reversed in mice by killing senescent cells
MySQL has wider adoption historically so of course you will see more large site/apps using it because you have to be around awhile to get so large. I expect that to change because PG has improved replication and performance over the last few years and now a lot of companies are choosing PG for new projects. Those stats will likely change more in favor of PG in 5-10 years.
It took months to become familiar with the existing tech at the company I'm currently working for. Still learning their internals
I think there is a difference in the use of the term Community depending on who is using it. To some the 'scientific community' is just a term describing the body of people writing papers, reading papers and attending conferences. To another it may mean a group of people whose collective scientific activities and values enrich that individual's life and are a significant part of their work motivation and emotional satisfaction.

I think there is a natural friction between those two views. Some people are solely motivated by their work and view other aspects of community as a bothersome necessity, or at best a source of a few collegial laughs. To others the work and the wider communal epiphenomenon are deeply intertwined: they would likely not sustain interest in the work without it.

I think both views have their merits- but they don't mix well.
I find it hard to test opengl. That would be my first approach to fix it: provide a good way to debug and test the compiled programs.
It is available on the same shortcut on Unity as well.
Which of the companies paid the best/has the best benefits?

If it's the tech giant, it's very possible they attract better candidates because they offer more.
Could explain a weird thing that happened to me. I used to throw everything on github as a teen, got a pull request last year to a to-do list app I'd written to learn python years ago
Truly structured interviews are better than even the most rigorous traditional interviews. They are also more expensive to design and much more painful to deliver. Some kind of interview is probably necessary for every serious tech hiring process. Organizations should be realistic about the low quality signal they'll get even from structured interviews. Take time away from interviews and feed that time to off-site work-sample testing.
This is excellent. I've been trying to find a technical explanation of ASCIBOOST for some time. Most of the articles and discussions gloss over the details.

It is possible that this is part of the reason some miners are blocking SegWit but there is more to it. Core (the main Bitcoin development team) promised to provide a block size scaling solution and then reneged. This pissed a lot of people off and led to the blocking of SegWit. I don't see ASCIBOOST as a real problem for Bitcoin.
By the way, Jean Michel Jarre just played a concert in Israël at the Dead Sea against difficult weather conditions.

It was done to promote an ecological message as effect of global warming can be seen in this specific area, see more info about his show on the official website.

https://www.jmj-israel.co.il/en/index.html
It's interesting from a UK perspective to see this described as a "growing trend" - the "gap yah" [1] has been a tradition amongst wealthy students for, oh, decades over here.

[1] https://en.wikipedia.org/wiki/Gap_Yah
Screening 142.731 Startups
Again, n=1 but I've experienced and have friends who have experienced around 50 hours/week for mid/later stage startups.

The stress is lower because you usually have more cash flow or significant rounds that make the work more enjoyable and you have a better comfort of working overall.
I understand that "just write a book" might come off as glib, especially for profs who teach 3+ classes per semester. So I don't mean that everyone has to, or should, but

1. Writing 150 pages that are targeted for your class and your students is easier than writing "the bible" for your field.

2. The quality of the first draft might not be great, but if you are getting feedback and constantly improving, it's not long before you are better off than using one of the expensive tomes.

3. If you start with other free material, you can get off to a fast start (several people have now written books that started with my material, and then evolved beyond recognition).
The research likely behind the book: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2853669
Spring (and latest JEE editions with better support of DI) no more encourages spaghetti designs than does manual wiring of objects, so usually these giant balls of mud are the result of project management and design mistakes, not the failure of the tool. In fact, properly designed system that uses DI is indeed decoupled (because you can limit the number of interfaces between components) and modularized (because you can wire dependency of one module on interface with implementation in another one). Moreover, it opens the way to plugin architecture, because application context definition can serve also as plugin definition and there exists discovery mechanism (e.g. classpath:/plugins/*.xml in plain DI or Spring Boot AutoConfiguration).
I don't think they need software lock-in. They already have hardware lock-in, which is easily 10 times stronger.

Rewiring and redesigning all electronics around a new MCU is just an insane undertaking. Irrelevant of API change in the software.
What are you guys coding that makes you think so much? Most of the time I either code or research a particular tech. I rarely have to think about stuff too much...
Why make it more complicated by adding another path of WP->Static Pages?

WordPress can pretty insecure if not micromanaged. It's often a vector for hacks, and requires meticulous updating.
I remember Windows 3.1 to use far fewer disks. A cursory search on eBay says six.
Google tries to keep interview questions confidential - that's why candidates sign an NDA - and periodically rotates out questions that have appeared in public. Many engineers are also continually trying to think up new questions as well, usually based on their work.

For most questions, there's no "right" answer, but there are a set of points that the interviewer wants to see you touch on. For example, they might first want to see that you can code up a naive brute-force variant of the algorithm, checking whether you know the programming language claimed and can think through the problem, and ask you the algorithmic complexity. Then they'll want to see if you can get a divide-and-conquer or dynamic programming variant with lower time complexity. Then they might ask "What if it has to be an online algorithm, where new input arrives before the computation finishes?" Then they'll ask "How would you distribute this over 1000 machines, and what are the failure modes?"

At each stage, they're watching how you answer, and where you get stuck. If you ask clarifying questions or spend time to think before diving into coding, that's a plus. If you have never heard of the problem before (this is frequent - many questions are not in textbooks), they want to see how you would reason through it, and break it down into subproblems that are similar to textbook problems. If you miss language trivia, most people don't care; when I did interviews I'd usually volunteer the answer if they missed some API call, and when I interviewed my interviewers did the same. If you don't know how to solve the problem and can't make any effort to move forward through a solution, that's a big negative. Similarly if you don't know what the concept of big-O is or why it's important.
> The key psychological insight here is that people have no trouble turning any information into a coherent narrative. This is true when, as in the case of my friend, the information (i.e., her tardiness) is incorrect. And this is true, as in our experiments, when the information is random. People can’t help seeing signals, even in noise.

People see patterns where there are none. I think this is fundamentally why humans fail at statistics. If every fiber of your being wants to see patterns then you will see patterns. Probably why people hallucinate when in sensory deprivation tanks as well. The brain will make up patterns just so it can continue to see them.

The paragraph right after follows up with the statistical failure that pattern seeking leads to

> They most often ranked no interview last. In other words, a majority felt they would rather base their predictions on an interview they knew to be random than to have to base their predictions on background information alone.

So people would rather do busy work in order to continue to satisfy established pattern seeking habits than figure out a better way.
> I kept my 401k allocations mostly in the bonds thinking finally FED will increase the interest rates, but that did not happen.

The Fed literally just raised the rates.
If I remember correctly both Unity and MATE came out as a response to GNOME 3's launch. GNOME 3 had a lot of bugs and was rightly shunned by the overall Linux community when it came out. Some people decided to fork GNOME 2 and create MATE, Canonical thought it was easier to use the underlying GNOME core to add the features they wanted in their desktop. Both options are free and open source software and nobody is locked into using either of them.
Agree. Hardware SDK and tools are utterly terrible.

That's the major reason I stay away from embedded development.