skysight-inc/HackerNews huggingface dataset:
Shine? I already said they were terrible, why would you expect them to shine?

But there are definitely areas where they are missing. Consider the tech industry, for example. There are tons of workers in the lower tiers who just get chewed up and used by the industry. They work 50,60,80 hour weeks on salary without getting significant equity or even job security. Or they work hourly at far below what they're worth. Or they work through contract agencies and get mistreated by everyone (with the contract agencies taking 1/3 or 1/2 of their pay with almost nothing in return except access to working at a big company). And it's even worse in game dev.

Or, not far off, look at the visual effects industry. Hollywood is a rough neighborhood business wise, and they've had tons of practice sharpening their cutthroat skills. Everyone in that business who earns a living either gets paid cash up front plus a percentage of the gross (the "stars" and powerful producers and directors etc.) or is unionized and gets paid a standard, decent, wage. With the exception of newcomers like the VFX industry, who didn't have the clout to demand cash up front and tried to play around with competitive bidding, with the result being a ton of them going bankrupt and lots of VFX employees getting screwed over.

Unions wouldn't solve all the problems there but they would swing the pendulum in the right direction at the very least. It's the same with minimum wage laws. Also horribly flawed and broken, but when other more effective mechanisms don't exist currently you have to use what's available.
Thanks! Glad to know that you like the app :)
Cool. What's it like having a 25 year old car? Why'd you choose to stick with it as opposed to getting something newer?
This article is a little hand-wavey. Customer support is definitely underappreciated in terms of its value. Support is the primary connection to your product's relationship with customers and a source of research as well as ambassadors for your brand.

On the other hand, the idea that employees doing one aspect of a company's work could count on being promoted to another area requiring different skills is not particularly common in most industries, pre-internet. Most people who regard doing support as an "in" need to either independently enhance their skills or choose to work at a much smaller company.

One of the sad things that this article exposes is that so many support people choose their careers with the same attitude this article criticises; that support isn't valuable or rewarding to them. Maybe this is akin to people going into teaching, which paradoxically tends to be a major with lower scores and grades than average. People go into a job where they help people not because it's exciting but because they think it's an easier path to working in tech than coding. Great support people committed to what they do can sometimes succeed and grow into more senior roles, and that path should be more rewarded.
Actually doing it may be easy for those familiar with the details.

Doing it with legally-provable assurance that you won't permanently screw it up, and proving chain-of-custody issues along the way, is hard.
I can't find the percentage of Wechat users who use iOS, but that 500 million number is potential based on the fact that Wechat had 500 million users at the time.

Clearly not all are iOS, and clearly not all happened to have that one compromised version.

That was indeed a serious breach, but the rigor of your comparison is lacking.
The FDA also provides a HUGE barrier to entry. Once a company makes it through the approval processes (if they make it), they will have a monopoly on that corner of the medical market for many years. I agree its difficult, but the rewards are higher.
Yes!

Also, the link ought to be fully authenticated and end-to-end encrypted. And one could require the user to press a button on the key fob.
Thank you for taking the time to write this out. This is probably the best description I have seen of why it is enjoyable to write JavaScript. I myself have been programming professionally for 15 years, writing C, C++, Scheme, Java, Rust, PHP, Python, Ruby, shell script, etc. I actually enjoy C and Rust, have a tremendous respect for Scheme, Clojure, Haskell, Scala, ML, etc., yet I always reach for Node and JavaScript because of the great JIT, instant startup time, great debugging tools, and ease of use of npm.

To add to the part about extensibility, many times I have jumped into a "node debug" session, in my own code or in 3rd party modules installed to node_modules. Many times I have added breakpoints or tweaked 3rd party code right in node_modules, or monkey-patched methods temporarily. This kind of thing is often nearly impossible, very time consuming, or just plain difficult to do in other languages.
If you write the loop yourself, you can add everything to a double instead of a float, or a long double instead of a double, if you have those.

Oh, if all your numbers are positive you can also sort the array and it will minimize the error accumulated, but I'm not sure what to do with mixed signs.
You're correct, and I partially blame the author of the article. He chose a very controversial and, in my opinion, incredibly counter-productive way to frame the discussion of progressive web apps.
There's also bash-it, for those who want a similar framework but don't want to move away from bash for whatever reason/s:

https://github.com/Bash-it/bash-it
NPM itself is clearly faulty, but I don't think the concept of outsourcing logic to dependencies is. If something is complex enough to have a legit security vulnerability, it's probably the sort of thing I don't really want to write myself. And yeah, that comes with the responsibility to stay up-to-date. But pretty sure my head would rightfully roll anyway if I wrote my own bootleg SSH protocol and got my company exploited.
It's a bit unreasonable to join a tech company as something other than a technical person or a manager, and expect to quickly be promoted to a top-tier position. No career path works that way.
These are both great tactics that I hadn't thought of.

My greatest "tactic" for conferences specifically is right after a speaker is done speaking, go up and ask them followup questions. This might only work at smaller conferences (like MicroConf, etc) but it's super easy. The speaker will probably be swarmed by 4+ other people, but this is even better for you. You're now part of a conversation group that is socially acceptable for you to just hop into. Wait your turn and ask the speaker a burning question you had. This way you've already made conversation with this speaker, whom you can talk to at other social events. You're also opening yourself up to other people in the talking circle, showing you ask smart questions and they can have conversation with you. You can also listen to what other people are asking of the speaker and you can follow up with those people later if it seems that you might connect.

I learned this halfway through the last conference I went to and I'm totally going to do it every time now.
The Python community has a proper response: https://pypi.python.org/pypi/left-pad/ /s
cheer, 350ms delay gone with iOS9.3
Seems a bit weird. The i3 doesn't have an ignition - it is an electric car.

Even if they mean "switch on the electronics which control the motor" - I find that hard the believe. There's nothing on the key fob which can do that.

And, even if they did, the battery use of a parked car is negligible.
A real programmer makes mistakes, and a real programmer automates tasks. That's what programmers are for.
Yes, that's what I'm saying. Most clubs choose female dancers because both men and women find the aesthetics of a woman more pleasing and less risque. It's a sexual thing. Podium dancers are sexualized.
Yea. I don't think many argue against abstracting complexity into more easily understood orthogonal modules. But some of these modules aren't abstracting complexity. They are ludicrous. They are nonsense. They are a symptom of a very real problem with how JS is programmed, how people expect to program in JS, and the difficulty people have with decomposing problems.

So many people on this page have written about how these are well tested, performant, and correct modules. But, the modules aren't even correct in many cases, let alone providing incomplete coverage over edge cases or the slow performance and horrendous dependencies of many of the modules.
It's likely that many on Hacker News join you in your condemnation of 'right-thinking' persons who happened to have lived in the past. An unsolicited word of advice to this audience: challenge yourself by considering the worldview of your forefathers before summarily condemning them.
And is that the same across mediums...i.e. are email, chat and phone all $30 on average?
Because writing code is what programmers (should) do. If something is simple, then it is simple and won't take up time and energy. If you don't know how to do it, then learning how to do it is worthwhile -- especially if it turns out to be simple. If you make a mistake, then someone on the team must look at the code and understand the mistake. This means that the team learns that things that seem simple are sometimes complex and they learn how to recognise their mistakes. When there is a mistake, someone has to fix that mistake. They learn how to fix the problem. Other people on the team must review that fix and they also learn how to fix the problem.

There is always a balance between getting some extra productivity by using somebody else's code, or getting the knowledge, expertise and control of writing it yourself. Far too often I see young programmer's choose something off the shelf so that they don't have to understand it. This is a recipe for disaster -- for your project, for your team and for yourself.

IMHO, as programmers, we should err on the side of writing code. Often it is obvious that you should use standard libraries, or a particular framework or or another reuse library. But where it is not really obvious, I would start with writing your own code and see where it gets you. You can always replace it later if it doesn't work out. I think you will find that you and your team will be miles ahead if you take this approach.
Someone hasn't read Stallman's issues with (scare quotes) "the open source definition": https://opensource.org/osd-annotated

Also, what software did mpeg describe? I can't see any such reference. And if you mistakenly meant my reference to Windows/Office, well, that was meant as a hypothetical.

What term would you use for "publicly visible, but not hackable-by-license" software as opposed to "publicly not visible, and not hackable-by-license"? The former satisfies many concerns with vendor software, in that you can examine the code yourself for bugs, vulnerabilities, or backdoors.
The EFF is fighting the fight we all should be fighting.

In my opinion their letters are too forceful and not understanding of how difficult it is to enforce the law and bring justice to victims. For example, they write

> We call on the Obama Administration to heed the advice of neutral security experts, engineers, and even his own advisors who have affirmed the dangers inherent in the order issued to Apple

There's no need for Obama to change his mind here simply because experts say so. In fact, if properly explained, he could understand himself that software is ungovernable. Encryption technology is just words on paper.

Print out an encryption program and send it to your representatives. Let them see how anyone can create it for free. Let's educate our representatives. Enough with this idea that they need to be beaten over the head with a stick. They believe they are doing the job protecting public safety and the constitution. Once you give them that benefit of the doubt, then we will be able to move forward.
I think you're seriously overestimating quality of the average programmer candidate.

Someone who understands what NPM is, has written and published working code (even stupid code) is miles ahead of the curve already.

Most companies in the world, especially non-software companies, don't go for 5% hacker gurus. Attracting someone vaguely competent is already a blessing.
No reason to turn something trivial into rocket science.

You examples does not mention the type of variables involved. And dependent on the type and the language your first example may be (a lot more) correct compared to your third example. Ie. negative floating point numbers.

But who says that a library implementation is a lot better than what you as a programmer can come up with?

In particular with all these "micro" libraries written by random people.

Are they actually smarter than you? Do they understand the "edge" cases as you do?

Most people don't bother with looking at the library source code they are importing. And I don't blame them because things are in general a mess and not only for JavaScript.

The solution, for me at least, is to import less and be more conversative with what you import.
Is Apple saying anything about what they found? This is a big deal. Who put something in their servers? NSA? The PLA? Samsung? Did they have any strange chips analyzed? There are companies that can take an IC apart and see what's inside.[1][2] It's not cheap, but Apple could afford it.

[1] http://www.siliconinvestigations.com/
[2] http://www.istgroup.com/english/3_service/03_01_detail.php?M...
Maybe not Apple data centers, but it is possible to have a data center of Mac pros: http://photos.imgix.com/racking-mac-pros
Or "post-startup" or "previous startup" or "startup alum" (like YC alum)
When a corporation makes a tool, it's to do some job it needs to do. Usually features are added over time to provide for the requirements of its users and various teams. In this way, it only does what it needs to do, and is usually kept around a long time, used by everyone, and rarely replaced, because it can always be modified to fit a new feature. It ends up being pretty feature-complete and useful (which is sad because they usually end up locked up as intellectual property).

Non-corporate tools, on the other hand, are typically made by people who need to do something and want to do it their own way. It's not that they couldn't make due with an existing tool - the functionality probably existed in another tool or tools - they just want to do it differently, with some kind of interesting twist. The end result? Reinventing the wheel with maybe one new feature, and missing all the ones they didn't need/want. Do this a hundred times and you have a hundred tools that are useful to some people, but not most people.

I'm not saying it's lame, i'm saying it's a waste of engineering effort.
Engine is generally optimised for max efficiency at a cruising speed. A airliner engine is optimised for transonic cruising, you can't just half the plane and double the speed.
Fwiw, this article about 37Signals moving their iconic blog to Medium is worth a read.“Signal v. Noise moves to Medium” https://m.signalvnoise.com/signal-v-noise-moves-to-medium-c8...
Ebeling...
That's true, and I use closures sometimes. But they are a performance and readability anti-pattern, and it's often better to either pass in or bind the data you actually need.

In some sense closures are globals and globals are bad.
You bring up a good point with respect to copyright/licensing --- at what point does code stop being copyrightable and become public domain simply due to pure triviality? There are not very many sane ways to write an averaging function, and the most straightforward one (add up all the value, then divide) would probably be present in tons of other codebases.
Dumb article....customer svc is a low man on totem pole job. There is a huge demand for coders so learn how to code and make a very good living or fight all ur fellow reps for that one or two PM openings. That's how it goes in the tech world and in general. Everywhere.
Similar idea but what if you were to write your tests first and then upload them to a site that pieces together the required modules to pass them and generates an API against the modules.
Since you asked "why wouldn't he?", here's why:

I spent quite some time trying to work around the glitches, which I was helpless to do anything about. So then I spent some more time writing up a detailed problem report including screen snapshots of Chrome debugger traces showing where some of the problems were. When I didn't hear back from them, I put even more time into trying to work around the glitches, and found even more, different glitches. So then I spent even more time writing up those problems in detail and sending them in. Then I continued to wait for a reply. And waited. And waited. And so far I have never received any acknowledgement of any of my problem reports. And none of the problems have been fixed. I have much better things to do with my time than to help AngelList debug their web site, and wait for a response before finishing my profile. Now my profile is still in a half-finished inconsistent state, because I went on to more important tasks, and have never heard back from them since then.

The first problem I reported was related to inappropriate unsolicited email that Angel List sent to my former employer on my behalf without my consent, applying for a job at a company I used to work for, presumably with forged headers and first-person pronouns making it seem like it came directly from me:

I added an entry for a company I worked for, XXX, and when looking at that page, I was surprised to see a button that said “[checkbox] Sent” in their Jobs section. I did not mean apply for a job there, and I do not remember doing anything that expressed my intention to apply there — I used to work there, but I’m working somewhere else now. There does not seem to be any way to list all of the jobs that I have applied for (or that AngelList applied for on my behalf without telling me), or DELETE any applications that I may have mistakenly made. Can you please remove my application for a job at the company I used to work at, XXX, or explain to me how I can do that myself.

How am I supposed to fix the problem myself, without access to their source code and servers and databases? Don't you think the ball is in their court to reply to my bug reports, after I've spent so much time unsuccessfully trying to work around it myself and writing up and sending in bug reports?

Or are you suggesting I start my own web site from scratch to compete with AngelList, instead of spending my time reporting problems that I have with AngelList to their team who ignores me, or even spending my time on my real job that I'm trying to describe on AngelList?

Was I wrong to spend so much time trying to work around the problem and writing up bug reports, when I should have instead spent my time watching a Ruby on Rails in 10 Minutes screencast, developing my own competing web site, deploying all the infrastructure required to publish it, hiring people to maintain it, getting the money together to run it, and renting office space? Should I use AngelList to get funding for that, in spite of all its flaws? Or are you offering to fund my AngelList competitor yourself?
"Perfect" is a stretch. It was one of the better options in its release window, though.

One flaw: tough to repair (2/10 on ifixit [0]) which will be fun when the battery starts to go.

Another issue: Android Marshmallow (admittedly not Nexus-specific) doesn't play well with AdBlockPlus, and if you want AdAway or another hosts mod, you still need root. Rooting will allegedly break Android Pay, too.

[0] https://www.ifixit.com/Device/Nexus_6P
Mathematicians find a peculiar pattern in primes
A Reply from from Mike Roberts, Head of Messenger  Kik
I doubt Apple would go so far as designing a low volume server processor for their datacenters. It is probably not cost effective. Apple reusing their iDevice SoCs in microservers could work though.

The A9 has PCI Express lanes for NVMe flash that could be used to add wired networking and storage while the secure boot and code signing would allow them to build a microserver that only runs their code. This arrangement would also be incredibly cost effective for them.

They would want to give their SoCs have properly protected internal data paths and the necessary logic for ECC RAM before using them in micro-servers if those chip features are not already there though. If they are, I doubt that the ECC is being used in their iDevices.
If I remember right, this generates a number that is probably prime. :)
C didn't get a standard (or a standard library) until 1989. It had been around for 17 years at that point. Two years after its invention, JavaScript was standardized in 1997. That's almost twenty years ago.
I doubt that using their customers' audio as training data was a major motivation for offering this service.

But, assuming that was their plan, they'd have a couple options:

- Like you said, they could turn it into supervised training examples by transcribing it. I'm sure they'd at least like to transcribe some of it so that they can measure their performance. Also, while Google does have a lot of 1st party applications feeding them training data, customer data might help them fill in some gaps.

- They might also be able get some value out of it without transcribing it. Neural networks can sometimes be pre-trained in an unsupervised manner. One example would be pre-training the network as an autoencoder, which just means training it to reproduce its input as its output. This can reduce convergence time.
I believe this is what OP is referring to: https://medium.com/@azerbike/i-ve-just-liberated-my-modules-...
Google Cloud Platform Adds IAM
And when a bug is found, instead of fixing it in one place once, you now have to hope that all of your deps and all of their deps update themselves appropriately.
Coal in the USA is nearly a $50 billion industry, the vast majority of which is used for electrical energy generation. It's not something you can just shut down. If and when better economic alternatives are available, it will go away naturally.
Lol, nice, I wrote "pass-any" first. I then copied the code and replaced "or" w/ "and" to create "pass-all".

I will probably have go back and change this now that I know about it. In general though, not gonna a lie, I am not very concerned about micro performance optimizations.
This entire comment thread is such a breath of fresh air. I was beginning to think that I was that guy who was crazy for thinking that all of the people doing this were crazy. This thread is like my new support group.
I would have to look at your code, but generally if you have a long callback chain and you're trying to propagate errors up it you are doing something wrong. Are you really working on 10 nested activities simultaneously, or are you just nesting things because it's convenient and you don't want to think about how to do things in stages?

If you're trying to convince me that "callbacks become painful in situation X" you really don't need to. I know that. What I'm saying is that 9 times out of 10, the answer to the question "do we really want to be in situation X in the first place?" is "no". But instead of getting out of a bad situation by refactoring, people just write crazier and crazier control structures (i.e. promises) to make those bad situations workable.
No company is static, what will Apple look like in 10 years? What would happen with my data they recorded today should company policy take a shift?

I'm quite uneasy regardless of who holds my data.
Most people who charge $2,000/day for consulting only ever do that for a few days. Everyone seems to make more money than they really do.