skysight-inc/HackerNews huggingface dataset:
The argument is that Erlang (and its OTP environment) gives you the tools to distribute your system in such a manner that hardware failure is observed and that the failed portion of the system is restarted elsewhere. The granularity provided is better than most STONITH models. It provides a lot of help, but one still needs to make an effort to assure that, e.g., merchandise is not sent unless an invoice is generated.

STONITH: https://en.wikipedia.org/wiki/STONITH
App developers are building apps on top of Apple's mobile operating system. They cannot exist without Apple. Apple has nothing to do with the music being created.
Now to be fair I am in favor of giving employees isolated rooms to work in, however the reality is that at small startups they simply cannot afford that kind of office space. If you're concerned about noise and also the loudness of music playing in headphones, you can always get what construction workers use to block out noise:

http://www.homedepot.com/p/Howard-Leight-Thunder-T3-Noise-Bl...

They look pretty intense but it's certainly one way to solve the problem.
>> I guess it depends on your perspective but THAT IS EXCITING. For me at least.

Who is best at lift and coast. Who can manage tire temps, who can manage tire deg, who can break the 1 sec DRS, then hover at about 2 sec infront...

On lap one, when Lewis was attacking we all knew he had one, maybe two laps to over take, otherwise his tires would be screwed. I want to see that attack last twice as long -- 4 laps! Hell, maybe 5 or even 6 laps! Out of 60.

I think we'd all like to see Lewis and Nico battle it out, balls to the wall.

And when will f1.com offer streaming? Huh?
> Music is Distracting

Sometimes, the right kind of distraction is good. Even if having no distractions gives me the opportunity to have acute concentration on the subject, in practice, having the right kinds of distractions really do help me reach peak productivity.

If I don't have music or background noise of some kind, my mind wanders and I never really reach that "acute concentration" point anyways. But I work best with the right kind of music -- or even a TV show that's just interesting enough to be background noise (without capturing all of my attention).

That said, the wrong kinds of distractions truly are too distracting. The study mentioned that music with lyrics is more distracting; I know that my favorite songs (generally 70s classic rock) really do grab my attention away from work sometimes. Music where the words are unintelligible and fade into the sounds or music without words actually works a lot better. Also, obviously a really captivating TV show will definitely hurt productivity.
Not only is it the most important skill (unless for small home projects maybe), it's also the one which takes the longest to learn and hence the one you really improve on during the years and which distinguishes the experienced ones from the lesser experienced ones. Coincidently, it's also the skill for which you won't find a ready-made answer on stackoverflow or any other site/book.

thinking of it, I've also seen this as a typical difference between fresh CS graduates and those who have been programming for 10+ years. The latter would sometime take way longer to come up with clever math-oriented algorythms than the first, because the graduate has been trained for it and still has it fresh in memory, but experienced programmer would make up for that by being able to use the algorithms in all proper 'best practice' ways one can think of. Whereas the graduate would just slam it in somewhere and call it a day even though there are now x more dependencies and whatnot, you get the picture.
Check out Clean Code by Robert C. Martin. May be helpful.
More like a 90 day interview.
Agreed, but I wouldn't go as far as to thank Apple. And of course it's for PR purposes. All large companies are sneaky.
I understand where you're coming from and I think there is a middle ground, but there is certainly a decent rationale for locking it down: these machines cost $750K to $1M and enormously complex. Allowing an owner to inject some jury rigged code could cause hundreds of thousands of dollars in damage to the machine, or worse yet hurt or kill someone.

Honestly, what would happen if the implements you have hitched to the back of the tractor can't receive the proper instructions because the owner bought some counterfeit FTDI chip. You can set up your spray zones to make sure you don't spray pesticides near waterways, who is liable if that gets screwed up? The counterfeiter? The Farmer? Either way you know John Deere is going to get dragged through the mud for it.
Maybe she did, maybe she didn't. It doesn't matter. Naming is correct, since it's a brand. Same like POTUS - President did this, president said that... when in reality his staff did and said and he ok'd.
> Even if it's less functional.

Having something with missing functionality and/or bugs isn't always better than having nothing if you look at it from a marketing perspective. I agree that hiring someone talented who seems to like your brand to work on their extensions of your product would usually be a good investment, just not always.
Structure and Interpretation of Computer Programs.
This famous book emphasized controlling complexity and how to build a structure that is easy to extend.
Programming in Lua by Roberto Ierusalimschy is one of the best introductions to any programming language. Hw writes the new version along with each language release now, on the grounds that if you cannot explain it right then the language feature probably needs fixing.
C in Easy Steps
You do make a fine point that case regarding unemployment status.

But, I think there is a difference between legalizing prostitution and preventing what's essentially human enslavement.

I'm not saying legalizing prostitution won't help or shouldn't be done, I just don't think it will have as big impact as people claimed, and that it will have possible negative impact if other states don't adopt it.

IMO it's akin to legalizing drugs, just legalizing it won't make drug problem disappear. For instance in cases where some states legalized drugs and most didn't; a state that legalized drugs can become safe haven for criminals from other countries, where drugs aren't legal.
Yeah ok. I agree. Taylor Swift is indeed a brand.
Not in a straight line, but if you lined the walls of the room it should be able to fit in at least one room of a house. A 15x10ft room would probably have enough wall space.
How about asking? All I ever hear about is how it's never been more of a seller's market for software engineering talent.
Nice post, organization definitely is one of the most overlooked aspects of programming. It takes a lot of experience and thinking to be able to organize properly. It's really what separates the beginner programmers and the experienced ones.
Zoommy – all free stock photos in one app
The mining industry has dreamed of self driving vehicles to replace humans in dangerous work conditions for ages.
Gee it's almost like it was a PR stunt.
Just FYI, the author is one of the designers of LINQ.
That's what I meant to imply.
Ask HN: How to communicate security issues to the community of software project
Some project recently had an issue that let remote, unauthenticated users read any file from the server it ran on as long as user permissions did not interfere.

The fix to that issue was implemented in a reasonable time frame but the release was not specially advertised. Instead the mention was inside the body of a generic "softwareproject Version 1.2.3 released" post.

When I posted some pretty angry comments about this, I was met with a mixture of understandable personal defense ("we do this in our free time, don't be so negative") and ignorance ("the users should take care about sandboxing and permissions themselves").

The software is widely deployed on government systems and companies all over the world. Randomly sampling Google results gave me more vulnerable servers than not.

I feel that the project misses the severity of this issue and neglects the security of its users. I want to make sure they understand this and how to prevent similar problems in communication in the future.

Looking around for some best practices on this, I came up blank.

How could the project have communicated the issue better? What are the commonly exercised best practices. Are there industry standards?

Thanks!
Easier React application instrumentation with react-i13n
Honestly, I'm pretty disappointed in this. The music industry has long been using bullying to get what they want, and this is no exception to that rule.

The sooner every traditional media company goes out of business, the better the situation will be for everyone -- listeners and artists.
U.S. Department of Defense Developing UK Hoverbike
Is Apple paying the artists, or the record labels? And if the latter, how much money would actually end up in the artists pockets?
I wouldn't be surprised if 90% of downloads are only from the top 10% of artists. I believe swift was sincere when she said that this isn't about multi-millionaires, but about unknown artists trying to make a living.

By redistributing her income (only for the users first three months of course) she and other artists could really help the ones who are struggling, but hey, if it's all about money that's okay too, but she should own up to it instead of pretending like shes looking out for smaller artists.
https://www.2checkout.com/
I think you're correct. I can vividly remember a local news story from at least 15 years ago that talked about self-driving cars being just around the corner. All it would take is putting sensors in every roadway and having dedicated lanes for them. I was pretty young and excitable, and I could not figure out why we weren't putting those sensors in as roads were replaced around the city. Google requires none of that insane retrofitting, and is therefore much more likely to be useful.
That was one of the rules for the Qt documentation too, back when I worked on it. It's a great rule.
> the right solution is more productive working conditions

Absolutely! To me what's most disturbing about "Just use headphones" is it's highly prevalent information-age companies but shows a deep _lack_ of understanding for the need for _focus_ and long periods of uninterrupted concentration essential for creative work.
> I think the better solution is only allowing in teams who can actually afford to race.

In the past, I had the same opinion. However, today as I see even the mid-pack (Sauber, Force India...) struggles with money. There are 3-5 teams, that can "actually afford" racing in F1. With a better distribution of the profit, even smaller teams could spend more money on development and probably catch some podium finishes. Like Williams, which is not a big team, but still receives a little from the shares because of its past successes.
I think a lot of the commenters here are correct in pointing out that the problem John Deere have solved is very different from the problem that Google, Tesla, Uber are trying to solve.

That said, I think there is a "human acceptance" piece necessary for autonomous vehicles to be allowed on roads. A lot of people are going to fear, dislike, or be otherwise opposed to sharing the road with autonomous vehicles. A lot of people simply don't believe that it is possible for an autonomous vehicle to handle certain driving situations. To be able to point to tractors driving themselves around fields for the past X years is valuable in getting humans to accept robotic cars.
...and now there's tons of free media that Swift's latest album will be on Apple Music (and not on Spotify)!

I think this is a bit too much of a bank shot to have been planned ahead of time, but nice work by Eddy Cue and Apple PR to acquire and then cash in this bargaining chip in probably the most effective way possible.
Great read. 100% agree.
I like The Little Book of Semaphores: http://greenteapress.com/semaphores/
How I Made a Career in Marketing by Telling Stories
I think I would like the ability to edit commit messages for typos without having to force everyone to reset --hard.
Apple is not currently about to release a new App Store with new rules and has to hope that all the current App Developers will move over. Apple Music will suck if too many big artists refrain from signing up for it, so Apple needs to cater to the Artists.

It is the same with Microsoft's App Store, where they literally pay developers money (or used to) so they port their apps over to the store.
That post's been on HN before. I don't know if it's really making a good point.

> Imagine you've implemented a large program in a purely functional way. All the data is properly threaded in and out of functions, and there are no truly destructive updates to speak of. Now pick the two lowest-level and most isolated functions in the entire codebase. They're used all over the place, but are never called from the same modules. Now make these dependent on each other: function A behaves differently depending on the number of times function B has been called and vice-versa.

This is a complaint that the programming language is preventing you from introducing a hidden dependency. This is a strange complaint, given that hidden dependencies are a problem in software maintainability.

I mean, yes, it's convenient now to be able to "just" add global state here and there, but it will come back to bite you later.

> [Single-assignment form] is cleaner in that you know variables won't change. They're not variables at all, but names for values. But writing [single-assignment form] directly can be awkward.

Well, you don't have to write single-assignment form functional code. If you want to modify state within a function in the same way we all know and love from C, you actually can do that. In Haskell you could do this with the state monad, for example. Purely functional programming enables the composing of operations in many different ways, so you actually have a huge amount of freedom in what style you write your code.

> For me, what has worked out is to go down the purely functional path as much as possible, but fall back on imperative techniques when too much code pressure has built up. Some cases of this are well-known and accepted, such as random number generation (where the seed is modified behind the scenes), and most any kind of I/O (where the position in the file is managed for you).

Random number generation doesn't require threading the seed if you really don't want to. In Haskell, for example, you can also:

* Generate an infinite list of random numbers

* Call the IO monad function to get a new random number, which advances the generator behind-the-scenes

While the author might have a point that some things are simpler in imperative code, I don't think their examples really support this. Perhaps they had not delved very deep into functional programming.
Only few things prevent greedy companies from pushing further and further. Bad PR is one of them. I don't care about Tayler Swift, but I think the behaviour of the big players are extremly questionable.
Fair enough. Then you can read my comment as "The term 'gamification' covers two very different concepts, one of which is very constructive...".

Also, there seems to be a big difference between (1) "you completed the errand of picking up the milk; you get 10 million super points and this e-Trophy" and (2) "here are the real-world implications of your actions".
Yes I remember in the UK the older bother of a class mate got 3A's at A level (back when that was hard to do) and was by all accounts the cleverest student the school had.

Unfortuntly when he went to Uni he had a nervous break down.
> 'Going undercover as a sex worker'

This article is about human trafficking, not sex work. The title makes as much sense as 'Going undercover as a construction worker' and then writing about a construction worker kept as a slave in Dubai.
Not commenting the content of article which was beaten to death dozens of times, but whole article appears to be an add by "Linkurious", name is mentioned 9 times in article, and it's also posted by them.

Nice success story to show your customers, but label it as such, and not as some sort of investigative journalism like original topic was.
Arguably, this is what higher level languages like Java and C++ provide. Tight organizational language metaphors that help implement design patterns in a thoughtful, consistently structured manner.
I don't think you understand the benefits of type checkers. Here are some:

- Catching at compile time errors that would otherwise happen at runtime

- Performance

- Occasionally, it can enable making your code mathematically, provably correct

- Maintainability and flexibility in the sense that the code is easier to read by future hires

- And the most important advantage of all: automatic refactorings. Without that, the code base rots because developers are afraid to refactor since doing this without errors on a dynamically typed language requires a lot of tests, which nobody really has. Even renaming a function cannot be done safely in a dynamically typed language and it requires the oversight of a human
Who says that "Mostly functional programming" sets out to control side effects?

How the hell do you get to the conconculsion that's it's no more useful than standard imperative programming? That implies that e.g. first class functions do not have merit, which is, excuse me, horseshit.

Lisp doesn't do that and it works wonderful. Same for ML/F#, PerformunsaveIO, Ocaml, you name it.
"Tell me about writing a compiler"

There's no way to interview for what you're looking for, but compilers seem to require both great organizational skills and some algorithmic chops. there's enough complexity you can't hide lack of one side or the other.

Anyway, asking about building and enhancing a compiler seems like one of the ways to get insight about how people grow code. Every program is a seed. Is this the kind of guy that will end up with a mighty oak tree, or kudzu in 10 years?
Looks like a publicity stunt...
Lvca, good to see the OrientDB team cooperating in the benchmark. Performance is just one aspect when evaluating a database, other things like robustness, stability, community can be as important if not more important. As such as I’ve shared my 10 month experience with OrientDB in:
http://orientdbleaks.blogspot.com/2015/06/the-orientdb-issue...
Not actually. John Deer doest not build vehicles, he builds machinery.

John Deer machines work in a strict set of environments, and although they may be very sophisticated and react to a range of adverse situations, these situations are still much more predictable and the route much better known in advance than roads and streets.

If the autonomous vehicle problem were dealing with different roads, pavements and other pre-programmed vehicles, the self driving car would be a thing from the 80s, together with the robot car welder.
And Apple, Google, Microsoft are much more philantrophic than the music companies ...

Of course not, they're worse as they gain more control. Best for customers and artists is good competition.
As much as I love dynamic languages, I have to disagree friend. :( Static typing confers more benefits than just enforcing a self-documenting type check on your code. It adds a level of expressiveness about datatypes to match the expressiveness of the algorithm itself. This is especially true in languages like SML or Haskell where the type system lets you describe the data you're working with in a pretty precise way.

Dynamic langs have lots of good qualities to them, but every tool has a drawback. Tests, documentation, good team dynamic, etc. hedge against some of the disadvantages of a dynamic language. They aren't a panacea.
Cool, I don't need to run Chrome for this.

BTW, you should release some generic binary tarballs, those debs work just fine on CentOS/Fedora if you unpack them.

No notifications/tray icon in MATE though.
I know, imagine wanting to get paid for the work they produce. What utter scumbags.

I presume you work for free?
Yeah, but landed on the roof. The damage to Apple is done.
Speaking as someone personally affected by all this, I can tell you that encryption most certainly would have helped if used in a system designed with modern security principles in mind. But (especially in government) there is no incentive to redesign a functioning system. There isn't any money available to fund the work, and there is no specific legal liability that poses a risk if you don't.

It's not surprising that corporations and governments don't take steps to avoid these problems when an 18-month membership in some identity theft insurance program is considered equitable compensation for losing 10-years' worth of personal information.
a) All programs include at least one bug.

b) All programs can be reduced by at least one line of code without affecting their behavior.

Therefore: All programs can be reduced to a one-liner, which doesn't work.
The anti-Facebook
Show HN: Weightof.it – Compare JavaScript libraries by file size
Sony Hack: WikiLeaks Releases New Batch of 270k Documents
Same here. I only have 2 years of experience, but right now my opinion is that this is not something you learn in a book (for the moment).

You can learn how to create clean, readable methods and classes with a book (1).

You can learn how to refactor old methods and classes with a book (2).

You can learn how to organize a small team to allow fast iterations with many books.

But building a project lasting more than a few months with constant changes in the requirements, new developers every month, new SDKs and frameworks every 3 days, without the code rotting to death and everything going out of control is a different story, at least for me.

I guess you just learn by watching old guys do what they do after decades of experience...unless someone has a magic book for me?

(1) http://www.amazon.com/Clean-Code-Handbook-Software-Craftsman...

(2) http://www.amazon.com/Refactoring-Improving-Existing-Addison...
I understand your point but your second line is completely inaccurate (at least, in regards to app developers). Apple have never changed the cut that app developers get nor have they ever shown unsolicited ads near/alongside/with apps.
Huh, well how about that. In my last comments on the subject I postulated that Apple could easily afford the money to pay artists/labels during that period. Apparently they could not afford to not pay, image wise.

Not sure if it sounds more cynical or stereotypical on my part, but I'd guess that there's a lot of overlap between Taylor Swift fans and Apple's target market. Good move in the long run for Apple, and in the short term they get to play it off like collaboration. I don't see it as anything but a disagreement between two juggernauts, The Taylor Swift Corporate Entertainment Empire Wordwide (TM) and Apple's Jimmy Iovene Music Experience (TM), but I'll take my pennies and keep on truckin'.
Some professional photographer is calling Taylor Swift out on her hypocrisy.

http://nextshark.com/an-open-response-to-taylor-swifts-rant-...
I've done a few similar things at my previous employer. Basically, taken it upon myself to write internal reporting applications, to much success. I've also done some other small things (AHK, etc..) which worked out well.

Point is, I've been modestly bringing these up during interviews when asked what I've been doing the past few years. It is always glossed over.

I don't think companies want or recognize that they want someone who will be able to handle these tasks. If they knew these tasks needed to be done, they'd hire for it, right?

Seems some of the most important things that can be done for a company may be hidden to the executive team.
Are you saying we should have app developers and content producers with a Taylor Swift-like popular status?
This pretty much aligns with my take on that from four years ago: http://berislav.lopac.net/post/13061099545/the-most-importan...

As wise men said: All problems in software can be solved with more layers of abstraction, except of the problem of too many layers of abstraction.