skysight-inc/HackerNews huggingface dataset:
I fundamentally lack respect for bureaucracies because although they may be made up of minds far brighter than mine, they are subject to organizational dysfunctions and well documented psychological failings like group-think. The Peter Principal is another problem, as well as the influence of outside money. Additionally, the incentives are wrong for individual scientists--making bold calls is a career risk. Going with the flow is career enhancing.

Further, the FDA doesn't operate on the precautionary principle.

References:

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

Distorting effects of authority (this applies both within the FDA, and regarding listening to the FDA)

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

Conformity and group-think:
http://en.wikipedia.org/wiki/Asch_conformity_experiments
I don't see any hint of coercion in the article. It seems to me that you're showing bias in thinking so. The foreman is painted as using his prior experience to influence the other jurors, in a manner that he shouldn't have. He isn't painted as being a standover man.
It really depends on how you manage your inbox, one of the drivers behind us building Tray was the customisation it offers. The triggers that define the rules can cover as many or as few contacts as you wish ie 'anyone I have a meeting with in the next 48 hrs' can be a trigger, or simply based on email content, pre-defined contact groups etc. In most cases this is a handful of rules.

Email rules that are setup within the client or service restrict filtering to contact, folder, content (in some cases). We can react to data that's outside of your inbox, anything from your relationship to the contact based on another web service, to accessing, storing, and sharing with services you use regularly. Beyond this triggers such as time, email load (driven from analytics), location can all come into play. We are really just getting started with the possibilities, a way to interact with custom web apps would be great for developers/companies that use bespoke tools.
[Gays] won't magically turn you into a lustful cockmonster
Shepard Fairey gets 2yrs.'probation in Obama 'Hope' poster case
How do you make your $ character appear smaller than usual?
The same thing for zsh https://github.com/jeremyFreeAgent/oh-my-zsh-powerline-theme
Can't be bothered.
The point that we are consumers first and producers second is a very good one. We absolutely need to accept that jobs are a cost, not a benefit.

But the article goes way off the rails towards the middle:

"But capitalism as such is not interested in quality of life. It is essentially a system for producing things to sell at a profit, the greater the better."

This is silly. Insofar as capitalism makes normative claims, the claims are merely that people should be able to do as they wish with their own property. It also makes the positive claim that allowing people to do this will typically increase utility for all market agents.

I'm also not sure what the heck he is talking about in the conclusion - people without a liberal education are unable to make their own choices about what to buy? Huh?
I even don't like using map, pefering comprehension.

[w.upper() for w in ["foo", "bar"]]

This underscore.py is not pythonic. Don't use it.
Check if your income makes you eligible for Income-Based repayment: http://studentaid.ed.gov/repay-loans/understand/plans/income...
I think it really depends on the type of apps you write. If you write small - medium rails apps, then the db is usually just dumb storage and if you are careful to use the ORM properly, then DBs are just plug and play. If your app is larger and you need more features, then you look more deeply into the features of each in which, most of the time, POSTGRES is the clear winner.
Sesame seeds, ice-cream and the colour cyan exists. It's not all bad.
Physical Book as a Computer Interface
> No, you'll have a maybe temporary hard time.

If you come from a middle-class family that can provide a safety net for you, or live in a social-democratic country that provides a safety-net for everyone, then yes; you end up with some unpleasant months and get back on your feet. But in the U.S. you can end up in some pretty bad situations, perhaps homeless, and lacking things such as internet access, nice clothes, or a permanent address that are very useful for getting jobs or otherwise making money. If you end up in that kind of position, it can be very hard to get back out of it, so most people, especially from less-well-off backgrounds, put a large premium on minimizing the risk of getting into it in the first place. Hence, a preference for "safe" jobs at larger companies.

(Part of the problem is that what does exist of a safety net in the U.S. moves at a glacial pace, and is geared towards chronically poor people. For example, housing assistance programs typically have years-long waiting lists, so they serve the exact opposite use-case from the person who needs a place to live ASAP, but only for a few months until they can pay their own rent again.)
Reconstruir una secuela de pie equino varo congénito
Collection functions are not that useful in Python. For Function functions I'd prefer using decorators.
In the 80s high schools were pushing German.
Yeah but I've seen several people who tries node dismiss it on the grounds that this programming style is immensly complex and incomprehensible. In this guys words "The async-style of programming is almost entirely inaccessible to my brain".

I just find it contradicting then that every man and his dog seems to be able to whip up some client side Javascript which works in the same way..
every time I read a PostgreSql vs MySQL post the only thing I can seem to take away from it is that DBA's really seem to hate the fact that MySQL has made them obsolete and really want you to think you should switch to a platform where they are necessary.
As apparently the lone voice of dissent, I like to say that I find the StackOverflow moderation to be helpful and increase the quality of the site. I suppose it's not a coincidence but I don't find it difficult to participate at all.
I second beets, it handles big libraries better than any tool I've come across. My once messy library is now pretty much perfectly tagged (thanks to MusicBrainz) and organised.
It used to be like that for me, until I met someone in real life who's a few years older than me (late twenties) and who is a self-proclaimed programmer and who acts like that.
And I think you are wrong.

From wikipedia:

>In computer science, concurrency is a property of systems in which several computations are executing simultaneously, and potentially interacting with each other. The computations may be executing on multiple cores in the same chip, preemptively time-shared threads on the same processor, or executed on physically separated processors. A number of mathematical models have been developed for general concurrent computation including Petri nets, process calculi, the Parallel Random Access Machine model, the Actor model and the Reo Coordination Language.

You can certainly build the actor model on the backs of threads.
Doesn't this go contrary to one of the greatest "benefits" of software - that it is reusable?

But you are arguing that if someone says, "Just give me the code, I don't care how it works, I have a test and if it passes then I am happy" that this is a bad thing.

What is wrong with that?

"Give a man a fish you feed him for a day, Teach a man to fish and you feed him for a lifetime, but you reduce the efficiency of society since the fixed cost of catching and feeding yourself one fish far exceeds the marginal cost of a fisherman catching one more fish." - American Proverb.
2 years of work experience taught everything
I did a quick grep of the go tree to search things that are unsuported by uClinux, but I haven't found any. It might just work.

edit: the CPU is ARMv4T, the gc Go compilers generate code only for ARMv5 and higher, so it will not work.
Maybe use \033[L (ANSI for insert-line).

Edit: If I understand what you're doing, then maybe you can use this:

tput ind; tput home; tput il1; echo -n "header"; tput el; tput cup $LINES 0

Use "man terminfo" to lookup things like "il1" and use "infocmp" to see what they translate to in your terminal.
I do believe it is because it already worked before -- the cloud essentially needed one thing, cheap and fast consumer broadband.

3D printing needs a lot more than that, before it will become viable, while corporate blogging sounds a lot less useful than a twitting refrigriator (which could be a cool, if terribly expensive, gimick). After all, who the fuck wants to read a corporate blog from the people who make your toilet paper?
The scary part wasn't necessary to experience something wonderful.

I am producing electronic music myself. These days, where the internet is mainstream I don't dare posting anything online.

About 9 years ago, things were different. I was a 15 year old kid and enjoyed producing trance music. My setup was extremely primitive and my music in a way, too.

But I managed to make those tracks sound quite euphoric.

Then (that's how I actually learnt HTML & CSS) I set up my own webpage and put that stuff out there.
(later, that project turne into a little net-lable where 4 people were posting their music for free and we started doing remixes for one another)

To my surprise, quite some people were downloading my songs. Some even burnt them onto CDs and listened to them in their cars. (Back then, internet-browsing and recordable discs weren't exactly cheap. So in a way, they were paying for my music!)

The "highlight" was when a DJ from a big Ukrainian radio station played the tracks in his show & on one of his gigs. Some of the listeners posted positive feedback on that station's website.

Perhaps, programming turned me a little paranoid, but today I am quite scared of what could potentially be done with every bit of information you put online. It is true that wonderful things can happen, but (unknown) dangers aren't to be underestimated.
I agree that the Node.js model of concurrency is one of the weakest models out there. CPS is for the compiler writer, not for the programmer.

The underlying problem is that sequential languages do bad when you "bolt on" concurrency to them - unless said language is expressive enough to make it bearable (Haskell and some MLs come to mind). For all other language, you are just frankensteining your system.

The reactor-model, of which Twisted, Node.js and a couple of like systems are built around has one advantage: It is fairly easy to get going. It is by far the simplest model you can get bolted onto a system with relative ease. The crux of the problem is that we have a lot of sequentially oriented programmers who suddenly need to do full concurrency. This is the first attempt.

To a professional Erlang programmer like me, it does look rather odd that one would hail a reactor model as being anything decent to work with. There are other concurrent calculi out there, which may be better than what Erlang provides, but none of them worries about callbacks in the style of Node.

I have a hunch the kid must be dragged screaming into the concurrency shop.
Transhumanists: Who Are they? What do they want, and predict?
you're out of your skull if you really think that Haskell has a shot in this market. Node.js is popular because it's easy to learn. Haskell fails there. That's probably the most important factor for web frameworks. Remember the total fucking trainwreck that is Rails, and how popular that was (and still is)?

Technologies don't become popular on technical merits alone. Haskell fails at psychology.
Good job! I know that some of these functions maybe have already occurred to Python developers (map et al), but this probably lead you to a broader understanding of underscore.js itself.
Mobile phones are an old technology. They've had a few different types of technology.

It's trivially easy to see analogue mobile telephones disrupting a wide variety of electronics. Luckily, no one uses analogue phones anymore. It's trivially easy to get a GSM phone to disrupt other electronics. (The burbling noise you hear over a nearby radio when the phone connects to the cell tower is one example.)

Airline safety is conservative. Very many people travel by plane. (Over 133 million just in London each year.)

Being conservative is probably a good thing.

But how are the rules supposed to change? Given that many people think these rules are nonsense, how should the regulatory bodies test phones on planes?
@shit_hn_says

Why not? A thread allows for two parts of the program to be running concurrently. Whether or not they run in parallel is orthogonal. Why don't you think they allow for concurrency?

A few citations to back myself up:

Concurrent Haskell is all about adding threads to Haskell: http://www.haskell.org/ghc/docs/latest/html/libraries/base/C....

The Java tutorials on concurrency all use threads: http://docs.oracle.com/javase/tutorial/essential/concurrency....

The Scheme manual uses threads for concurrency: http://sisc-scheme.org/manual/html/ch06.html.

The Oz language also uses threads for concurrency: http://www.mozart-oz.org/home/doc/tutorial/node8.html.

So who's wrong here? The world leading academics behind Haskell, Scheme and Oz? The industrialists and pragmatists behind Java? Or little old you?

The reality is that threads were created only to allow for concurrency. They were then re-used to allow for parallelism when we had multi-processors and then multi-cores.

Edit: does this guy work at Google? Unbelieveable.
Really well thought out article.

The single app vs. multiple apps distinction is a good frame for constructive discussion.

Not so much because Postgres is better or vice versa but because in these days of agile and YAGNI development* there's a real problem with some developers not thinking further than the next iteration.

I like that development shouldn't be weighed down by 'what if we'll need X someday maybe' but it should have at least a rough roadmap - the terminology i use next is irrelevant but I'm getting at the idea of having macro, micro and miso level goals defined - in the future we'll deliver architecture concern Y, so let's not box our implementation into an incompatible state.
Have a space by all means where people can talk, just make sure it's soundproof. I had someone sitting next to me on an hour long train ride, who, if she said "at end o' day" one more time, I would have killed her and pleaded justifiable homicide.
I've had several interchanges that have led me to limit the amount of time I spend trying to help someone.

I answered a question on a forum with a series of other questions ... some were the "what have you tried" variety and some were not. After three or four iterations of "defining" questions and answers, the person I was helping said in exasperation "can't you just give me the code now"? To which I responded, "I don't have the code you need ... but I can help you understand how to write it".

The person's response is indicative of a certain type of person that I no longer try to help. He said "thanks for wasting so much of my time". How is educating someone a waste of their time? I guess it might have been more a waste of my time (especially given our relative level of expertise and pay grades).

So now I rarely give out code and often tell people up front that I won't. If they want to learn, I'm happy to help them learn and I am constantly amazed at the additional insights I gain during these interchanges. If they don't want to learn, then I just stop the correspondence right away.

One interesting side-effect is that I've come to enjoy the few in-person interactions like this much more. Two people and a whiteboard can do a lot of damage to a problem and at the same time, build bridges between those people. Conquering a problem together almost becomes like playing on a team together or fighting in a war (yes ... with far less risk).
What are you on about? Concurrent programming is the set of problems that exists when there are multiple 'computational processes' accessing shared state. This is a 'thread' (overloaded use) about JS, but Java has a package called java.util.concurrent and there's also a seminal book called "concurrency in practice", these are about nothing but threads.

Parallelism is just a new buzz word for people who have just discovered that threads\processes exist and they can have multiple things running at the same time. They just removed the shared state cause they don't want to have to deal with the headaches of concurrent programming.
No, the starter edition map pool has been unchanged since its announcement.
Not only do I agree, I'd take it a step further: the jurors should be expected to use their specialized knowledge. Yes, they should rely primarily on what's presented, but the application of knowledge is important. Yes, there may be instances where a jury foreman misinterprets the law, but that can happen anyway, so why attempt to enforce the unenforceable and pretend domain knowledge isn't important or useful?
I think the easy part of China's ascendency has just about finished, a lot of very hard economic, political and demographic problems are about to kick in, I wouldn't presume that their continued meteoric rise is guaranteed.
I'm I the only person who is reluctant to add a service hosted by a startup to your email process? What kind of plans do you have for when they close/exit/pivot/whatever were calling it these days? How is this not going to be another Sparrow or Fluent?
Not to mention Prince's former name...
I've never been able to completely dismiss MySQL since it obviously works for so many users, but I also haven't found it very useful in my work. I started with PostgreSQL in the '90s and every time I tried to use MySQL, I found myself asking either "why did it do that"? or "why would I want that"?

The article describes two databases that are very different conceptually, and I think they're mirrored by users that conceptually think about data in different ways. So if one or the other works well for you, go for it.

I should note that I have successfully deployed applications on both platforms ... once I started doing most of my database interactions through an ORM, the differences didn't really matter any more.

Vive la difference!
I will do my best to attribute everything, but I'm also going to be writing this in an open manner and accepting bug reports on github :)

I think the idea justifies a short book, more of a booklet almost. Something you'd want to read as an ebook, but would likely scoff at in a dead-tree version. I have a strong feeling that ebooks are to books like blogposts are to newyorker articles.
It's really a perfect storm of destruction, driven by greed and exploitation.

1. If you are a young person and aspire to "middle class" employment, in 90% of cases you need a 4-year degree. The reason this is true is simply because potential employers will prefer an applicant vetted by a college admissions council versus a not-vetted candidate. It's a basic signalling arms race.

2. Many professions such as law and medicine legally require purchase of the appropriate degree. There is no option for apprenticing or self-study and sitting the licensing exams without the degree. If you want the profession, you are required by state law to buy in. And the degree-supplying institutions have no qualms about "finessing" employment/income statistics (if they even pretend to collect them) and the like to give the impression entrance in such professions is like winning the lottery.

So you have two sources of basically inelastic demand for these little sheets of paper from young people anxious to find a seat in society. If you are a supplier of such sheets of paper, how do you exploit this situation for maximum profit? After all, 18 year olds don't have the cash in their pockets to be defrauded of. The solution, of course, is the federal government.

Make a deal with the federal government that in exchange for risk-free blank checks from the federal taxpayer, you, the degree-supplier, will graciously grant these poor 18 year old saps with seals of approval from your fine academic institution. Once you have have this deal arranged, blow tuition through the roof, say 500%+ in the past 10 years, with precisely 0 correlation to actual costs or say competition in some sort of "free market" where firms are actually exposed to "risk" etc. Congratulations sir, you are now wealthy. You won America!

Oh, it's not fair to indenture teenagers with mortgage-equivalent debts at usurious interest rates for a service most first world nations provide for free or limited expense? Doesn't matter: 'merica.

Oh, it's not constitutional to disallow discharge of these exploitation debts in bankruptcy? Doesn't matter: 'merica.

I think basically the question is: why aren't we fucking over young people more? I think if they want a college/professional degree we should make them sign contracts like "In exchange for this most valuable degree, any money I ever earn over $30,000 annually for the rest of my life goes straight to Uncle Sam, and/or the appropriate collections agency".
Yes, that's going to be a large part of the book. It's why I'm going to be doing interviews with programmers - to find out how they manage to fit in with the rest of the world.

The why part will be aimed more at people around programmers, so they can better understand that freak occupying a part of their living space and being all maladjusted and odd.
Someone is making an effort to lower the threshold to my field of expertise, and make it available to a general public.

My livelihood depends on this!

We must divert our energies to repress and quell this enemy. Spread the fear, uncertainty and doubt!

// the node haters manifesto //
The other irritating thing about the ban is that no distinction is made between devices that transmit RF and those that do not. Granted, there are fewer and fewer devices that one is likely to carry and use on a plane that are not capable of transmitting something (e.g. wifi or bluetooth), but iPods were banned during takeoff even before they had wifi, and AFAIK portable CD players and tape players were never allowed either. It actually makes more sense now to ban everything because enforcing that they were all in airplane mode would be impossible, but 10 years ago the ban was universally applied to electronic devices and not only radio-transmitting devices.

Mostly I just want to be able to use my Kindle during takeoff and landing. Maybe it will happen:

http://www.theatlantic.com/technology/archive/2012/03/flight...
If the Kindle is just a portal for buying/consuming Amazon services then I don't see it setting the world on fire. Once more people realize tablets are the ultimate mobile general-purpose computing platform then interest in consumer portal tablets will wane.
On Sticking to Open Software, Celibacy and Veganism
Organic Traffic Packages
I suppose you go back to doing whatever you were doing before you used the service. Annoying yes, but it's not like they're hosting your mail and you have to rush to find a new host.