skysight-inc/HackerNews huggingface dataset:
Most of the recent research on factors affecting vehicle speeds is summarized in http://onlinepubs.trb.org/onlinepubs/circulars/ec151.pdf

In it, Dimauita et al credit every foot of lane width with a 2 mph increase in vehicle speeds, and Wang et al credit each additional lane with a 6.5 mph increase.
Isn't this nearly a heatmap of poverty, or mean income?
I like this in theory, but in practice I have found that the differences between databases make this not work as easily as it should. I often end up seeing subtle behavior differences when using different DBs, which can be problematic when something works fine in development and fails in production.
I am sure there are many places where this is the case, but the OKC area is where I live :).
Panhandlers aren't always homeless. I don't think this is really news to anyone though is it?

If the woman was really homeless, she couldn't have made use of the spaghetti dinner fixings anyways; she likely wouldn't have any good place to boil the water or prepare the meal; even hotplates are disallowed at most shelters, due to the fire hazard.

It's much better if you can ask someone if there are any particular items they need, or better yet stop by a local shelter and inquire there as to items that most need to be donated.

If i were that woman i would have said "thank you so much ... but" and let your wife down easy. But even for the genuinely homeless fending for yourself on the streets doesn't leave everyone equally grateful.
A Brief History of Animated GIF Art, Part One
Like in this clip, taken with an iPhone, of guitar strings vibrating?

http://youtu.be/TKF6nFzpHBU?t=10s
LinkedIn Owes Employees $6M After Violating Federal Labor Laws
> If it works

That would be the question. Is it bugfree, or will it eat my data and let scriptkiddies run amok on my host?
Typically my design approach for this is to use cron items to pre-compute components so that they don't have to be computed (nor templated, ideally) at runtime.
Actually, they're sensitive to many of the same things.

It's just easier to get those things out of whack. We can't change the acid content of the air animals are always in contact with, nor can we significantly change the chemical composition of that air.

An ill-maintained fish tank will do those things - doesn't meant that a fish is more sensitive than a dog, only that the environment of the fish is much more sensitive than the environment of a dog.
PgHero – Database Insights Made Easy
men and women are not the same. they certainly deserve the same treatment, but no amount of legislation or arguing will change the fact that they are biologically and chemically different, their brains are wired differently through hormones, chemistry. yes, culture can change this wiring to some degree, but it will never make the sexes equivalent and interchangeable. no one is "blaming" biology. it is not an "creative" way to treat people differently. the differences are there and have been there for tens of thousands of years and will continue to be there for thousands of years. disregarding biology is no less harmful than "blaming" it.
First lesson of executive leadership is that you need to learn how to not give a hoot about what people think about you on a personal level.

If you're worried about being a <whatever> you are unlikely to succeed when things go bad and action needs to be taken.
France, Germany and UK top 'right to be forgotton' requests
Yeah, but it isn't a grey area, the rules are well defined and actually pretty easy to understand. I've had people not know the rules before, but they wouldn't call themselves experienced.
How do you down vote submissions? I thought you could only down vote comments.
To my (non native speaker) ears, "asshole" sounds less offensive because it's gender neutral. An asshole can be a man or a woman, but only a woman can be a bitch. So calling an aggressive or ruthless CEO "a bitch" sounds slightly more offensive and sexist to me. Maybe I'm wrong.
I think ORMs like SQLAlchemy are really useful for many many use cases. I don't think most people who work with ORMs deal with the kind of complexity described by the author, let alone work on such a specific application for 30 months at a time. In that sense, ORMs are super powerful tools that cut down your work, shortens your code and do nifty optimizations once in a while

With that being said, this article totally resounds with me, having resorted to using direct SQL in almost all of my large-ish projects. Using an ORM always starts out nicely, and then eventually it gets messier and messier. Specifically, when your DB data has subtle interactions with a cache, I have found it harder to keep ORM code clean and readable.
"Object-oriented programming is great. It's what's enabled developers to create the vast world of amazing applications available today. But there's an impedance mismatch between OOP and relational databases. That's why today we're reinventing database access. Say hello to SQL."
I would say that the security properties are different, with pros and cons for both. For clarification, Tendermint has strong security independent of external factors, while Bitcoin has simplicity but it is always vulnerable to an external attack -- this is what makes all PoW altcoins vulnerable. Tendermint has pretty strong consensus guarantees, but when it's broken, it's broken and requires manual recovery. Bitcoin has weaker consensus guarantees, as any blockchain fork could become a winner in the future (esp true if large miners form cartels), but it's not brittle and in the case of a fork, the winner can be determined (even for inactive participants) by shoving more work onto it. Finally, Tendermint does require clients to "hook-on" to the correct blockchain fork by a priori knowing a recent correct blockhash before syncing, which is easy to do in practice and only needed after a period of long inactivity.

But the problem is the same problem, and I would counter that the security is if anything stronger than that of Bitcoin. Ever since I studied pre-existing literature on consensus, I no longer see Bitcoin as you probably see it today.
I believe low speed limits give police officers a legal means to stereotype drivers and pull them over. Since everyone is now speeding, they can pick and choose who to pull over and have a legal reason. Young? sketchy car? minority?
Not only for women...

http://www.nature.com/nm/journal/v14/n11/full/nm1108-1170a.h...

http://www.nytimes.com/2012/08/23/health/fathers-age-is-link...

http://www.nytimes.com/2014/02/27/health/mental-illness-risk...
Database portability is a poor argument for using ORM in my opinion.

In the real world, most apps don't change database engines during their lifetime. You wait for the rewrite and then you pick a new engine.

If you stick to ANSI compliant SQL, you should be fine when porting over databases. It's not perfect but it'll get you most of the way.
I'd rather write Django ORM than write create and alter table SQL, and migration SQL any day of the week. The developers who wrote Django's ORM are also way better at writing SQL and database related code than I am and sure I could spend all the time I need to become so proficient that my migrations work as nicely as migrations and syncing in Django and Django related projects like south, or I could just spend that time writing my application using Django ORM. If and when problems happen, as they have, I usually find easy ways to solve them. I've been using Django for over 4 years in high load environments with few frustrations.

Before using Django I wrote my own SQL with web.py, and PHP before that. When I work on non-Python projects I use non-relational databases instead of SQL.
If you think having children out of wedlock is linked to US welfare system incentives, how do you explain global trends?

I think it has more to do with female equality and increased earning power. But it's a complex multi-vectored phenomenon not really suited to an off-topic thread here.
Spock made in Lego
Wrong -- Google lost the first of the Android/Java battles to Oracle for 9 lines of "copy/pasted" range check code.[1][2][3]

[1] https://news.ycombinator.com/item?id=3951575

[2] https://news.ycombinator.com/item?id=3951480

[3] http://www.theverge.com/android/2012/5/9/3010404/judge-denie...
Opportunity cost only exists if you're an optimizer.
> Women have to give up more than men.

I don't think the couple weeks most women might consider the minimum during maternity leave is significant.

It seems pretty even IMO. Waiting until your 40's, 50's or 60's for a man doesn't come without it's own trade-offs.

Most men who "someday want a family", entrepreneurs or not, are probably going to want to start a family before 40 I'd guess. I don't think gender probably plays a very big role in the "when" decision.
My EE knowledge is a few years out of date, but I was surprised to learn that excessive correlation between pages causes problems. The XOR key used for decorrelation is apparently not too hard to reverse engineer, so I wonder if this could be turned into an attack against solid state storage devices. Would storing a particular data stream which becomes very correlated once the XOR is applied lead to data corruption? Wear leveling and filesystems might make this difficult to pull off, but it still scares me a bit.
Thanks for using video in place of GIFs!
Google tip on child porn email leads to arrest, sparking privacy debate
Either that or you can write in a SQL-like language (e.g. JPQL for JPA).
Adam Carolla won’t let Personal Audio drop podcast patent infringement lawsuit
Why I moved to CentOS 7 (on the desktop)
Occasionally I will block off a several hour appointment on my calendar labeled "Develop Software". Usually works. Sometimes do it for our entire team.
In my opinion: throw it away.

More constructively, what are you trying to accomplish? There are few goals that a press release will help you with. It may help with some vanity links in Google News if you search for your name, but that's about it. If you want press coverage or user attention, a press release is almost certainly not going to help.
There is very little in this article about the interests of anyone not driving— crash severity is due to speed deltas, and pedestrians and cyclists are almost always moving much slower than automobiles. And a self-interested driver won't slow down to keep pedestrians safe, since pretty all of the consequences of a auto-pedestrian crash fall on the pedestrian.
This is all quite interesting.

I wonder if there are others in my boat, however, who were (in my case minor) iOS developers, and were initially excited by Swift. (I chatted with Chris Lattner at WWDC and thanked him for what looked in the first couple of days like an amazing win.)

But after a while, I began to rebel against the idea of learning a whole new complex language and new environment just to keep doing iOS development.

So in the end this nice clean breakpoint just pushed me back into the "open web" development camp. I'd like my efforts to work on all platforms.

This isn't a plea for sympathy, honest, or an attempt to put down Swift, which looks like a great development--I'm just genuinely curious if others have had this experience.
I wonder if this can be exploited for business networking purposes. Simply choose a person in your "network" and ask them to introduce you to one other person they know and repeat with the new person.
There are also very high standards (strict regular inspections) regarding vehicle maintenance. US citizens would never put up with that.
That's supposedly to be the ideal case. The problem is that in reality, once you get to the more advanced features and each SQL differs each other slightly, it's anything but agnostic (if it's even there to start with).

Take UPSERT for example, Postgres doesn't have upsert until lately (I'm not actually sure if it's in stable yet), and the upsert's equivalent of MYSQL is INSERT ... ON DUPLICATE KEY, which behaves different than a normal upsert. The ORM solution? Don't implement them at all. In the end, you often end up with a mixture of bizarre ORM code + SQL.

The best compromise I've seen is probably Korma for Clojure (http://sqlkorma.com/). It's not really an ORM, since object mapping isn't particularly necessary in clojure (with map manipulation and all that), but still provides you with some stuffs of normal ORM (implicit relational joins). And yet still, many times once you get to the truly rarely used part of the db ... there is nowhere but raw SQL query to go.
Having moved to the US from Germany, it always stroked me as particularly dangerous that it is common to overtake cars on the right and have slow cars and fast cars in any lane. The article mentions that different speeds are dangerous. I think enforcing cars sorting themselves properly into the right lane would make a huge difference in reducing accidents and allowing traffic to o faster. I wish law enforcement could focus on that instead of giving tickets to people who go 5mph/h faster than most other cars.
Huh, I never figured.

I guess that's a reason to spermbank. Though really, people should just have kids young in the first place. :/
The eastward moving house
I agree that SQL is a brilliant data processing language, while C#, Java or C++ are terrible at it. And there are obvious benefits to learning SQL and being able to use it efficiently, makes imho much more sense than throwing away RDBMS because they're 'slow'.
But if you write applications in an oo language objects are quite natural way of representing both data and logic. Sometimes you do application-level transaction management or use the mapping metadata to implement higher-level features, sometimes you have to integrate application events with data operations, or you need your data objects to live outside of database transaction - ORM saves you lots of coding in such situations. And adds services like caching, prefetch, intercept/triggers etc so you don't have to invent it.
Interesting. This is a university project yes? Will you be looking to open source some of the code, in particular the language parsers.

I ask from a purely selfish purpose as I want to integrate this sort of information into searchcode.com and would prefer to avoid writing my own implementations.
Another problem with ORMs is that they make performance diagnostics much harder. DB-side, you might have a list of worst-performing queries and examining it reveals a huge, hundred-line monstrosity of a query. Because the queries are ORM-generated and are not usually very readable it isn't exactly clear which part of the application is generating it (or why). Even further, if your DBA says you could make the query more efficient by changing X and Y, it's not likely that you can take her advice since the query is programmatically generated! So you have the choice of abandoning the ORM in performance-sensitive paths and inserting raw SQL (making the code ugly) or living with poor performance.

I'm a fan of abstractions only when necessary. I want to have control over 100% of the code stack. When performance issues crop up (and they inevitably will), I don't want to just shrug and go "well, Hibernate must be doing something weird..."
Right; "female" and "male" bring to mind animals and base biology. "Woman" and "Man" distinctly separate us from the animal kingdom.
I find ORMs quite handy, and they've always generated tight SQL.

Oh yeah, we had to support an additional DB recently... all that involved was changing the JDBC connection information and dropping in a new driver. Good luck doing that when everything is written in raw SQL.
I haven't studied global trends. Nor am I suggesting that trends in the U.S. have only one factor influencing them.

That's kind of a bogus rebuttal.
While a different technique, this reminds me of how researchers were able to extract keystrokes based on the sound from each key press.

Here is the original paper:

http://rakesh.agrawal-family.com/papers/ssp04kba.pdf
It makes your code less portable. Raw SQL means you're essentially tied to a single DB provider. What happens when you need to move to a different one?
Lowercase and capitals, just like the python program in the post uses.
I don't think either will be a catalyst for anything significant - there's just craploads released every day and it's unlikely anyone will notice yours unless you, your startup, or your investors are notable enough that journalists are specifically watching for them. It definitely won't be worth paying for.
Assembly is a way for people around the world to collectively build startups
I worry that the example of HTML colour codes implies that the client is more technically minded than the article was trying to claim.

Updated article with new scenarios in an attempt to convey original point better!
Xamarin Acquires Petzold
Gannett Said to Agree to Buy Rest of Cars.com for $1.8B
Yes, but the ORM often influences the schema design. That can be very painful down the road when you realize your tables are actually tables, rather than instances of objects, which would be what your ORM led you to believe.
>>First lesson of executive leadership is that you need to learn how to not give a hoot about what people think about you on a personal level.

Incidentally, this is one of the primary characteristics of the now-abandoned concept of "sociopathy."
I used to write raw SQL for many years, then, around 2005 switched over to ORMs in order to be able to target different databases, have a nice model, etc. Lets be honest here, the ease of justing doing:

p.username = "Carl"
p.age = 33
p.save

instead of "update users set username=:username, age=:age where id=:id" has a ton of advantages. For one, some sort of syntax or type checker is actually trying to understand your queries and makes it easy to find typos before the database laments in the middle of a huge transaction. Strongly typed languages are even cooler here (most notably Slick for Scala, which has a fully type-checked DSL for database querying which makes it really difficult to create typos) [1].

However, the downside of this is that it only works as long as whatever you need from your database is the lowest common denominator of database features. I'm currently working on a Clojure + Postgres project and I'm using all the bells & whistles that Postgres has to offer: HStore types, Json Types, subqueries in subqueries, Upserts, functions, etc. I have a rather complex database that I'm running analytical queries against, and using an ORM for this would simply not work. I'd spend half my time trying to figure out how to implement a certain Postgres feature in -insert-or-name-here. I actually started with Korma [2], a simple Clojure ORM, and gave up because it was too tedious trying to figure out how to get it to correctly run my 4-function column result query.

I've since switched to YeSQL [3] which follows a very interesting idea: You write queries in .sql files (full editor support, jay) and tag every query with a name. YeSQL then reads these .sql files during compile time and dynamically generates clojure functions with the correct amount of parameters based on these queries. It is kinda the best of both worlds. Example:

queries.sql:

-- name: get-users
-- a function to retrieve the user by name
select * from users where username=:name

clojure.clj:

(defqueries "some/where/queries.sql")

;; now I can do:
(get-users "carl")

I think it really depends on the use case. If the database model is simple and there're no crazy database technologies in use, I'd rather go and use an ORM again I guess.

[1] http://slick.typesafe.com/
[2] http://sqlkorma.com/
[3] https://github.com/krisajenkins/yesql
She didn't emphasise it very strongly, in fact it was a very weak emphasis but she was saying that everyone has a different set of strengths and weaknesses. She might find it easier to get press attention as a woman but a guy could easily have a strength that makes up for this.

> But I don't think this kind of dismissal of the issues women have is very helpful

I think she knows better than you, unless you are a female CEO.

She made the point that sometimes when a woman is doing sales the customer can be more interested in her than the product. But historically, a lot of women in sales have tried to use sexuality to get the sale.
I use that example specifically because it came up on /r/chess the other day, and I've had newer players ask me once or twice. I agree that an experienced player should know, but casual players may not.
End of the day, you shouldn't have laws that 80% of the population breaks during the ordinary course if business.

I've found myself in vehicles towing trailers where 65 mph was about as fast as I could go. I continuously had cars passing me. If everyone is a criminal, something is wrong with the law.
Also reminds me of this: http://cnx.org/content/m13224/latest/?collection=col10380/la...
Ditto this. It's likely not to get you any press of value. Write some personalized, targeted emails (or get intros) to press instead. Tell a compelling story (tie into an existing narrative if you can) and keep it short and to the point.
> A recent count of one such table in my work resulted in over 600 attributes and 14 joins to access a single object, using the preferred query methodology

At some point between inception and having 600 columns someone had to have stepped in said is this necessary? Maybe I haven't worked with big enough data sets, but to me that number seems insanely high - and I really don't see how the ORM would be any worse than raw SQL - if they were equally optimized.

It sounds to me like best practices SQL are being compared with worst practices ORM. Now many ORMs, by default, may lead a developer to use bad practices, which I will concede is a problem.

But in optimizing a query with SQL you only select necessary fields - and don't use any more joins than required for the data you need - you only gain over the ORM if you didn't limit the scope of the object you asked the ORM for and instead asked for the full object.

> Attribute creep and excessive use of foreign keys shows me is that in order to use ORMs effectively, you still need to know SQL.

Well there is your problem! Thinking you can completely ignore the underlying database mechanism of an abstraction layer is a little naive - if you want to maintain maximum performance. Though bad marketing of some ORM's may claim differently which is a problem as well.

I agree, there is a potential downside to ORM's. Raw SQL likely will get you better performance almost 100% of the time. Is that necessary? Well, it depends. If the ORM is being used with best practices, I'd say until you're at the scale of billions of pageviews a month, it'd be negligible. However if you're essentially doing a SELECT * and JOINING on all related tables just to get one field from the Users table - then the SQL will win hands down.
I used to live in Atlanta where all of the major highways were capped at 55 around the city. The average highway speed was probably 75-80. If you drove the speed limit, you would be the most dangerous car on the road by forcing the flow of traffic to run around you.

Let's just focus on getting self-driving cars out the door as quickly as possible.
Well, 5 minutes of googling and 6 months of learning russian :)
Awesome. Great job by the way!
I hope people are taking more than a couple of weeks. I know this is America and all, but 2 weeks?!? If I was a (male) CEO I'd definitely take more time than that, at least to set an example that people shouldn't feel like they can't take time.
If you are considered a <whatever> to people you won't go anywhere.
A fair point, I might be unduly influenced by having done a lot of work on a huge, unwieldy internal app. Running the tests in postgres took literally half a day, and there's no way we could have worked like that.

In that case trading some db efficiency for actually being able to do work was a pretty easy decision, but horses for courses I guess.
The problem was SQL got standardized, and became static. There is so much room for innovation in the database language space, but that would mean breaking compatibility with the SQL standards...