skysight-inc/HackerNews huggingface dataset:
A lot of funny stories about how that piece of consumer software exists in the world today. About 5 different parties involved, some who are 100% competitors (V vs. MC). 16 or so years ago, MC bought a company called Orbiscom that provides what Citi & BoA use for vCards. Its a layer at the network to provide these mappings and so when BoA issues a Visa card, and you request a virtual card, you're making a call out to a MC service to generate them on a Visa BIN.

None of this even addresses or ties who BoA uses as their core processor for CC, which is now TSYS, and typically have little knowledge a vCard was used.

The good thing for what we're doing at Final is that this goes beyond many credit card numbers, its rethinking what is a piece of plastic in hundreds of millions consumers pockets for how we shop and interact w/ merchants in this day and age.
Kerckhoffs's principle
Since there's a possibility people will try this, the linked article states that the benefits usually only last until the patient falls asleep. This isn't a practical treatment strategy right now, although it is interesting scientifically. If you have depression I'd urge you to take the advice of a medical professional rather than attempting to self-treat.
The study is about the effects of "test first" vs "test later", not "writing tests" vs "not having tests".
We had our logo stolen, so we're letting the world know
I'm sure I don't have to tell you after that loss, but of course offline data doesn't render backups obsolete.
And thus terrorists win long term. Not by actually achieving what they want, but by paralysing their enemy and affecting them negatively.

One would think people in "the land of the free" wouldn't act like either scared rabbits or enraged bull.
To the eye of a developer used to more modern languages that also shows some bad choices in the design of the Erlang syntax. Basically everything that makes the source code less readable than the original: uppercased variables, the minuses that prefix the module and export statements, the wierd =:= operator. I add the also wierd <> binary and string concatenation operator, not used in this example.

The semicolon-period statement separators/terminators are in the original and in natural languages, but newer languages proved them to be useless. Probably compilers in the 80s needed some help by the programmer to be fast.

Elixir fixed some of the worst offenders, kept others and added something. Examples: the <> is still there but at least we can interpolate strings Ruby like, the useless do at the end of almost every defsomething declarations (the compiler should get it by itself.)

But every languages has its wierdnesses, the contest is to have the least of them.
Clean (programming language) – Wikipedia
I think the profusion of use-after-free bugs and memory leaks in C code running all over the place should put the lie to this. And, further, modern C++ allows you to firewall off the damage of bad C++ and most C, when you are forced to interact with it, via unique_ptr and your own enforced RAII. (And the idea that using this is so pejoratively "shackling" is bonkers to me; being "shackled" to the use of railings on walkways over a pit of fulminating acid is just the worst.)

The idea that people use C "sanely" more often than C++ (or, you know, something actually good--further shouts, Rust!) doesn't pass the smell test. Are you checking the retval of every sprintf? Are you writing goto drops in every method where there's allocated memory, diligently checking every error code, and properly bailing out, every time? If so, you're that one percent. But you're probably not. And that's not a slight--I'm not, either. That's why I am proud to count myself as a member of a tool-using species, because we build (and have built) better tools to compensate for our flaws.
> the great majority of HN discussions start with a comment like this one: It's seriously flawed, etc.

That's easily the best part of HN and reddit. A great help with the Murray Gell-Mann Amnesia effect.

I don't think it's that HN is negative (though HN can certainly be negative), I think most articles really are just kinda crummy. Could be oversimplified, probably overhyped, maybe some wildly skewed sense of "providing both sides", or one of a million other possible problems. The comments will tell you about these problems, and that makes them a better barometer of "is this worth it?" than the title or even the content.
How does it compare to RAML? http://raml.org/
Criticism to the study goes both ways. It COULD be that with a larger sample size, more meaningful project and more experienced developers the result would be "TDD actively hampers productivity by 70% and leads to more bugs compared to test-last".

Being mindful of the conditions of the study is important. Shrugging it off isn't helpful in the least.
I'm pretty sure many more people find TAOCP confusing than they do Erlang :p
Email aaron@getfinal.com.

And not sure why someone reposted our website, but always happy to discuss the intricacies of human behavior and how it relates to payments.
While I can see your point of view, perhaps that is an ideal and not a realistic view of how science actually works. Similarly, someone might have an ideal view of software development, but if they saw how it actually worked and read actual in-production code ... and I think that describes every profession.

Science does work pretty well; it predicts things with accuracy and reliability otherwise unknown by humanity (AFAIK). It's an interesting question: If not by hewing close to this ideal, how does it actually achieve results?
As a TDD advocate, and assuming this study has any scientific validity, this is actually good news! There's a very common claim that TDD makes you less productive. It's good to have some study to oppose this claim.
I'm a professional and you can take the lambdas out of my cold, dead hands.

Also, their examples are removed from reality. I've never seen people use lambdas like that. Most of the use cases I've seen are callbacks that get triggered on certain events (i.e. "display notification when background loading thread completes") and predicates (i.e. find_if). I see neither in their examples.
Context for the remainder so you can know they aren't cherry-picked and your reading of whatever you get out of any of them is through your own bias alone and not Assange's, the NYT editorial team's or whoever else. You only need to trust that Assange will publish you don't have to care what he thinks about anything else.
Perhaps oddly, it turns out that presenting no data is better than presenting data with poor foundation. Comments like this get upvoted because many of us appreciate someone pointing out when there's no "there" there before we've spent our own time reading.
I used to hold the same opinion as you, but I've recently changed my opinion of firehol; it's a little higher level than ufw and friends, and highly encourages good practices which are easy to forget or get wrong if you iptables all the way.

I've realised that when I noticed that the comments I wrote for others on my iptable configs were comparable in length and content to firehol (but not verifiable or executable). Unlike ufw, firehol actually saved me significant time and effort even though I know (and use) iptables directly.
Modernization is an obvious benefit to banks. Anyone who's been in this industry talks about how many banks traditionally do not have good infrastructure or are ultimately buy everything remotely.

Capital One is changing that, we're building a lot of our own stuff. It's not an overnight process, but the results are pretty amazing internally and I hope it'll become more obvious externally soon.
What? No comments? This stuff is amazing.
Fair enough. As the comment below points out, more likely she had in mind the idea of personally ruining him, as she has tried to do (and partially succeeded) to at least one other person in the past.
Can we say: "If you understand the first 20 pages of TAOCP, you understand Erlang"?
I understand that, I just don't agree with it.

How many of us would want to have everything we've ever said or done in private aired out in public, under the guise that "the public is smart enough to not editorialize anything"?

I'm quite certain that would have disastrous consequences on my life, as well as just about anyone else's. How about yours?

That said, when it comes to something affecting the public interest (eg government corruption), then yes, I am all for airing such matters. Transparent government is good. Transparent "what kind of porn does Joe Public watch at home?" is not.
I think this may be the first list ever to contain Santa Sangre and Jurassic Park. Well done.
Knuth's function would be written in Haskell as thus:

f [n] = [n]

f [m, n] = [m, n, 0, 1]

f [m, n, r, 1] = [m, n, mod m n, 2]

f [m, n, r, 2] = if r == 0 then [n] else [m, n, r, 3]

f [m, n, p, 3] = [n, p, p, 1]

It needs to be implemented with variable-length lists instead of fixed-length tuples, in order to satisfy the type system.
It English subtitling on an movie in English, as they often have at bars.
Hm... thanks for the head's up. I thought that SQLITE_CONSTRAINT would detect both read and write conflicts, but I'll dig deeper there.

As for how much contention there will be, I'm not sure: that's one reason we haven't taken the plunge yet as we sorta want to determine this first. However, given that we have a huge number of users modifying unshared data (eg, our largest group still makes up a tiny fraction of the userbase), I suspect conflicts will be relatively few.

And to be clear: even a little write concurrency goes a long way. If we can even do two writes simultaneously, that doubles our write performance. But I personally suspect the average batch size of non-conflicting transactions will be in the dozens or even hundreds -- meaning I suspect we will achieve so much replication throughput that something else becomes the bottleneck before replication is saturated.

Only one way to find out however!
https://news.ycombinator.com/item?id=9588304

"Remember that Netflix does not typically offer bonuses, stock grants, etc, and just pays people a salary."
What was your favorite dial-up modem?
Nigeria’s Social Media Bill Is Back
Lol. Thay got dank infrastructure. Web 2.0 all the way.
> The whole point of careful statistics and well-designed experiments is so that we can learn whether a premise is true or not.

That's where you're wrong... even with "careful statistics", the point of sample-based studies is to disprove the null hypothesis with some confidence level. There is no requirement that it be 100% confident. In fact, with p<0.05, you might expect some small fraction of repeat experiments to show no significant effect.

(See, it's easy to get this wrong!)
Freelancing questions
I have been working in the same company cor 5+ years, and I have not been doing a lot of cool stuff for the last years. I'm an experienced PHP developer , but I do have learned lots of stuff on my own though.

I am from Mexico, and the job market place is very difficult for developers so switching jobs it's hard, at least for me. For the last 5+ several years I've been under earning, and I have always been spending more than I earn because I negotiated very poorly my first salary (I was straight out of college). I've tried to negotiate my salary several times, but the increments have been very small to make a real difference at the end of the month.

I need extra cash to stay a float, and I'm willing to do freelancing but:
a) Most jobs require full time
b) Most jobs are not long term at all and not stable, and some can even not pay you.
c) Many freelancing sites have hundreds of bidders (some automated), that it's very hard for me to land anything.

Do you have any tips or suggestions of what I can do to stay afloat?
Any tips for freelancing? Or any part-time remote job site?

Any comment would be very helpful.
In my experience, some people are too much attached to that good feeling of knowing "all there is to know" about something; this has the taste of proficiency, but the very real risk is to prefer the small pond because of that, calling the sea "overextended".
uhm. lol? are you saying a study can't be criticised by anything less than a counter study?
If your code doesn't have tests then you can't refactor because you don't know if you broke something. Getting the right level of tests is important, they should check the interface and not the implementation, otherwise I agree, you can't refactor anything. But if you test your interfaces the same way that real code would use it then it actually makes you more agile, because it gives you the peace of mind to do major changes.
You're correct that SI with a single writer will always be serializable.

(I was one of the authors of SSI in Postgres)
It's hard to draw the line though: "needy Latinos", that environmentalists should "get a life", the sneering comments about Catholics, the constant chummy relations with the media and a reporter leaking info "because I have become a hack"? The insults towards various specific activists and groups, a D-list "journalist" like Budowsky openly saying he'd trojan horse the Bernie supporters?

Could this have been done better? Perhaps. We don't know the details of when Assange got this information, what opportunities he might have had to filter it through MSM outlets with the resources to handle it and release it before voting (which has already begun).

The fact is, quite a lot in there is in the public interest to know, and especially for someone like Tanden I have little sympathy for her shit-talking being made public, after she's attacked others for less.
Yeah, the buyin is deep. What we're doing there is actually the publicized versions of our new internal process.
After realizing the posts were marked as dead automatically due to flags, I take this back.
How do you propose to gather more experienced, professional developers into the same location and get them to work on a topic that isn't making them tons of money? They can't be left to do the problems in their own workplace, or the next criticism will be "uncontrolled variables!". They also have to be vetted for minimum skills (there are plenty of experienced, professional devs out there who aren't worth a second look). The parent also wants more complex tasks done.

So... where is the money coming from? Who is going to pay for this multitude of professional programmers to converge to the same environment, be vetted, and spend a non-trivial amount of time coding the same thing as the others in the group?

Of course the researchers in the article would have loved to have those kind of resources and do the perfect, wide-ranging, deeply detailed study, but the OP's criticisms just show how divorced the OP is from experimenting with real-world humans in real-world situations, and with real-world resources.
SSRI drugs (sold as 'anti-depressants') have always been known to cause suicide ideation... While they do seem to help some people, it is now known that this is because of the drugs' effects on the neurosteroids [1], NOT because of 'increased serotonin'. Anti-serotonin drugs (LSD, various MAOIs, etc) are much more effective anti-depressants.

[1] https://en.wikipedia.org/wiki/Neuroactive_steroid#Role_in_an...

There are some good articles in the Boston Globe's archives about Prozac, circa 2000. "Prozac, Revisited", etc [2]. Robert Whitaker [3] worked for the Boston Globe, before he wrote Mad in America and Anatomy of an Epidemic.

[2] http://www.narpa.org/prozac.revisited.htm (the boston globe's official archives site is not so easy to use, but I've previously verified that these stories exist)

[3] https://www.madinamerica.com/robert-whitaker-new/

The first patient in this BBC article could also have been diagnosed as 'exhausted':

> She had begun taking [SSRIs] while caring for her seriously ill mother and studying for her final exams at Cambridge University, but suffered severe side-effects after her GP prescribed a stronger dose of tablet. (emphasis added)

I think 'exhaustion' is a frequent cause behind the symptoms labeled "depression".

In May of this year, I watched Lexapro (an SSRI) destroy all the progress I'd made with my girlfriend... She'd asked for this drug a month after she'd escaped from her court-ordered tranquilization, because she thought it had helped her years ago. Really it just helped her relapse on cocaine then. This time it caused rapid heartbeat, and much anxiety. Her last benzodiazepine turned her into an anxious wreck... The psychiatrists got hold of her again, and they're making sure that she will never recover.

About a week ago I went through videos on my phone... and found one of my girlfriend about a week before she was taken to the hospital. The video proves, beyond any doubt, that she is not "persistently" disabled, that the symptoms that originally put her in the hospital were entirely due to quitting her addictions cold-turkey, and not due to 'defective genes' or other pseudo-scientific rationalization for forcing her to use palliative drugs.
Apple Gets Ready to End Mac Update Drought
The comments to that story are pretty good.

An interesting question is: why does TDD fail in such experiments (it does so unexpectedly consistently), even when many developers feel it has benefits when they practice it?

There is no silver bullet, so there must be circumstances in which TDD does not work. And conversely, the central question is: under what circumstances does TDD work? What are the preconditions?
Ubuntu vulnerability list:
https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2...

(TL;DR: Ubuntu 16.10 (Yakkety Yak) is listed as "needs triage", no other releases are affected (14.04/16.04/etc))
OK, I had not realized this. Thanks.
> There's definitely evidence that heavily implicates Russia.

No one has shown any evidence. The US government just claims that Russia did this just as it claimed that Iraq had WMD's. Please show us the evidence that you have found.
For me what's striking about Erlang syntax is the meaning of the semi-colon and the period, as function clause separator. Most of the rest is just vanilla FP lang syntax.
One thing I don't like about Elixir is the Ruby-style "optional" sytax e.g. `IO.puts "hello"` vs `IO.puts("hello")` and the whole keyword list arguments syntax sugar thing. I mean, I get it now, but it's sorta hard to read as non-Ruby beginner.
It's called pattern matching, and is present in most functional languages - Haskell is a good example of something which uses this style extensively.

In a sense it's derived from the way that some mathematical functions are expressed, e.g. i've seen the fibonacci sequence expressed in this manner a few times.

The only thing this excerpt from the book has to do with Erlang is that they both used the same (existing) idea.
Of course students had problems—-it's one more damn thing for them to learn about C++, likely from professors that don't know it very well either. But <algorithm> is way more useful these days, and boost::asio is a dream.
> In a graduate-level engineering class, the students were making similar statements about all the studies we read

Yeah, that's because they are all terrible.
Disregarding cost (haha) is OpenStack actually attractive to use? I was under the impression it was a bit of a bear to deploy and operate (my previous employer gave up, though I strongly suspect the project was never resourced properly in the first place).
> When you split your libraries into separate projects, you have to start versioning them.

Or you can have your tooling use the convenient built-in versioning provided by the VCS. It's not called a "version control system" for nothing.

> And every update to the code requires other teams to then update their library/app to use the new version, and apps depending on that dependency... you get my drift.

This happens regardless of whether the codebase is organized as a monorepo or not. I've been subjected to monorepos at my previous and current employers, and we run into difficulties with this all the time. At least once a quarter, I get an e-mail from someone telling me that they updated such-and-such, and now the build fails in one of my projects. So I have to sit there and figure out wth they changed, why it's causing my code to fail the build, and how to fix it. Only once was the problem actually in my code (my Makefile, actually, which failed to bind some variable that was expected by the build system but wasn't documented anywhere, and of course the build system spits out a worthless error message, but I digress).

> You end up with a complicated dependency headache which hurts productivity.

Again, monorepos aren't immune from this, nor do polyrepos inherently suffer from it.

> With a monorepo, you can statically identify all places where your library is used and update those automatically with tooling, or manually. You can also monitor where and how a piece of code is used across the company, etc.

There is literally nothing preventing this from being doable with a polyrepo. In the case of updates, you may need to have the updated repos checked out, but it's not like you can only ever have one repo checked out at a time.

> If you then ensure that only commits get accepted that pass the relevant tests, you end up with a sane and working HEAD that's always up to date.

I've never worked anywhere on any project that disallowed commits that didn't pass the tests. It's typically been up to the committer to ensure that what they commit is acceptable. Furthermore, while my employers thus far have all been customers of AccuRev or Perforce (whose only real feature beyond what Subversion offers is that they cost lots of money), and have not personally had the pleasure of working with a DVCS at my day job, this workflow of "allow only test-passing commits" is wholly contrary to the "many small commits in quick succession" workflow afforded by DVCSs, which I contend is one of the biggest productivity boosts afforded by DVCSs (along with cheap branches and network unnecessity) and one of their main draws. And even so, it's still rather easy to maintain a sane and working HEAD with a DVCS (thanks to the cheap branches if nothing else).

If you find that you can't do anything you've listed here without a monorepo, that's a tooling issue rather than an organizational one. Frankly, I've never seen a large monorepo I felt was justified. Every single one was just baggage held over from a time long past when a single repo still made sense for the codebase.
Some thoughts from someone who's been prescribed anti depressants in adolescence but never took them because I believed the doctor misdiagnosed:

* Do these drugs genuinely help or is it just a strong placebo response?

* If the anecdotal evidence increases the odds from 1 in 100 to 1 in 4, would this be considered normal in medicine?

Of course the symptoms could be attributed to the wrong thing here but they sound pretty horrific. My initial reaction was that in the future we'll look back at these drugs as barbaric, similar to how we view lobotomies today.

Edit: formatting
Life is so much easier with Modern Life Hack