skysight-inc/HackerNews huggingface dataset:
I think the problem is people generally look to the big tech companies like Google for guidance on designing their interview process and for those companies it may actually matter that your approach is o(n) vs o(logn).

Big fan of 'homework' to walk through/extend in the onsite interview. The homework should avoid any UI elements and ideally just talk to a database or another API. Another thing to do is try problems that require the candidate to learn something new like a new language, database design, cryptography, distributed consensus, machine learning, geo-fencing, telephony, etc. Strong candidates learn very quickly and enjoy learning new things which usually becomes pretty quickly evident.
Can't Download MS Process Explorer / Problem with old sysinternals DNS?
The US was consuming massive amounts of wood in the 1860s, much of it for fuel. Coal didn't surpass wood until the 1880s.

England switched to coal after deforesting the British Isles for glass, iron, and ship manufacture.

One kilogram of iron requires 80 kg of source fuelwood, as charcoal.
Laying in bed, drinking tea... reading hackerNews...

What are you doing?

<wink>
Same, I find it much easier to start new projects, finishing them after I've done what I consider the core "thing" is much harder. We're clearly not alone.

Not all projects are worth finishing, but I find that once the rush of learning new things have worn off and the only thing left to do is rigorous evaluation or polish my desire to work no it fades.

I find tying some reason to finishing them usually gets me more willing to do so. Giving presentations about my work has often served as a good forcing function since they have due dates associated with them and the fear of being embarrassed by my work outweighs the boredom of doing the last ~20%.

Not a panacea, but it helps me.
This is what it will look like.
http://imgur.com/a/WPBVh
I found it too much work to deal with a complex schema in Firebase.
Code paths that have not been _reached_ are very different from code paths that have not been _changed_, though.
Uniblue System Tweaker 2016 Activation Key Full Version
Maybe you can get a more fruitful answer, if you layout what kind of problem you want/expect to solve. I can tell you to read more books, solve more problem, but I'm pretty sure you already know that, or can know with some google search.
To your latter point, any time we do technical exercises, we _always_ let the interviewee use their own IDE. Nowadays it's easy because most people have laptops, though we do offer to set one up if they do not have a laptop to bring.

Their choice of toolsets and setup can also be a really interesting discussion topic. More than once during an interview, someone has shown me something really cool that I adopted (new key binding, a new tool, a particular way someone had their terminals split-paned, etc).
For the most part I find myself writing unit tests to save time debugging. With a unit test I can create a limited context for my module to execute within instead of having to manually run through through several steps in the larger application to test out some piece of functionality.
I did not claim they were doing anything shady, just that they got those certs through out-of-the-ordinary deals.

It would be a lot more justifiable (and far better for everyone involved) if, for example, the SHA1 certs through Comodo’s pulled root were available to everyone.
I played that mod. It made me really want Forth to have been part of the college education I had.
Clickbait title with little content in the end. You can read more about Joel and his opinion on how software development should be here:

http://joelonsoftware.com/
Passing tests tell you a lot if you pay attention:

"""

Gregory (Scotland Yard detective): Is there any other point to which you would wish to draw my attention?

Sherlock Holmes: To the curious incident of the dog in the night-time.

Gregory: The dog did nothing in the night-time.

Holmes: That was the curious incident.

"""
I thought about that later as well, but as the map isn’t exactly accurate, they could likely have moved it a tiny bit for that, too.
Is the penalty more than they profited from the bad thing? (No according to the back of the envelope calculation I just did)

Why are they paying the money to the government, rather than refunding those who were harmed by the bad thing.

This just amounts to a tax on the people who bought the pens which will just go to the government funds. The penalty may cause the company to change their behavior, but they still managed to profit from the bad behavior. And those that were overcharged are still damaged by having overpaid.

There really needs to be some common sense applied. The penalty must exceed the profit. Those who are damaged must be made whole, or as close to whole as they can reasonably be made. Anything less is an insult on the public's intelligence.
So remove all code for handling unlikely failure scenarios? ;)
This is cool! I like how you've iterated on a central concept (NLP) with different codebases.

Tip: The link to the source is pointing to github pages, which hasn't been set up.
It could be worse. My personal recruiting peeve is what I call the "Dunning-Kruger interview", where they ask algorithm questions they don't understand and don't even realize that fact. It is unfortunately common, and made doubly worse when it is plainly my area of expertise and the reason I was recruited in the first place.

More than once, I've been recruited by executives at Famous Tech Company to run major new initiatives involving vast volumes of spatially organized data, since my expertise in that area is well known, but there is a technical diligence step where I am grilled on spatial algorithms by a shockingly ignorant (e.g. doesn't understand R-trees) Principal Engineer or similar who actually believes no one can know more about the space than they do. (If that was the case, they wouldn't be trying to recruit me.) If an interviewer wants to test my expertise, they better be able to have a substantive discussion on the subject matter and understand the limits of their own expertise.

I view algorithm gotcha games as disrespectful of an experienced software engineer's expertise generally. I like to turn it into a substantial discussion about the algorithm class generally; if the interviewer is incapable of having a substantial unscripted discussion about said algorithms, it is a red flag and they have no business asking those kinds of questions. These days, I just walk away from an opportunity when this kind of nonsense happens.
You are right, but reproducible builds are still very useful, not for high-assurance though.
So certain are you. Always with you it cannot be done. Hear you nothing that I say?
I think it also highlight that different people - even experts from different fields - can have vastly different definitions for things that seem common - e.g. what a computer is or even what "information processing" entails.

So I could kind of understand him if he wanted to defend against people who heard "the brain is like a computer" and then jumpted to conclusions "oh, so the brain has a hard drive and a processor and can be programmed to do stuff"...
Just curious, this account of yours shouldn't be past the downvote threshold, I'm curious if you have a higher karma account elsewhere? The "anonymous" one you refer to?
The hard road to reproducibility
Sure it is and without sarcasm. Even when you do not post anything here then reading what is posted influences you toward certain target. Perhaps you get more interested in Javascript for example or most probably, startups.

The question is not in this. The question is in the scale of the operation and actual spread of the influence.
"* If they expect you to know the circumference of the Earth (equatorial 24874 mi/40030 km, meridional 24860 mi/40008 km) and capital of Sumer in 2281 (Uruk), then they could be interested in someone that has a scientific mind, great memory, and likes trivia or is very into history."

===> ... or who has the skill of typing "google.com" on a browser
Using Go Channels Instead Of Conditions
There is a public exception process to handle SHA1 certificates, and for the rest, they get special certificates of old root certificates that are only on older devices.

Obviously, all these options are not available to anyone except a handful of large companies.
> Followup question: how do we find independent folk to help us check our work?

I don't have a very good answer for proprietary software. If a company is serious, I think they should pay people to independently review it. There's great evidence that software inspections detect a lot of defects, but in many circumstances detecting & fixing defects is simply not valued as much as the costs of reviewers. We need customers to demand independent analysis of important software.

For open source software, the situation is often better. I think you should work with the people who write/manage/run the relevant system or language package management tools so that the packages are reproducible.

As far as the broader question of "checking our work", there a lot of things you can do to make it easier for people to collaborate. I strongly encourage all OSS projects to try to get a CII best practices badge: https://bestpractices.coreinfrastructure.org/ That has a list of basic things you should do to encourage collaboration and be secure. (Full disclosure: I lead the CII best practices badge project. But you should do it anyway :-) ).
Restricting carbohydrate intake let's you control blood sugar levels and insulin response to meals, which generally leads to weight loss in most people.

I get that the wiki article on low carb is rambling, but why HN :?
The writing in here looks pretty clean. My one suggestion would be to get some more examples in there. Most of the descriptions are one line and as a total outsider I just wanted to see some in action.

This document is much more appealing to me than the project's README. Since people often browse just the README when visiting a repository on GitHub, I wonder if you would be better off getting some of the language from sections 1 and 2 into the top of your README. The current README Overview just didn't do it for me. As soon as I saw the first two sections of the user manual, I was more interested because it showed what problem you were solving and how.

> Warning - This manual may reflect a future state of szl.

Got a chuckle out of me.
The big environmental movement followed Rachel Carson's book Silent Spring (1962).

There was some earlier resource awareness, mostly growing over the 1950's, but it really only chrystalised in the late 1960s / early 1970's.

Earlier concerns were much more diffuse. Aldo Leopold, Thoreau, a few others, but little mass awareness.
The Simulation Argument
I've always thought one of the most important goals of learning math was learning how to think logically. This may be coming from a physics perspective where the language is used because it is (arguable)the most accurate tool we have to analyze the world around us.

The average person doesn't need efficient proofs and algorithms. But they can use generalized facts.
Repossessing stuff is not an uncommon legal situation. Having a rented TV set in your home means little. The cops show up, and you hand it over or go to jail.
Is Donald's Locker Room Trash Talking Worse Than Hillary's Bimbo Eruption Squad
What do you say to my rebuttal of the trend to focus on this stuff as stated below?

https://news.ycombinator.com/item?id=12667632

I try to be clear in there that I'm not rebutting your work, which I respect, so much as the extreme amount of focus by all the IT forums on just a few problems that cause almost no failures in real-world vs the ones that cause all sorts of compiler & app issues (including security). I also present an alternative that addresses root causes, leveraging two of your own articles, that knocks out the interception risk as a side effect of just doing the computation and distribution securely.
Bootstrap: teach enough math to turn non-mathematicians into mathematicians.

Then teach mathematician-to-mathematician.
Depending on what language you're using, x=5 may not be as trivial as you think.
I have +6 years of work experience as a developer and for the last two months I have had +36 pre-selection interviews via HackerRank with a wide range of small to medium sized companies. I am not ashamed to say that I have failed every single one of them, but I have to recognize that I have learned more things during the last couple of weeks about algorithms, data structures and prioritization than in most of my career.

This week I was invited by an in-house recruiter from one of the "Big 4" to resolve two coding problems via HackerRank in 120 minutes, plus a third exercise asking about the time and space complexity of my solution. I am 99% sure that I will fail this pre-selection too, but I really do not care, the more I practice now the more opportunities I will have next time. I have talked with people who were hired by Google, Amazon, Booking.com after 8-12 months being unemployed, so — in my case — two months is certainly nothing, I can use the next six months to train myself and maybe next year one of these companies will extend an offer and then I will forget about all this hiring madness.
Also the little schemer series, which just expect you to work things out by hand.
Yes, and what percentage of those killings are actually justified? The police have an inherently dangerous profession.
Fundamentally it is more like tcl (function chaining) than like bash (process chaining), where process pipelining is the central operation, and where functions and programs are equivalent. In that sense, it has mostly the advantages but also the inconveniences of tcl, javascript and similar non-shell scripting languages. My opinion is that they have quite missed the ball in bash on non-nestable arrays when they introduced them quite recently, but besides that, bash is still pretty much my favourite tool.
The slide showing the Internet Exchange's switch says those are Ethernet cables, but they're actually fiber.

I'm really impressed with this presentation, but I wish that one flaw could be fixed.
I agree with the comment about distributed transactions - basically, Mongo had the first mover advantage and Rethink (albeit a great platform and easy to setup / administer) needed a big differentiator. That's actually why I'm using cockroach right now, they picked a great problem to solve (cross dc / cross continent transactions) that enables a ton of developer use cases.
Organizations seek out formulaic ways of qualifying candidates because actually assessing an individual's talent and personality takes time and effort, and is a significant investment. The pressure to streamline the process grows as the company grows and hiring becomes a more frequent thing. It's one of the main reasons I like working for small companies. As a case in point I'll describe the process that led to my current position.

After the application and a brief phone call I was given a take-home project with a one week deadline. The project was directly related to what the company does, and was interesting and fun to do. I submitted a pull request in four days. The pr was reviewed by their engineering team and they all voted to move me forward. The next step was a work along day for which I was paid. These are typically done in person but for various reasons on both sides we did it remotely. The entire engineering team participated in a dedicated slack channel as we walked through my homework project, suggested and implemented changes, joked and in general had a good time. At the end of the day I said my goodbyes and an hour later the recruiter called to tell me they were preparing an offer.

The advantages of this process should be readily apparent. By the time my first day arrived we already knew we'd get along, approached work in compatible ways, etc. The costs of the process should also be readily apparent, and it would probably be really hard for a larger company to do things this way.
Don't forget other ventures e.g.

* http://www.spiber.se/
It depends on how much granularity you desire I suppose. If you downvote and then see the post turn gray or see it turn gray a few minutes afterwards, that's feed back in a sense. Same for if a vote rises to the top in a thread. You get hints of how a comment does, just not a number. The uncertainty there gives you an idea of the communities feelings while not allowing you to split hairs "comment x in thread y has +4 while comment z in thread w (y!=w) has +3, let me down x to make it consistent with z (I hate x's guts anyway)."
Using something like HackerRank as a screen to check that candidates can actually code seems like a good idea to me. But that means setting problems which depend on that, and not specialist knowledge.

For example, an old employer of mine used something like "write a function which, given two strings representing durations down to a hundredth of a second in the format HH:MM:SS.SS, prints the difference between them, in the same format". To do that, you need to do some basic parsing, some simple maths, and some formatting. You don't need clever algorithms.

On the other hand, a problem which requires a "trickily smart O(N) DP solution" requires specialist knowledge, and is not simply a test of whether someone can code. If a company actually needs people who are good at particular algorithms, then this may still be a useful test. But barely any do.

A more ambiguous case is a test i did recently which asked for a function which printed all primes smaller than N. As it happens, i know a couple of (simple!) algorithms for finding primes, so i just coded one. But i know people - including some brilliant colleagues - who haven't studied maths beyond secondary school, and so won't know those algorithms. They might work one out, given time, but that's time they don't have to spend coding.
Another thing missing from interviews is being able to find various talents in engineers for the diversity of the engineers out there. Are they good at finding corner cases, are they creative with product design, are they good communicators with a non technical audience.
Have there been any updates to their lawsuit? http://www.x-plane.com/x-world/lawsuit/details/
My Google Tasks are completely gone
This makes no sense at all. The skills needed to diligently revise algorithms from a book are completely different to the skills needed to keep a startup afloat.
Three More Law Firms Are Suing Apple for Ignoring iPhone 6 Plus ‘Touch Disease’
This is not about soft skills, at least for me.

This is about the environment often present with any sufficiently large open office. I have been in offices with 26 people in a space probably meant to hold 20. It speaks to a culture of cost cutting over engineer productivity; when even a low amount of tech discussions at a given time end up with 6~ people talking simultaneously constantly. (see comment re: emotional noise being worse than mechanical noise, in a prior sysadmin job I worked in an office next to a transformer room and would go back to that in an instant because if I really needed to focus at least I could shut the door; and the transformer wasn't going to ignore signs of focus like headphones and being heads down to come over tap me on the shoulder and context switch me to something that really doesn't need to be discussed.)

Similarly; not having enough private rooms when they're actually needed for focus work, being placed in rooms with entirely distinct feature teams, and being often shuffled between them.

These are all "non soft skilled" environmental factors that have made working in open offices FAR more unpleasant for me than private offices (By private I include up to 1-2~ other people sharing your literal role)

Let me address your "at a cto role you must handle distraction" comment as well, since while I agree, we are _not_ at the CTO role, and to pretend the nature of our work is even similar is dishonest. Long-term context dependent thought work has an extremely well documented penalty from context switches. The CTO role, as has been described in recent HN threads and elsewhere, is far more of a salesman/face/public mouthpiece than engineer or even a technical role, and these career skills lend themselves to very different traditional environments.
Bit-for-bit reproducibility does require changing how you do things. Always use checksums, not dates. For zip we have a special version that sets all the timestamps in the archive to a fixed value. Anything writing records to a file based on a hash table needs to sort the entries. The team needs to be dedicated to making all its tools work this way.

The good part is that you have a clear goal.
Java Encapsulation for Adults
Learning to code without a computer is what we all did, 40 years ago!

He may write programs on paper, and send them to you to type them in, compile them, and print out a listing with the errors. You then send back the listing, and he will correct his program and repeat.

He'll become a great programmer, since he will have to be extra careful to avoid losing one week on some typo.

Now, it's been a few years since gcc has been able to produce a real listing of the compiled source. You would have to write some script to combine the error output with the source file to produce a classic listing. Similarly for other common modern programming language implementations.

On the other hand, without direct access to a computer, he would not attempt to write any interactive or GUI application, only batch programs, unless the interaction is performed only by an external tester for him.

Another idea: some progress has been made on optical character recognition, so if he can write well enough, it may be possible that you may be able to scan his written programs, and convert them to source file easily, without having to transcribe them. So the process could be smooth enough.

If writing ustensils include typewriter, then even better for the OCR!
I can't read the original article? Is police blocking it?
Tests are for refactoring and other changes in code. To make them safe.
In addition to film being entertainment, it's one of the most effective mediums for communication we have right now. Case in point: way more folks are aware of the Narcos subject matter than previously.

Now whether or not we can transition communication to action is another question entirely...
Looks good. Thanks Alex for all your hard work on Hapi and now Electron!

Going forward I have few follow ups: 1) Where is the best forum to discuss Electron, components and application composition? and 2) Can you point me to some example apps built with the framework that have source available?

Thanks in advance!
Not really. "Making it work in practice" is a perfect recipe for creating a cockup. It is a perfect illustration of how software engineering isn't.

Do you really want a real, professional engineer to use the strategy "I don't need verified designs, I'll just make it work in practice" when building a bridge or railway?
Scientific papers aim for a similar objective. They also recognize the importance of being able to summarize. Abstracts are a good idea, and don't necessarily mean people will make snap judgments.

There's a lot of long rubbish on the Internet. Being able to quickly distinguish it from good stuff is essential to using your time sensibly.
English Breakfast: The Baseline Black Tea
What if the candidate doesn't have a machine of their own (company owned)?