skysight-inc/HackerNews huggingface dataset:
Yes, that is true, 16 is also for urgency and safety messages, but ideally channel 70 should supersede 16 as the routine calling channel. Of course, for that to happen the equipment has to be made actually user friendly. It would be trivial to implement the software to let the OOW simply click an AIS target on the ECDIS to have that target's MMSI entered into the transceiver and a call initiated. If ships were running on free software someone would have already done that, sent a pull request to the ECDIS software maintainer, have it pass perfectly repeatable and transparent integration test suites to make sure the patch won't make the ship go keel up, and Bob's your uncle. But for some reason people seem afraid of this proposition.

As for music, last time I heard that was in the Java sea, but Americans aren't much better, making securité calls when moving their Bayliners, or the USCG with their incessant babble about irrelevant things.
Question was how to get better as a developer and engineer--relying on The User is the worst possible way of solving that problem, because they don't care anything about the tech...they just want results.

Your advice is correct about how to get better serving users, but that was very much not the question being asked.
Usually with side projects I bite off more than I can chew and never ship them. This time I tackled something a bit smaller, but hopefully useful. This adds a management command to Django that will automatically generate views, admin, urls, forms, and templates for each model in a given app. After you add a urlpattern to your URLconf everything will be fully operational, with a ListView, DetailView, CreateView, UpdateView, and DeleteView for each model. In addition, it stubs out a bunch of commonly overridden methods to make editing a quicker process. It also tries to make smart choices here and there to get you up and running quickly. For example, in the admin, the list_display is already set to every field in the model other than ID. And each URLField is listed as a clickable link, as is each ForeignKey and OneToOneField. The list_filter and search_fields attributes are also set. I wrote some detailed documentation in the README.

Anyway, I hope this is of use to someone.
Okay, wow... forgive my typos and grammatical errors. Rage replying :)
Not just alcohol. An interesting observation in An Economist Gets Lunch (one of my favorite books on food) is that Prohibition is responsible for putting many great restaurants of the era out of business (restaurants make money on alcohol). The remaining restaurants adjusted to a more "family-friendly" palate, (think grilled cheese, chicken nuggets, and cheeseburgers) and away from more subtle flavors.
Greek FinMin Varoufakis speaks after talks failure [video]
I think that's the goal of firms like Palantir. To help filter that volume of data.
> more focus on quality (eg. decoupling

> technical debt awareness

> enhanced architecture

I think all three of these can be improved and alleviated somewhat by better languages.

Some languages most certainly have cultures that promote properly taking care of all of these as central principles.

It's a bit shortsighted to think that since projects are hard for reasons other than language choices (too), we should just ignore languages all together.

At some point that'd just mean you end up realizing you could be even better with better tools, so why not start now even though everyone hates each other and can't talk to one another?
Once I had to port a large legacy FORTRAN program to a Unix box. It was structured entirely with goto, no procedures, functions, or control structures - just thousands of lines of code with gotos. It was doing some complicated iterative engineering calculations, goto loops inside of goto loops, gotos jumping outside of the loops, jumping back in, etc. It was obvious somebody kept tinkering with it over the years, adding new gotos to make some new features work.

Very hard to analyze what was going on, very hard to refactor, very hard to reason about this program.

I was able to break out some parts into functions, and turn some gotos into loops, but for the most part it resisted my efforts.

This is what Dijkstra was complaining about - programs that resisted proofs because they were hard or impossible to decompose. He was not pedantic about goto.

You shouldn't worry about a goto here and there when it makes sense.
Absolutely, I wasn't saying that farmers in pre-industrial America didn't contribute anything. My point was that once tech displaced the majority of their jobs, they didn't all just sit around and not do anything.

Technology freed up their labor from producing food and allowed them to produce things like automobiles, textiles and eventually computers. The idea that new tech will leave large parts of the population with absolutely nothing to do has been suggested before, but we still have no example of it actually happening, and in fact, far more examples of the reverse.
This is correct.

Just to add to this — most freelance work comes through client recommendations and word-of-mouth referrals. This translates to building a reputation, which in turn requires you take your outlook and presentation very seriously.

I'm not saying you're doing this, but in general — replying "lulz, this projet is dope" to a client will not help a freelancers case.
Did not know about this. It looks great, I'll definitely be trying it out!

The project name was originally calc.go, but as you can imagine that didn't work out too well with `go get`.
That's a common misconception. While designing your own cipher or implementing AES is a terrible idea, it's fairly easy to produce broken systems with strong primitives like AES or HMAC, and the brokenness would not have anything to do with the implementation of those primitives.
According to the report, researchers within the USA were infected with Equation Group malware too.
I think the missing piece is here:

"I am not questioning the many benefits of broadening or learning activities, just the premise that they lead to any sort of mastery." - Rich Hickey (from the same gist).

Norvig is speaking about becoming a better developer by becoming exposed to tools that solve problems in different ways, so that you can internalize those different problem-solving techniques and apply them when appropriate. But exposure alone has only a limited benefit - at some point being able to write a quicksort in a new language is going to produce diminishing returns. At some point understanding the advanced techniques offered to you by a programming paradigm is going to require studying that one paradigm to a greater level of detail.

Hickey is speaking about becoming a better developer through 'mastery' in the sense of thoroughly understanding a system, having the ability to acquire new information, identify and solve problems that comes only through extensive experience.

These are two different ways to become better as a developer. Hickey's point is that the 'skill ceiling' for the former is very low - once you've been exposed to a number of different paradigms, you can either continue learning even more languages for little marginal benefit, or you can begin to master one or more of the paradigms you've seen. And that mastery builds a whole different set of skills that will make you a better developer no matter what toolset you end up using.

> I can't help not getting excited by React or not spending a month learning OCaml or building side-projects tangential to my 9-5 line of work...it is a sure fire way to level up as a developer.

Do you feel the side-projects you've worked on in the past have made it easier for you to work on your job, or your current side-projects? Have they given you more insight? Do you come across solutions more easily because...

* you've seen and solved a similar problem before?

* the month you spent working on OCaml gave you insight into a functional way to reframe the issue?

* your exploration of react.js gave you a better appreciation of client-side engineering issues?

* something else?

If you can honestly say 'yes', you are almost certainly leveling up as a developer. Otherwise, you might want to examine whether your side-interests amount to more than dilettantism and whether you might be better served spending some time focused on a single topic.
Indeed, but the Common Lisp condition system exposes it and wraps it elegantly.
This.

Especially if said agency can feed you work so you don't have to do any of the hustling/selling. It's a huge peace of mind and you get to stay 95% billable.
I feel like the article missed a big point about the lessons we (should have) learned from atomic energy: that the negative aspects of nuclear power (mass destruction, etc.) have significantly outweighed the positive aspects (relatively clean and abundant energy, with a safety track record that's among the best of any energy source despite a few high-profile incidents), likely because the negative aspects were humanity's first impressions of such an energy source.

If this "software revolution" is to be a positive direction for humanity, we as a species must learn from this. The sooner a positive and constructive use of a technology can become household knowledge, the better.

IBM's recent dabbling in machine learning and AI with Blue Gene and whatnot is a good foot in the right direction for that particular potential-weapon-of-mass-destruction, and hopefully other companies and entrepreneurs can spearhead further developments there in order to emphasize the use of synthetic intelligences for benign uses - self-driving cars, self-cleaning homes, the works.

Meanwhile, the idea of being able to genetically modify crops in ways not previously possible through selective breeding alone is very promising, though it certainly needs to overcome the bad PR tacked onto it thanks to the likes of Monsanto and its ilk. The improvements to crop yields made possible with genetic engineering will at least postpone humanity's eventual reaching Earth's capacity, giving us more time to build up our orbital infrastructure and prepare for humanity's eventually-essential need to expand beyond the confines of just one quasi-spherical rock flailing about in space.
She didn't get locked out until she changed her name from her father's to her mother's. It seemed pretty obvious to me that she got flagged because she changed her name after eight years of Facebook use, not because of what she changed it to. She wonders why white people with hippie name accounts don't get shut down, the obvious answer is, they do all the time and she just doesn't know about it. And they typically don't get shut down unless the account does something suspicious, or someone reports it.
Another one: "it's low prices" -> "its low prices".

its -> possessive form of "it"

it's -> "it is"

OP seems not to be a native speaker of English but is doing well despite that.
The best startup opportunities will pay off more than the best big company opportunities. On the flip side, even the worst big tech company job will pay off more than the worst startup job.

The problem is, it's a lot harder to determine which startup opportunities are capable of providing a big pay off. By the time a startup is clearly a winner, everyone is clamoring for a job there and the chance for a big pay off is usually gone.

With big companies, the best ones with the best pay offs are always hard to get into, but much easier to identify.

To justify going into startups, you need to love what they stand for and the work that you'll be doing. If money is a major factor in your decision-making for a job, it's best to stick to established companies.
"I like your example quite a bit, but to make a side point:
Do you really think it might be hard for guys to believe?"

That is a good point. In my world view, even the jerks are "nice people trapped in an a-hole's body". I guess I was trying to speak to the "inner nice person" that resides in those guys who don't "get it" yet.
I've been working at the third company where Scala is used in production. I live in a large city (Berlin), so it's not a big problem to find a job in it. Scala is more popular here than Haskell, Clojure etc. It's not that popular on HN in my opinion because it's not that sexy at the moment, has Java burden, not as clean as Haskell, not web dev focused.

Once you start writing code behind Scala tutorials, you will be exposed to Java ecosystem and JVM. Sure you don't need to learn JEE, but definitely things like Java concurrency, Maven, JDBC won't harm.

You can learn a lot from the language and infrastructure (FP, type system, Scalaz, actor-based concurrency, etc.), write critical production systems in it - there are lots of mature libraries and frameworks. There are nice new things coming - Akka Streams, Scala.js.

And don't expect Scala to become mainstream.
Suddenly, I feel like I should spend a heck of a lot more time reading classic papers, books etc.
> If you think this is a novel idea, you’re wrong. Praise Elon’s great PR strategy, but there are already Petafactories (orders of magnitude greater than Elon’s Gigafactory, in terms of output) in Japan, China and Korea to produce batteries.

There is a disconnect between what the author is suggesting and what Elon has said multiple times regarding the output of the Gigafactory. For example, from http://youtu.be/ZHeR2-ifbg4?t=15m40s, "[the Gigafactory is] not just going to be the biggest lithium ion battery factory in the world, but it will actually be bigger than the sum of all lithium ion factories in the world."
Mass is probably a poor analogy, but let's take it a bit further. Let's say you have a sun about to collapse into a black hole under its own weight, and some lifeless rocks elsewhere. You could, perhaps, skim off some of the sun to stop it from collapsing, and use the mass to create a thousand new suns, and breathe life into those lifeless rocks far from the main sun's light.

To be more literal, when someone has no wealth, they have no capability to create wealth. You're simply incorrect that wealth is simply an effect and not its own cause. Like matter, wealth draws wealth to itself. Unlike matter, wealth can be used to create more wealth.
This is pretty much what I was going to say. I think that the best way to be a good consultant is to first be a good creator of value and to be confident in the value you create. I didn't quite flame out doing consulting (I was doing fairly low-level stuff while in college), but knew I wasn't going to be able to eat off of it, so I went to work. I'm 27 now and, in all likelihood, I'm going to go consult again whenever my current gig peters out. Difference is that now I've stepped on many of the rakes and learned my lessons--and gotten much, much, much better than I was when I was 22. Five years isn't a long time, but it's long enough to learn a few things and be able to both create more value and explain how I create value to prospective clients.
> And an "Irish pub" is really a 1990s phenomenon

That is an extraordinary conclusion which requires a bit more evidence than you're putting forward.

Another interpretation of the data is that the entire idea of a bar, pub, or corner bar was Irish by default until the 90's, when it became necessary to distinguish between different types of bars.

As an older fellow, my memory from well before the 90's is that what we think of now as an "Irish Pub" would have just been called "a bar" back in the day.
The author would have done much better if, rather than poking sticks at those who wish to forbid gotos, and posting vague and generic quotes about memes and cargo-cults, they had provided several examples of code wherein the use of gotos was a decided improvement, in terms of speed and clarity, over the best that could be done without it. Anyone who has read code that has been twisted out of shape, or entagled with unecessary "done" flags and the like, and who can be improved with such remonstrations, will recognize the virtue in this point of view.
15 Years of Durability – A Chat with Twitter's First DBA
To expand on this, distillation also solves the logistical problem of "how do we transport fruit (e.g. apples) hundreds of miles without the use of trucks, refrigeration, or pesticides?". Answer: we turn it into applejack!
Yeah, but without autocompletion this is hard IMO. You might want to try photon for that: http://photon.komoot.de/ and with routing see here: https://graphhopper.com/maps/ or https://www.komoot.de/plan
Both are right, and they agree with each other. But you have to understand what they are talking about to get it.

The point of Peter Norvig's advice is that once one has learned 3 different ways to do one thing, it is easier to abstract out the fundamental principles and think about when to take one approach or another. Which makes it easier to understand the actual game.

Which leads into Rich Hickey's advice. Recognize that the game you are in is programming. Which is the art of keeping software doing what we want to it to subject to various constraints including timelines, changing requirements, and so on. This is not the accumulation of esoteric information. This is not the accumulation of prebuilt solutions. Those are necessary, but not sufficient. You need both a skill set and a mind set.

I used to like chess so I'll use a chess analogy. In chess, and many other games, there is a clear difference between tactics and strategy. Tactics is, "I do this, he does that, I respond like so..." Strategy is the abstraction across tactical situations to recognize things like the importance of controlling the center, that attacks naturally proceed along the line of pawn chains, and what affects the relative value of pieces in different situations.

You cannot learn strategy without knowing tactics. Because the accumulation of strategic advantages is useless without the tactical skills to notice and use the opportunities that arise. And mumbled slogans do not a coherent strategy make. So learn tactics first. But to become a great chess player, you will need to master strategy.

The same applies to programming. Programming tactics include languages, paradigms, platforms, building blocks, open source, conferences etc. These do not constitute strategy. Learn strategy. But you cannot do that without learning programming tactics first.
Fair enough - although with this set of revelations at least it's been credited at least to mail interdictions. I was responding in a limited matter to this project, this is an example of what I'm personally fine with them doing. Other people may very well have more trouble mentally compartmentalizing the broad range of activities that the NSA (and other digital espionage agencies within the US government) are up to. Many of which are clearly unconstitutional and should be (and appear to, in some cases) now being scaled back.

In any case, to answer the specific question, we can be pretty sure that our we're not infected with official US government 0day malware by the practical considerations - they go to pretty considerable lengths to keep the spread limited (per the reporting) because once Kaspersky or any other researcher gets their hands on it the utility of the toolsets goes away or becomes highly limited.
Basically, in order to make a case against being extradited, you'd have to convince the court that you wouldn't be given a fair trial in the country making the request.

His problem wasn't that he wouldn't receive a fair trial, his problem was that the laws themselves are silly (but not obviously immoral or excessive). If he had faced a corporeal punishment (death penalty or mutilation), he might have had a case.

Of course the ideal path would have been facing the hearing and then pleading guilty when he was extradited, but the plea bargain likely required him not to challenging the extradition and his chances for successfully doing so were likely far too low to take the gamble.
Do What Makes Your Soul Sing – Free Ebook on Entrepreneurship
The point of the article is that no one knows what to do about it, and maybe we should start thinking ahead to plan for crises before they occur.
Depending on what you do, other developers may be clients. As I note in my sibling comment to yours, I'm not currently doing consulting, but I get a lot of free lunches bought for me so people can pick my brain about clustering, scaling, Docker, Chef, etc.
The BBC has a story on it, it doesn't add much to this but there are some pictures:

http://www.bbc.com/news/science-environment-31491805
Easy to say from the vantage point of history. But folks starved, died when their livelihood disappeared.

http://webs.bcp.org/sites/vcleary/ModernWorldHistoryTextbook...
It seems that you are offput by his title in a way that you feel he is personally challenging your knowledge and experience with JavaScript. I would guess that when he was writing and naming this series, he did not have someone with 20 years experience in mind. Seems like the series is geared towards someone with moderate experience.
> Is there anything else this is comparable too - where a company has the gall to say "another company looked at our black box and said it was good, so trust us alright guys?

Uh, isn't that how third party trust works?

Like how SSL cert verification goes to a trusted root CA for validation.
Unless you opt to run all your own stuff you will need to trust someone. Even if all of Microsoft's code were open source, how can you trust they're not running a modified version?
Those who cannot remember the past are condemned to repeat it. Those who can remember the past are condemned to watch everyone else repeat it.
I'd argue the recovery is about complete.

Go into any neighborhood liquor store, and in addtion to the Big Three and the other inexpensive pale lagers and pilsners, you'll also see something from one of the major craft breweries (Samuel Adams, New Belgum, et. al), -- a couple amber ales, and at least one pale ale or wheat ale. Go into a larger liquor store, and in addition to the above, you're likely to find beers from other craft breweries local to your region, all of them offering various ales and lagers ranging from very pale and light to very dark and heavy, and plenty of points in between.

There's good stuff to be had. You just have to be willing to consider beer to be more than cheap pale lager, and to go looking for it.
Yahoo's brutal corporate re-alignment
"If the Treasury were to fill old bottles with banknotes, bury them at suitable depths in disused coalmines which are then filled up to the surface with town rubbish, and leave it to private enterprise on well-tried principles of laissez-faire to dig the notes up again (the right to do so being obtained, of course, by tendering for leases of the note-bearing territory), there need be no more unemployment and, with the help of the repercussions, the real income of the community, and its capital wealth also, would probably become a good deal greater than it actually is. It would, indeed, be more sensible to build houses and the like; but if there are political and practical difficulties in the way of this, the above would be better than nothing." - John Maynard Keynes
I'll be honest, I'm working through a React book right now, and there's so many additional subject chapters that, while useful, would be better off spun off into their own books. I found the first 2/3 of the book immensely useful, but now it feels like I'm slogging through to finish it (just for the sake of finishing it).

Maybe splitting things up into very self-contained contexts makes a lot more sense than writing another tome.
Show HN: Vdist, creating OS packages for Python applications using Docker
Should there ever be any reason to trust your privacy to proprietary software running on a third party's server? Or is this "privacy standard" they are conforming to just another form of security theatre?
Freelancing teaches business skills that transfer into building a business, which is what every startup wants to grow up and become. Learning to create value that people want and will pay for, is also a very transferable skill.