skysight-inc/HackerNews huggingface dataset:
I appreciate falsiness in python as well (especially for None, [], {}, set([]))... Interestingly I think zero is arguably the most dubious of the falsies (not that I'd recommend changing it, for obvious backward compatibility pain), but I can remember being burned by bugs from zero evaluating False a number of times, yet I can't once remember being burned by any of the other values I listed burning me.

I do hope the ticket in question is reconsidered though. Midnight is obviously a "valid and populous instance" that shouldn't evaluate False.
Fixed Indexed and Hybrid Annuities
Results wise, "Find all references" should show you a flattened list of the hierarchy that you see with show dependencies. Also, the idea was to make it keyboard friendly.

Quick Info might potentially involve to show more information (definition, references etc). If not, and if nobody sees value in it, I might take it out.
SEEKING WORK - Remote / Amsterdam, NL

Rails developer with a focus on interaction.

I mostly do Ruby (with or without Rails). Experience with MySQL/Postgres, Javascript, HTML5/CSS/Javascript (and frameworks like Backbone, Ember, etc), Redis, Heroku/VPS, iOS development (Objective-C/Cocoa).

If you have a project in either Node of Clojure, I'm willing to work for a reduced rate, as I'm looking to gain experience points in those platforms.

Contact: tijmen at gmail com
absolutely nothing on the future of the public api.
BBC3 to become online-only channel
This seems like a problem that only manifests in environments with heavyweight concurrency primitives: threads, processes, etc.

If you're going to hit this kind of problem often, I'd suggest using a language with better concurrency primitives, either actors (Erlang/Akka in Scala) or a reactor (node.js).

Granted, it's often not up to a late-stage maintainer which language was used, but the state of the art in language design is giving us much more power to deal with the kind of problems this "design pattern" solves.
+1 for Reporter, but also Narrative, for the automated photo part.
You don't choose your inspiration moment. Rather, it chooses you (ref: http://blog.germ.io/how-to-get-from-ideas-to-execution/).
Our man had to get out of his problem and think about something totally different to get inspired by an elevator. Think he hasn't seen a missed elevator before? I bet he has. But he had to distract himself from the problem to let the hidden machines in his head get to work.. It's the same reason Archimedes "decided" to go to a bath when his life was on the line. I don't think he was looking for just soapy relaxation there..

Deep down, we all have our little temples.

"If Archimedes went looking for a towel first, you'd have never had a submarine" - qvikr
I'm back in Java-land these days, which is culturally very pro-unit testing. After getting exposed to it again for a few months again I've come to side with the author here. I've never really been comfortable with the amount of time certain people dedicate to unit testing, especially the TDD crowd, but in my hiatus something has arisen in popularity which has made it all the worse: mockito.

Prior to mockito, unit testing was (more or less) limited to testing that your methods behaved as expected, and would occasionally expose NullPointerExceptions or other exceptional conditions. Dependent objects were either simplified or simply ignored. With the rise of mock object frameworks, however, your tests specifically say "this method on this mock will be called X number of times, with this result". Mind you, this is all happening in the context of another method call. So, for example, if you were testing the method "calculateDueDate", and that method took a DateTime object, your test might look like this:

@Before
public void setup() {
MyClass myClass = new MyClass();
DateTime mockDateTime = mock(DateTime.class);
}

@Test
public void specificDueDateShouldBeTenDaysFromNow() {
DateTime result = myClass.calculateDueDate(mockDateTime);
verify(mockDateTime, times(2)).getHour(); // contrived
}

The problem with this is that the tests become obstacles in the way of refactoring the code. Should you decide that you don't want to use the DateTime library any longer you will have to not just change the code which is using it but the tests as well. Or what if, going back to the example above, you decided not to use the getHour() method any more? Every test referencing that will have to be changed. And changing those tests is very likely to be more involved than changing the code under test, because there frequently are more tests than code. This has a negative impact on the design of the application. Because companies rarely dedicate resources to making existing software better purely for its own sake, you tend to have to do what you can when you can. This means your time is limited to make that refactor, or upgrade that library, or do whatevever change it is that needs to be done. Unit tests, especially those that use mocks, can get in the way of this to such an extent as to make such efforts impossible.

I think testing is important. I do not, however, share the belief that is the sole, or even primary, determinant of code quality. In fact, an over reliance on unit testing can easily be a net negative. Should unit tests be thrown out? No. Baby with the bathwater and all that. But they should not be viewed as a silver bullet, either. They're not. They can help, but they can hurt.
In my opinion, the "explicit is better than implicit" mantra of Python (which I find very sensible) should immediately imply preference for the second, even in cases where the first is almost certainly not going to cause problems.

Testing for "not None" also immediately tells other devs at least something about what's going on. Example: If var is an argument to a function and you see "if var," really understanding what's going on means looking at all invocations of that function to see what's being passed in.

Further, in that scenario, it's possible that different types are being passed for that argument. While "if var" could make this work where "if var is not None" would break functionality, in my opinion, it should break. Without getting into arguments about static typing, "truthiness" allows both sloppy code and the accidental introduction of bugs that might otherwise be caught during development due to faulty logic from vague conditional checks.
i.e., it could be explained better (or for some, 'explained period')
First sentence of the linked piece:

> “People who eat diets rich in animal protein carry similar cancer risk to those who smoke 20 cigarettes each day,” reports The Daily Telegraph.
Creeping semi-booleans make me very uncomfortable. But what's the alternative? A-values and I-values? A "μ" for questions unanswerable in the type system? Just punt and let Javascriptisms take over the world?
I prefer the second one.

Explicit is better than implicit.
Cool article but says virtually nothing. We have:

* A smart man, according to the article
* Who worked for the government at some point in time (according to the article)
* Who's name is Satoshi Nakamoto
* Who values privacy (so much that he used his real name LOL)

So apart from the stalking and extremely irritating privacy breach this article shows about Newsweek's[1] journalists and chosen course of action, proves or states nothing.

He didn't admit anything, but seriously... Even he did, why do we care at this point?

[1] I was holding NS in low regard anyway. Now it's as low as it gets in my eyes.
Wow that really changes the story. Putting "Bitcoin Exchange" in the title strongly implies that the recent disaster could have been a motive for her death. The fact that BTC is just another payment method for her company means something entirely different. Thank you for sharing this.
I'll be curious about the gender classifier, mostly because I'm working on a statistical aging model for different gender/ethnicities. Keep on posting!
i use their api to construct my own playlists and am worried too...
Call his family, that is what reporters do to confirm a story. The man created a currency that is used world wide, is talked about every day on HN. Can you imagine if facebook was created and we didn't know who did it?
User authentication done right?
Does anyone here have some suggestions, books or articles, about authentication best practices for http(s) explained in a framework/language independent sort of way? What is your favourite resource on this topic? (barrage of Qs, sorry but I hope to learn something and can think of no better group to ask.) Is using secure cookies only for session validation/authentication really acceptable (effective)? How can one protect users at coffee shops and other public places where everyone shares an IP address? Would detecting the users machine, OS etc. from the http headers and hashing that as part of the secure cookie be a good idea so a cookie thief would need the same hardware/software as the victim? I haven't (yet) driven around to various public internet access points to check how their servers are configured, whether or not information about a users system is included in their request headers. Does anyone know how frequently this is done on a public server with a shared IP address?
Yes, citation needed, for you. When you make claims you need to back them up. How hard of a concept is that?

You can't just go around spouting "facts" without any basis.

EDIT:

Congratulations, you have just been hellbanned for your comments to me. But since you asked for a citation, here you go:

http://en.wikipedia.org/wiki/Philosophic_burden_of_proof

http://en.wikipedia.org/wiki/Argument_from_ignorance

http://en.wikipedia.org/wiki/Scientific_burden_of_evidence
Taking advantage of the existing situation for maximum personal gain doesn't indicate doublethink. It only indicates that they care more about themselves than they care about "the greater good" - which, in my opinion is how it should be.

Somebody's going to be getting paid for doing nothing - it might as well be me.
I agree that I should be looking for people who produce quality work, but I also think there's some flexibility to the 'interchangeable pieces' part of the argument.

Here's the thing: Building anything ends up being a very iterative process. From my personal experience, by the time one moves from the prototype/beta phase upwards of 90% of the original code/design base is thrown away, redone, etc. Since what I'm really looking for here is the first-cut that allows for the validation of the idea and the on-boarding of the first few (hundred-)thousand users, I think there could be some advantages to a little shorter-term thinking; if-and-only-if that means I'm able to deliver that first cut to market sooner than if I were to focus on the stability of the team upfront.

Don't get me wrong, I'm still wavering on my opinion of this (hence this entire thread). But I am really enjoying / appreciating the various methodologies.
For an interesting and deep analysis of China Study, one can look at

http://rawfoodsos.com/2010/07/07/the-china-study-fact-or-fal...

She uses Campbell's own figures, but comes to almost diametrally opposite results. It's up to statisticians here to judge how right or wrong she is ...
Yet Another Responsive vs. Adaptive Story - eBay's Multi-screen approach
Knit for oil damaged penguins
From a webhosting perspective, few people ever notice when their site has been attacked.

To a degree, this is by intention of those doing the attacking. They would rather have the site up and running, while the spam, code injection and backdoor can sit there earning them money. It's not until the spam causes damage (or is visible enough) that someone calls someone who is in charge, who in turn might hire a web developer, who in turn calls the hosting company in order to figure out that a 5 year old WordPress site that someone else put together has not been updated. Then it can take even longer until the new web developers has negotiated a price to fix the situation.
I was in the same boat as your daughter, and the only reason I was able to skip grades is because my elementary school was awful (so I looked smarter), and my mother is excellent at dealing with bureaucracy. I know very bright people who would have very easily been able to skip grades; much of the material students learn is repeated about 3 times over the course of 12 years.
TI Launches “Connected LaunchPad”
Tell HN: Meeting Satoshi 
back in 2011 I convinced my wife who ran a small creperie in DUMBO, Brooklyn to start accepting bitcoins. We were one of the first in the world physical location that accepted this new digital currency [1]. In the next couple of month we received a lot of attention, but no one has purchased anything with btc. Then one day, my wife calls me and informs that there is someone who would like to pay with bitcoins. I got excited and asked her to take a picture of the guy because he is the first one and it's a historic moment for us.
He bought 2 crepes and paid using his smartphone and our QR code with btc address. One crepe and a lemonade was 1 bitcoin at that time :)

After he finished his food my wife approached him and asked to take a picture of him for being the first. He blushed and politely declined citing that bitcoin is an anonymous currency. He wished us well, added that bitcoins should already be in our account and left.

My wife called me back and revealed that he refused to take a picture. So I asked her to describe him. She portrayed the guy as a humble polite Japanese man in his 50s. We joked maybe it was Satoshi, but I dismissed the idea. I assumed it was some one from Mt Gox since it was located in Japan.

Today I showed the picture of Satoshi in Newsweek to my wife and she recognized him.

http://bitcoinbabe.blogspot.com/2011/07/bitcoin-sex-drugs-and-baklava-and.html
An lsof Reference
I'm not up-voting this because Leah Goodman has violated even the most simple of journalistic integrity that should be afforded to such a sensitive topic.

Firstly, she very dubiously breached Nakamoto's trust by attempting to get through to him by talking about his passions. Then, when she didn't get the response she wanted, she posted this article that lists multiple family members' full names, most of Nakamoto's (if this is even the real Nakamoto) personal and employment history, and then has the audacity to post a photo of Nakamoto's house that is close enough to a google street view photo, enabling others to pinpoint his location.

If something bad happens to Nakamoto as a result of the personal information disclosed in this report, it will be a great shame for Newsweek.
The new documentary Particle Fever breaks down the “God particle”
Researchers Create Legal Botnet Abusing Free Cloud Service Offers
"This man is Satoshi Nakamoto."

"What?" The police officer balks. "This is the guy who created Bitcoin? It looks like he's living a pretty humble life."

- I do not believe this exchange took place. The police would've had his name from his initial call to them, and a random officer from the Sheriff's department would not likely recognize that name as the creator of Bitcoin. Just saying.
App developers, this app feature will get you dates
How is it unethical?
The guy created a currency that is used around the world and is a mystery.
I think what your proposed cognitive model of anti-government government workers is missing is something Upton Sinclair pointed at:

"It is difficult to get a man to understand something when his salary depends upon his not understanding it."

I've worked for financial trading companies and for advertisers before, but I can't do that work anymore because I think those industries mainly make the world worse. Not won't do it, but can't. The daily conflict between my principles and my actions would be too painful.

Cognitive dissonance is really uncomfortable. I don't think most people can live with the cognitive dissonance of being an anti-government government worker. Not without falling into what user omegaham correctly identifies as doublethink.

And I think that would be especially true of the libertarians I have known. If I were to generalize about them, I'd say that on average they're unusually thoughtful and unusually principled. Most people don't even try for a coherent political philosophy. I just don't know a lot of people who will think that deeply and then be totally ok not living by those principles.
For the same reason nearly everything McDonald's makes starts with "Mc" -- it establishes and reinforces brand cohesion.
10 Fascinating Statistics On Mobile Users
Heller: polymesmeric. Does it count if it's used as a byline on the cover, I wonder.
If the government did a good job of feeding its soldiers such that every time you get a government meal you're talking about how great it is, it would be inconsistent to say that government-provided meals are a disaster and that nationalizing meals would make everything related to it terrible.
No.

In no way is it an "open question' if "light smoking" is even bad for you: "light and intermittent smoking pose substantial risks; the adverse health outcomes parallel dangers observed among daily smoking, particularly for cardiovascular disease."

http://circ.ahajournals.org/content/121/13/1518.full
While not suitable for production operations, my go to has been a random one man vps shop. I have used him for years, because it is the cheapest plan I have seen. I pay $20/year per server, which makes it an easy decision to add another one whenever an idea comes up.
So, this is kind of network subnetting but for iBeacon, right?
That's true in the same way that double taxation is a concern when setting up a corporation. It kind of is, but it's really not.

Due to downvotes, I guess I better explain what I mean: Basically, EC2 provides instances where "if you restart your server you lose your data". You don't use those when that would be a problem for you, you use EBS backed instances which do not have this problem. Or you do it some other way. Point being, this is technically true but it's not really a problem in practice.

The double taxation reference refers to it being a somewhat common misconception among people that have taken a business class before that US corporations are "double taxed". IE, corporate profits are taxed, then your personal income is taxed. This is technically true but does not actually matter because you pay yourself a salary (which is taxed as income), but this is deducted as an expense from corporate income (thus not double taxed).

Point being--it's the same FUD.
Vim is sexy ~ Lightweight Editor
10 Important Google URLs That Every Google User Should Know
Not being a Pythonista, I have the following questions:

1) Is there a (native or custom) date type in Python? Is it an object?

2) Midnight when? Today? This date last year? Sure there's a "zero value" for dates - it's the epoch for whichever platform or library you're using.

3) Why in would anyone call it a "date" if it's really a time?

Maybe I'm getting off into the philosophical decisions of the reptile wranglers, but this particular debate sounds a lot like someone made a decision long ago that had ramifications further than expected and now the justification is engrained, things are built on it, and no one's willing to make the 'correction.'
Oh, I agree with you. The Grantland thing from a bit ago is I think a better example than this Newsweek piece though. Here there's arguably a legitimate public interest served by knowing where this huge and valuable thing comes from. While it right on the border, and others may certainly disagree, I think it's a stretch to call this piece so far over that line as to merit outrage about it.
I think there's a bigger design problem then, e.g. those functions should really be classes. I'm just talking about doing a few 'extract method' refactorings.
Unit tests aren't for asking the right question. There code is there and readable (hopefully) so that shouldn't be an issue. Unit tests are there to ensure when you need to make a change you don't include a regression (moving code backwards). Missed something that the function was previously doing.

They aren't useless and have a clear place in testing. Unit tests alone can't guarantee a fully tested system, but they minimize engineer error when working on various pieces of a code base, but this is predicated on cleanly separated and testable code pieces.
I also find this incredibly dubious.
This is what is plaguing the ocaml compiler and standard library. Overconservatism with respect to obscure features. For example, a patch was written to speed up hashtables (IIRC), and was rejected because it would change the result of hashing format strings (type-safe format strings have a different type from plain strings).

I can't imagine a single application where you would need to preserve the value of hashed format strings. But specifying their value so that you can rely on them just seems to be a bad idea.
Saw your OpenBSD spam yesterday too. Do you develop for the project?
With a little effort you can use the API[0] to spin up or destroy droplets. Sure, AWS and other services do that for you but I think this one of those cases where rolling your own isn't a crazy endeavour.

[0] https://developers.digitalocean.com/droplets/
Well, if you read the mailing list thread there are several core python maintainers saying that is bad style. So I wouldn't call it just a matter of taste when core maintainers disagree with it and parts of the standard library break your code when you do it.
It's also really hard to get an answer out of them for more than the simplest of questions.
They don't care. This is the story of the day and week.
Came here to say their description of WTF it is was poor. You beat me. Have an upvote!
Given a full name, it is trivial for anyone to find someone's home address on account of it is already published, most often by local governments.
So this guy was found using public records as it's his real name or used to be? I would suspect that the authorities therefore would have known about him for far longer than Newsweek.
Map of the Swiss tech startup ecosystem
If she accepted payment in bitcoin isn't it possible that she had a bunch of bitcoins in MtGox?
I've been using DO for about 5 months now, and love it. I still host my main websites other places (dreamhost, who, despite some issues, has been consistent in improvement, and is fair in prices), and I use DO for stuff like mumble servers, a few games, as a ssh proxy from less secure locations, and as some as a shared shell with friends for various skullduggery and fun. Very impressed with DO's service and price, but even more so ease of use.

My main issue is that I would like a hardening script, instead of having to go through each new one I spin up and lock it down.
Python has dates, times, and datetimes[0]. They're all objects. So yes, you could get around this by always using a datetime. However, sometimes what you need is just a time.

[0] http://docs.python.org/2/library/datetime.html
If you are talking about people writing 0==False in stdlib I argue that's a bad code. There are times when you don't want to distinguish 0, False, None, or empty. Unlike JS which has == and ===, Python only offers == I like that. Coding like !=0 is very C like to me, or not taking advantage of Python. In the Python world, it is common and advised to test trutfulness until you have to test the actual value. That is, you can get away with a lot of if object instead of if object.size == 0 or if function() == 0, i think you can do this by implementing your own __eq__ and __nq__ for the object. Imagine someone has multiple values to return depending on the logic branch, the following is arguably ugly and bad, but say it happens:

if cond1:
return -1
elif cond2:
return -2
elif cond3:
return -3

Unless there is a good reason to return these ints, if you only care about the semantic (to distinguish which branch in the caller's), just raise your own exception.

if cond1:
raise cond1Exception
elif
raise cond2Exception

So there are ways to go around and make code more readable. is this a bad coding? Each has its own taste.