skysight-inc/HackerNews huggingface dataset:
We're doing Agile, but I hesitate to call it Agile because I have nothing against the original concept and don't want to cast it in a negative light. The way we're doing it is probably the most dysfunctional system for software development I could possibly imagine.

Let me set the stage.

I'm working with 100+ other developers and probably 300+ total people on this one project. We're subdivided into 20 scrum teams of ~5 developers each.

So far so good.

The problem is that I'm working for a non-tech Fortune 25 company. The person who signs our checks and justified this project is literally six levels of management above me and reports directly to the CEO. To quantify progress and justify the cost (hundreds of millions of dollars) our project is treated as its own organization which has to satisfy a service-level agreement (SLA). This SLA contains completely arbitrary metrics like velocity, defect count, and myriad other things which are only tangentially related to software quality and execution.

This has resulted in the most ridiculous management strategy wherein everything is locally optimized rather than globally optimized. Here are some examples:

1. At the end of every three week sprint, there's a rush to complete stories because if anything is moved, management looks bad. Software engineering standards go out the window because there's literally not enough hours in the day, and nobody is willing to work overtime just to make some manager look better.

2. Speaking of poor software engineering standards, there's so much pressure to close defects immediately that the standard practice is to hotfix/patch everything rather than solve underlying issues. This has created enormous amounts of technical debt in our code base, making working on anything you haven't touched nearly impossible.

3. We're subjected to completely arbitrary pressure any time we're missing the metrics in our SLA. We're not in production or even close to it, and yet our management has had the gall to force six day work weeks across the entire project so the defect count could be brought down. Our strategy? More hotfixing/patching and pushing defects off to other teams, because when you're giving up your Saturday based on some completely imagined emergency, there isn't much incentive to do things the right way.

The end result? Extremely brittle software which satisfies acceptance criteria and has a pretty veneer, but will break the moment you sneeze on it. 200 million dollars well spent.
Humanities Data: A Necessary Contradiction
Even day traders have their capital in some instrument, be it cash, real estate, stocks etc. It's not unlikely that in addition to day trading, this trader invested a large amount of money into the stock market (and indeed, we have been told he did not invest in real estate).
Those virtual machines are certainly good, nice ones
Wow, fantastic paper:

However, the relevance of Turing model is questioned even in case of present-day computing [33] [34]. Indeed, any computing machine that follows a Turing model would be highly inefficient to simulate the activity of biological neurons and experience an increased slowdown. Since the super-Turing computing power of the brain has its origins in these ‘strong’ interactions that occur inside neurons, current models have missed the most important part. Simply, Nature doesn’t care if the N-body problem has analytical solutions [36] or can be simulated in real time on a Turing machine [37].

...

While previous models have attempted to represent Hamiltonians using Turing machines [35] the paper [1] shows that the Hamiltonian model of interaction can represent itself a far more powerful model of computation. Turing made an important step forward; however, there is no need to limit natural models of computation to Turing models. In this sense, the new framework of computation using interaction is universal in nature and provides a more general description of computation than the formal Turing model. In other words God was unaware of Turing's work and has put forward a better model for physical computation in the brain.
This is not really a problem. Some thoughts:

1. Time is never the same on two different computers.

2. Time is different when you send it and receive it (speed of light).

3. Time isn't necessarily linear (time dilation).

4. Clocks drift, even with NTP.

5. Some systems are isolated enough to accept inaccurate human input and time synchronisation.

Time is an invention for human consumption mainly. Machines are better served with explicit synchronisation (paxos, distributed transactions) or not at all (eventual consistency). Examples in brackets.

Time, if we lose a few seconds here and there, meh, don't sweat it.
iOS version of Popcorn-Time.se loads this plain website
The actual paper is actually way more interesting, with lots of examples of conversations: http://arxiv.org/pdf/1506.05869v2.pdf
If all occurrences of "this is [magic]" are treated as "this is [sufficiently complicated internally and beyond the scope of this post]," then what's the difference? The former makes for a point that's expressed more succinctly and eloquently at little real loss.
>The point of the criminal justice system is to manage that instinct in a large population.

Mostly in places with "old testament" attitudes towards morality. For contrast consider cells and prison quality in a place like Norway or Sweden for example (including prison time), compared to the US or some place in Latin America...

There have been many philosophical justifications by judicial philosophers and political experts on justice systems in various countries, and deterrence and rehabilitation are more often than not the stated goals.
What is a good Sharpe ratio?
between .7-1.2 mg now it's going down to .7 mg.
Foreachline: Do something for each line of a file with JavaScript
Except issues :(
Node.js Interview with Shubhra Kar
I've always thought that open source or freemium was an equalizer to get found by potential users on the net. If you lack the capital and/or marketing chops it's a valid alternative.

It hasn't been said but I suspect it wouldn't work nearly as well for a consumer product than it would for something targeting businesses.
Lithium works well for my symptoms but I do not tolerate it. When I learned that it only reduces hospitalizations by half I stopped taking. I did just fine for six years but became psychotic in graduate school.

Since then Ive taken valproate which works well and so far I tolerate well. However there is significant risk to my liver. I take regular blood tests to watch for that.

Lately Ive been feeling physically ill, as if I have been poisoned. I dont know the cause but will request a liver function test this week.
OCR please.
This is my understanding too. Basically losing more often than winning on your bets.
I live in Salmon Creek but often come to Portland.

mdcrawford@gmail.com

http://www.warplif.com/mdc/books/schizoaffective-disorder/
The module tag is not es6, not even worked on by the same standards body. Futhermore, while there is consensus that a module tag would be nice, no one is actively working on it. So don't depend on it in this context.
The facts point squarely in one direction, as far as I can tell. Profitable SaaS companies are proprietary. Where are the billion dollar open source SaaS companies? I don't see them. Maybe the big companies occasionally release a component on github to get some goodwill, but nothing big.

It's only when you go all the way down to the "lifestyle" sized companies that I see real dedication to the open source ideals. They're willing to put their entire product on github. Props to those founders, but it's pretty insignificant because those businesses are so small.

Most people don't have the skills to run their own servers, and nor can we expect them to. Service based products are the future, but I hope that interoperability gets to the point where customers can switch painlessly between different providers. That would put a lot of leverage back in the hands of the end user. If I had to name one problem it would be lock-in, not proprietary code.
Disappointing that the observations from article (which is from 2010) still apply, and appear to be even worse.
But still there are differences for example in tax rebates between, married, pacs and none of the above couples.
All GoLang Books Have Been Published
How is SMS offline? If Duo isn't there, where is the SMS coming from?
A 100-Year Debate About the Eardrum Comes to an End
In the early days of internet commercialization I thought issuing trusted certificates would ideally be provided by banks. Money transfers are all about trust and securing information, it seemed like a perfect fit. You get a smart card from your bank that holds their root certificates and pop that into any computer to authenticate an email or website. It also holds your private keys for authenticating yourself to others for online banking, voting, etc.

Of course I've since learned how awfully inertial the banking industry is and that the security of financial transactions is a lot of hand-waving and wishful thinking. On top of that, there's outright corruption of banks profiting from theft and always cooperate with governments.

So the answer is, you shouldn't have to trust anyone. The security infrastructure must be built assuming hostilities are everywhere. Any trust that is given should be limited to just what is necessary to accomplish the task at hand.
Contradictory signals in your rationale here. It comes off as if you're filling in a post-hoc justification.

Is it just an archive or isn't it? If it is, what's so important about the community, then?

It's fine that you chose what you did, of course. It's just that that in your defending it, you can't seem to decide whether you want to have your cake or eat it.

If you wanted, this would have been a perfectly fine reason to give: "We went with GitHub because it's just what we use mostly, and other stuff not so much."
For now, it's an implementation detail (rather than specced) as to how homeservers persist their state. The synapse implementation stores all data unencrypted in sqlite or postgres - /however/ that data may be end-to-end encrypted (we are releasing our e2e support over the course of this week - the first bit of the puzzle can be seen at http://github.com/matrix-org/olm). We should probably store all data AESed in the db to avoid casual snooping too.

This doesn't obfuscate metadata like room membership or profile data however; but fixing this is Hard. For now it's just a fact of life that Matrix servers have visibility on communication metadata - i.e. the identities of who talks to who, and when, and with what kind of event. In future we may support better privacy preserving semantics by evolving the federation architecture: eg running homeservers on clients and using Pond-style hidden Tor services for message transport, or layering on GNUnet as a transport. We've tried to design Matrix to support this sort of evolution, but right now today Matrix provides the same level of metadata privacy ss (say) an IMAP or SMTP server.
Why people buy? The truth about buying behavior and advertising that sells
Face it, your brain is a computer
> open p2p software that all coders get to archive their own full copy of github's repos

Do you mean git?
Case in point which tripped me up recently. Knowing that promise.then() callbacks aren't called synchronously[1], even if the promise is already resolved, I assumed that this:

var tick = Promise.resolve();
async function cpuBoundJob() {
for (...many iterations...) {
// crunch some bits
await tick;
}
}

...would spread out a heavy calculation and allow other things to break in occasionally and do work. But based on tests, nothing ever got a chance to run until the whole job finished.

My current understanding (correct me if I'm wrong) is that promise.then() calls you back from a microtask, which means "await tick" doesn't teleport you into the next tick, just out of the current call stack into a new one at the end of the same tick, regardless of how many things are piled up waiting on the next tick. In other words the entire calculation remains one big CPU-blocking chunk. This modified version ended up working as expected, since setImmediate is (apparently) not a microtask.

var tick = () => new Promise(res => setImmediate(res))
async function cpuBoundJob() {
for (...many iterations...) {
// crunch some bits
await tick();
}
}

[1] https://promisesaplus.com/#point-34
previous: https://news.ycombinator.com/item?id=439298
I left in 2010 so I was thinking the same thing. Folks who have since gone to Google have mentioned that they have added counseling for folks which could help. And as I pointed out to some folks while leaving, the people who care about these sorts of issues will leave, new people will be hired and the ones who stay won't care about those issues, and so you will have successfully evolved the culture/environment away from something the company was no longer interested in providing. As far as I can tell it hasn't killed their ability to hire new employees so the net effect is all positive for Google.
When you get the hype, for example front page of HN, that would probably be a good indicator that it should be possible to make a living on it. It doesn't even have to be your own project :P

There are excellent comments in this thread btw. I've bookmarked it.
Show HN: Phishing as a service
Also in a recession a lot of trades slow down dramatically, because firms will be conservative. If not a lot of trades are happening, there isn't much to make money on. In addition to this, the strategies that the day traders relied on don't work as well, since the signals will change as people start trading differently.
The whole point is that everything's changed. These people are griping about lack of free food in the office, bad pay and lousy benefits. They also complain that Google is "constrained to thinking in the browser." Too bad they didn't stick it out to see the self-driving cars, and none of these people were working on Android.
This is an awesome survey. I am a avid fan of Django and have been using it for over 4 years.

I found it amusing people are split between 6 and 12 month for release cycles.
What I'm wondering about is that they mention long hiring process as a reason for quitting the job. They finally made it to the end and they quit because of that?
Engineers Break the Capacity Limit for Fiber Optic Transmissions
Phishing
Can you spot the difference?
http://IIoydsbank.co.uk
http://lloydsbank.co.uk
They can be professional all they like but if they only have money as a motivator to work at a place they hate then they'll just be poor performers. They won't have the energy to do more than the bare minimum. Motivation is just not something that you can command at will.
The browsing experience on my quad core MBP is slower than on the 300 MHz PII I had in 1998 (on a 256k DSL connection) and isn't one bit better for all the bling. I actually feel pangs of bitterness when I see websites in 1990's movies. Just text and images like God intended.

At some point, the eye rapists took over all media. TV, movies, the web. Everything is more in your face and terrible than it was 20 years ago.
There is no escape from military service here... he will have to serve after he comes out from jail.
Apparently I am not "culturally fit" for this "inclusive and tolerant" community or an HN material in general which should be a good news in and of itself if you ask me.
"We needed to become more agile, so we lost weight by cutting off our arms and legs."
...or one could resort to the implied risk at Greek government bonds. A bond which matures in November next year trades at about 60% of the value you will (or wont) receive at that date. In other words the odds are roughly 2:3 that Greece defaults until then.

http://www.finanzen.net/anleihen/191049-Griechenland-Anleihe
Why buying advertising is so frustrating
I went and looked in the Oxford English Dictionary and did not find your definition of magic there. http://www.oed.com/search?searchType=dictionary&q=magic&_sea...
So we have an FAQ link which amounts to "too many clients have bugs around spaces in passwords". I'm not as certain that this is true as it was when we instituted that rule, but it definitely was at the time.

As for the autogenerated password thing. You might have followed that Google are making it more and more difficult to "just use your very secure password everywhere" as well, because they find that it leads to a higher account compromise rate than per-device password or oauth. We also see a higher account compromise rate than we would like, and so we have to design our processes to be robust against human error and phishing.

What we might do for the zero point something percent of users like you is offer a way to re-enable password based login for clients (just like Google do) after you read a warning pointing out the security downsides of not having selective revokability and guarnteed non-password-reuse of device passwords.
Curious, have you used pass on Windows or Android? I'm thinking about getting a YubiKey Neo and switching from KeePass to pass since then I can use a second factor as my GPG key.
Thus new release cycle will be 8 months, middle ground.

There are few other changes for release, notably SemVer adoption. For detailed Roadmap, see https://www.djangoproject.com/weblog/2015/jun/25/roadmap/
This is so damn cool. It's humbling to realize the scale of the universe we exist in, and how small a part of it we really are. And we're flinging probes around the solar system, millions of miles away, to learn more about our universe.

These are machines that still work, decades after they're launched on top of the most powerful (and most violent) form of transportation we've created, and after they travel millions of miles through the extremes that space provides. It's awe inspiring that we can accomplish things like that, and it's incredibly disappointing that more people don't realize the scale of what is being accomplished.
My Time at Tox
I'd love to see a simulation of particles moving around the Pluto Charon system. I've always wondered how they behave near the barycenter.

Here's some clues about what could cause the variety:

https://blogs.nasa.gov/mission-ames/2013/07/25/playing-marbl...
How to compile C apps with musl and Clang
https://news.ycombinator.com/item?id=9790964
This was linked in the article, but should anyone pass over it/not click through, here is a regularly updated list of new pictures from the probe as it gets closer: http://pluto.jhuapl.edu/soc/Pluto-Encounter/index.php

I've been checking in every few weeks and it's been fun to see it slowly getting clearer and larger. I recall watching shows about it on the Science Channel when I was in high school and thinking 9.5 years would be so far away. Feels odd that we're now only a few weeks away from it finally reaching Pluto.
It wasn't that long ago the Brendan Eich was still hostile to Dart [https://news.ycombinator.com/item?id=9266599] but now he seems to have softened.

"Ideally we’ll get things in JavaScript like big integers/bignums that Dart has that JavaScript doesn’t yet"

Historically, Mr. Eich has been critical of Dart, and if you follow that thread above he has nothing good to say about Dart, so this is a change, probably brought on by the everyone concluding that the Dart VM has no future in browsers and therefore is not a threat to Javascript.

Dart (dartlang) has a lot of nice features, is easy to work with and can increase productivity greatly in some cases. Dart still has a future if they improve the Javascript output as this project is attempting:[https://github.com/dart-lang/dev_compiler]

I'm glad Mr. Eich has opened his mind to some of the good things in Dart.
> Deadline-driven development? At least for security, that sounds like a dangerous approach.

This is a valid opinion, but management better be privy to these discussions. I've interacted with technical teams who believe their technical opinions and decisions were completely not the business of the people who were signing their checks. Actually, even a subset of management being privy to the conversations isn't always enough - unless there's a good reason, I'd advocate for the details of conversations and especially differences of opinions to be publicly available to most anyone within an organization.
Now we have SSD which means a small one-step-backward for storage. However, we will supposedly have 10TB SSD and beyond within a couple of years which should give some breathing room.

Even with all this development, I doubt we will be able to have everything on Github locally on our computers. I imagine the typical Github project to be tiny -- probably tens of megabytes at the most so I'd say we can have all the projects that we care about available locally. One can only care about so much.
Machines are better served with explicit synchronisation (paxos, distributed transactions) or not at all (eventual consistency)

Using atomic clocks to sync distributed systems is actually done in practice.

http://static.googleusercontent.com/media/research.google.co...
Unfold London – The Smart Way to Shop-  Summer White Edit for Men
Thanks for mentioning me. I'm happy to answer questions.

You're absolutely right though: your project is only as valuable as the problem you are solving. When someone told me early on that switching from Resque to Sidekiq was saving them $3000/month, I knew that there was a business here.
Why didn't your company publish their data. If day 3 biopsy is better and you have the data to show it get it out. This is not some meaningless result - this is a matter of life and death.
the Lisp Koans, Exercism, and 99 Lisp problems look especially good for FP concepts (and the first two are more modern than I had expected). Thanks!
It's already been OCRed. Just Ctrl-A, Ctrl-C, flip to a text editor, Ctrl-V.
> The people who know what they're talking about say it once, coherently and concisely.

In my opinion this generalization is only sometimes correct, I have been a personal witness (and participant) in many cases where it most definitely does not hold true.
This is such an exiting period! New Horizons about to reach pluto, Dawn about to reach Ceres, and Rosetta orbiting a comet approaching the sun.
I know you can.

The point is that it's fantasy to think we can ALL reasonably buy an Italian bicycle, right now, even though demand may be great.

So instead we believe the myth of the Italian Bicycle For All by buying one with an Italian name, and perhaps with a sticker that says, "Fatto in Italia". The large Italian bicycle manufacturers may eve want to produce an all-Italian bike, but they can't - perhaps the technology they need isn't in their possession, or the techniques needed don't work scale well

It could even be a really good bicycle! But part of what I'm buying into is the myth that it's a really good, Italian Bicycle. For some reason, this is important to us humans, and we'll pay a premium even though the bicycle is made in the same factory, by the same workers as a bicycle that has labels from a domestic company.

So this, "Icelandic Yogurt" is just more marketable then calling it, "Icelandic-style Yogurt".

It's not a rare thing. Look in the ice cream isle for "Ice Cream", as well as "Frozen Dairy Dessert"[0]. Which one sounds better to you?

[0] http://consumerist.com/2012/09/11/new-breyers-recipes-when-i...
Just because the CEO is gay then SO support this. So ridiculous.
This is really interesting from a community point of view. Embarrassingly I didn't hear about the survey and thus didn't submit responses. Lots to learn from the answers though.

Does the Rails community do a similar survey?
You assume correctly.

Any service, especially served abroad like in the US, where I share any of my data, I no longer feel as good about using.
What the author is trying to say is that this label is deeply ingrained into our cultural stereotypes but we should strive try to change the situation.