skysight-inc/HackerNews huggingface dataset:
I don't understand. The person you replied to didn't object to open access. He objected to this particular article, which (as it happens) says other things besides "open access would be a good thing".

The article suggests that part of the peer review process should be an examination of the software used, which is about as practical as saying that an experimental paper's reviewers should visit the lab and examine all the apparatus. (Actually, considerably less practical, as anyone who's ever done any sort of review on any nontrivial piece of software knows.) This is not the same as saying that there should be "open access".

The article opens by citing an alleged integrity problem in climatology and saying that lack of access to the relevant software is an even bigger problem. This is not the same as saying that there should be "open access".

The article has a very clear political agenda, as you can note from its beginning (climate-specific stuff, which you yourself have suggested taking as diagnostic for political agenda) and its end (approving links to Eric "famous computer scientist" Raymond and TCS Daily). timr is (1) pointing out the political agenda, for which you accuse him of being political, and (2) describing some specific problems he has with the article, which you characterize as "refuting calls for open access" even though his complaints do not at all take that form.

(I think it would be wonderful if every scientific publication were accompanied by every byte of code and data used in the work it describes, or at least the nearest thing to that that's legally and commercially feasible. But it wouldn't cure the problems that the article professes to find in the peer review process, and the only difference it would make to arguments over climate science is that the no-anthropogenic-global-warming people would find something else to complain about.)
I don't like my job at all, am I supposed to? I've come to the realization having a job means turning your brain off in the morning, appearing productive during the day, and making the most of your evening when you get home.
Windows Azure – Using DataSet with cloud storage
There are positive externalities from the use of EHRs, though. The whole health ecosystem benefits (including patients, other providers, insurers, etc), not just hospitals, so it's misleading to consider the hospital's bottom line as the overall impact of EHRs.
Ask HN: Review My (Common Lisp backed) Startup
Microsoft finally urging users to upgrade from IE6
Sounds like it's "The Homer" of cellphones.

http://simpsons.wikia.com/wiki/%22The_Homer%22
Less audio links would be better. Looking at the comments on the post, I see I'm not the only one who had a bad user experience on that page.
Where did Yegge claim that parentheses create rvalue lists?

Other commenters here seem to think you're referring to his complaint about (1,2,3,(4,5)) equalling (1,2,3,4,5), but I don't see how that complaint has anything to do with whether parens create lists. Rather, he's complaining that the comma operator is append instead of cons, kinda.

Note also that here he's talking about a bad decision made "very early on", back when Perl had no references; at that point the only way to make anything like nested lists was by giving names to all the sublists and using typeglobs or explicit calls to eval. That's a semantic point and has nothing to do with the syntactic role of parentheses in the grammar. Yes, nowadays you write [1,2,3,[4,5]] instead and make references everywhere, and that's better, but it's still not very nice because Perl references are ugly, and what Yegge's doing here is explaining how Perl came to need something so ugly.
The old axiom "Failing to plan is planning to fail" comes to mind.

I wouldn't say sell yourself short but always be realistic. For example if its a deadline you want to give for a project will take 2 weeks, build in some space for running over (a % based on complicity and client) and give that.

In your case I think your talking features. You can promise the basics first and discuss a 'stage 2' which adds more functions later.. If you get those done before planned thats a big plus.

Most clients only remember failures, not success. So I would agree with you on this one.
What I want is an extension for my web framework that transparently pre-renders certain Javascript-generated parts of the page, and then sends the browser a serialized version of that page that includes not only DOM structure but fully wired-up event handlers.

This should be possible using HTML and <script> tags, but will take some serious work to become plausibly cross-browser. But if that work happens, there will be a way to automatically provide the usability/speed benefits that previously required dual client & server implementations without the attendant cost. And that will drive a lot of people to using whatever standards those tools are built on.
I regret clicking this link. I should have stopped myself when I saw (sethgodin.typepad.com).
The best thing you can do is satisfy all user expectations, including the ones they do not know they have. People love being positively surprised. So the proposition is this: By the model of your partner, you create expectations for users, and then satisfy them. This essentially means people get excited about something, wait for it, and, at best, it eventually happens. So they think "Yeah, it's finally here.". Your proposition is to keep all that but also have them think "Yeah, it's finally here, and it's even BETTER than I thought it would be!". This is distinct from surprise releases and no release schedules, which I suppose is what your partner is thinking about. Raising client expectations is an excellent idea. Exceeding those new expectations is even more excellent. Promise something good. Deliver something better.
Expectations should be just right. Low expectations is lost business. If I don't think You can solve my problem or not solve it well, why do business with you? Elevated expectations are lost repeat business. If you promise steak but deliver hamburger, why would I come back?
To use Javascript then try the CPAN module WWW::Selenium (http://search.cpan.org/dist/Test-WWW-Selenium/).
Looks nice, but goddamn... These things are always US-only...!! And I'm not talking about the language.

If some startup would actually make anything, literally anything that was global, I'm sure it would get a segment of a market that nobody's utilizing.

edit: And a Javascript alertbox letting you know you're going to see new york instead... That's not helpful.
I don't know, but apart from that there are other benefits which are still valid. And I wonder if the yellow light would be necessary at all.
1. It' a lot harder to distribute to those people than it is to distribute to the early adopter/techie crowd.

2. People like to make stuff for themselves and their friends.
Consider the following dialogue "your new website will be ten times better than your existing one".

What would that make you think as a client?
Hey guys, I've been working on Postabon for the last few months (full time for approximately the last 2). We've been beta testing in NYC for the last few weeks - and feel we have enough content there to launch now. Any feedback (especially criticism) you have would be greatly appreciated.

The basic idea is that we want to help you find and share discounts near you. The video (click 'Watch a Video' on the left) will help explain the concept/history if you're interested.

Our iPhone app's release is pending Apple approval (hopefully just a few more days ...).

HN contributed to this in a very real way. Two years ago when I started visiting HN I had no intention of ever trying my hand at a startup. But being surrounded (at least online ...) by the entrepreneurial spirit here really inspired me.

The Lisp thing isn't actually a selling point - I just thought that the crowd here might find it interesting. If there is demand, I'd be happy to write some blog posts on the how/why of some of our architectural decisions. We're using a 'NoSQL' key-value (with btree indexing) persistence layer too :-D
Paul A. Strassman wrote a book about this in 1997. You can read the executive summary here:

http://www.infoeconomics.com/squandered.php

If organizations aren't following Strassman's recommendations for technology implementation, then it's not really that much of a surprise that they're still wasting money. The costs of technology are basically the same today as they were ten years ago, and it's not like human behavior has magically changed.
Star Wars intro using CSS3 and HTML5
Maybe as its the first..?

They said it has a million threads at about 20 feet long. 5 bucks for a length of spider silk seems high, but I don't really know what goes into keeping that many critters alive and happy.

Also, at the end of the video he mentioned "milking" spiders is a lost art because workers kept getting bitten and gave up. Yea... no kidding. Did you see how big those spiders are?
related article: http://ajaxian.com/archives/star-wars-html-and-css-a-new-hop...
Yeah - I'm sorry about that. We're only useful where we have content - and we only have content in NYC for now.

How would you prefer we degrade if there is no content in your area?
Test-driven development with Christmas lights
There is something like 12, valid 2x2 grids, and you can get rid of almost another (17!)^2 options because rows and columns are interchangeable. Actually thinking about it a little bit the only valid option for the top left square is:

0,0
0,1

However, the vast majority of the grids are eliminated by the boxing constriant before the grid get's all that large.
I've been waiting about a year to actually post here (HN). For access to the beta, please use the invite code: readwriteweb and email me if you have any problems or questions: jonathan@flavors.me

Thanks!
I don't know anything about these guys, but my first thought while reading the post was "He's trying to lump themselves in the same category as successful stores." It's an interesting technique if you don't have name recognition. Say it enough times and eventually people think you are in the same class even if you aren't.
From the article it sounds like the companies are failing. Only three hospitals in the study showed marginal advantages to having software, and theirs was custom built. I'm guessing the other hospitals are more likely to have generic poorly thought out software, like your friend uses.
One big plus of moving towards electronic medical recording keeping is you open up a whole new market for advanced software that 1) makes hospitals run more efficiently 2) provider a higher level of care for the patient and 3) flag and prevent potential errors that could result in malpractice (thus lowering insurance costs across the industry)

The software that does this isn't going to be built over night, and will likely take at least a decade to mature, but when it does the whole industry wins big.
One niche for Perl is it's omnipresence in most commercial Unices, even if as ancient as 5.0005.

I recall many cases at work when we had to use what's on the box and we were restricted by some funny policies to not to install/use any third-party (incl. open source) stuff. You may think it's weird, still it's quite popular in telco companies, banks and other monstrous borgs. Such organizations often run some quite old hardware/OSes and will run it for years, as they think it's cheaper to pay maintenance fees than to introduce a massive change (well often it's true). One indication you're using such box is lack of bash in favour of ksh or some so-called 'posix shell' (which usually isn't standarized at all, btw).

So, Perl saved our asses many times. The reason why some 'certified' stripped down Perl version was installed by the OS vendor was usually some ugly installer used by the vendor.

A little quiz: which commercial Unix do I have in mind? ;-)

[edit: typos]
Also available to JRuby as Celerity, which rocks.
I'm very surprised to see feminists studying the 'Roissy' [1] theory of female career choices.

In short, the theory is that women are extremely intolerant of low status men and try to avoid working in fields where they are prevalent, and particularly in fields where they are respected. It actually has a reasonable amount of predictive power, certainly more than the sexism theory.

I'll be blown away, however, if we actually follow the theory to it's logical conclusion...

[1] Roissy in DC is an extremely sexist, but insightful blogger. He didn't state this theory, but I've heard it described as the 'Roissy' theory since it follows his line of thinking.
I used to work for a health care information systems company called Meditech. They are one of the largest providers software and EHR to hospitals. While I was there I was amazed at how inefficient the whole process was. My daily coding work did not even involve version control! Also we were programming in a language developed in house from like 1985 or something. Its certainly easy for me to believe that a system like that would only cause more problems than it solved.
Exactly the same thoughts here. His entire blog post flashed through my head in the time it took me to click the link. Then I had to read it all over again...
First the simple question: the gap between Phase I end and Phase II start is often quite long. There are other process and IP-related issues (with DoD, NSF might be different).

Your estimate assumes that if you compete you have at least an average ability to win. This is very probably an inaccurate assumption. In my opinion, if you go in cold you are unlikely to have an average probability of winning on even a minority of the topics unless you are highly expert in the field of the topic and bring something utterly original yet reasonable to execute for the funding.

Assuming you do know the topic at a far-above-average level - you might not know how to write a good proposal, or understand what the proposer is really asking for, or be seen to be able to execute successfully, or be able to commercialize the result of the effort (maybe not as important to NSF as of a few years back) to name a few; but you get the idea.

Fundamentally, your odds depend on a fit with the topic and your personal ability to execute this type of process. That is why your odds go up after you successfully execute once.

Lastly, do a lot of legwork before proposing - figure a generous amount of out-of-the-chair legwork into your expected value calculations.

Look around for colleagues that have done this and pick their brains.
Yeah I considered it but Selenium uses Firefox, does it? And I needed a self-contained script without such dependencies.
How about s/tribe/community/ ?
I used Selenium or WebDriver for that. Not bad.
From the article: “No matter what we do to that room, even if we make it all female, women just don't feel like they belong there.”

Could it be that is is just computer science that many women don't feel attracted to? The statement above seems to contradict her own research, and she fails to see it. The stereotypes seem really outdated, too.

Or maybe women just tend to be intolerant... ducks
Squad - Real Time Code Editor
Saying science grant money goes to latino student centers jumps out as odd. Where has this happened?
This is kind of cool, but who is going to digest all of it? The techno folks may have some technology pieces working, but nobody out in the main world would be able to figure it out. I got a little dizzy just looking at all the links to all the pieces in just this one article. Let alone actually reading them all.

I like Java script but I think making it go server side is backwards. Why not make Python or Perl or Ruby go client side instead? (I am sure plenty of folks smarter than me have already thought about and probably worked on it.) Those languages already have all the parts they need except a connection to the browser dom. Java script has a connection to the dom and practically nothing else. These other languages have been getting tweaked for years on the server side. It just seems like such a big byte to get Java script to work as a regular language like the others. It also ignores some of the things that are lurking like Erlang and Clojure. It sounds correct that there are lots of Java script programmers. However are there lots of Java script only programmers? I doubt it. While it is compelling to write one language every where, I dream about it sometimes, we aren't close yet.

So embedding the Perl, or whatever, interpreter into the browser is probably a chore, but it is also probably doable, the browser should be able to deal with multiple languages. I think it is just that the people that are capable of doing that job looked at it and said. "Crap! I will just learn Java script." So the reality in my mind is that programming in two or three or four languages is just easier than doing all that other work. Everybody does it. In fact we say I know Java, or Python, or Java script, but that is just a word to give us a frame of reference when we communicate with each other. In fact what we really know is how to program computers and Python is a subset of the total global programming skill that I have. It is a like speaking English in some specific domain. There is jargon everywhere, one can speak English but one tends to get easily lost if one listens to lawyers speak to each other or doctors, and one is also not a doctor or a lawyer. Does that mean we should create a generalized English that both doctors and lawyers can use in each of their specific domains? Seems a little silly when one thinks about it. Is making Java script work everywhere is really buying all that much?
And with this post, the latest COMPLETELY pointless waste of my time, it's now official: Hacker News has jumped the shark.

Slashdot RIP
Digg RIP
Reddit RIP
Hacker News RIP
Bret Stephens: Climategate: Follow the Money
Your last thought is quite opinionated. The other approach is to write the actual code (in whatever you want) instead of blogging ;P
Looks nice, but goddamn... These things are always US-only.

This one actually has a reason: it takes a lot of effort to contact small business and get offers from them. Remember, once Postabon catches on it can rely on users uploading offers, but right now, at the start, smanek has to do it all by himself.
What is the blub problem?
Gah! The article contains yet another misrepresentation of what Lawrence Summers said:

> former Harvard University president Lawrence Summers suggested that men are hard-wired to be more analytical than women

What he said was that there was more variance in IQ in males than in females, thus there are both more stupid males and more intelligent males - there are more males at either ends of the spectrum. Given a filter for extra-high IQ, you would then expect that there would be more males in that sample.
The problem I have with this sort of research is that I think it makes too much of the "because your female you dont like that sort of stuff" myth.

Im a guy, I love all things tech (and am a bit geeky about it). However I never liked Star Trek and whilst I read Science Fiction / Fantasy the whole D&D and more mainstream Warhammer type stuff makes me squirm. I imagine that same room would put me off too; unless it had something cool in it (for example a complex lego "star trek" model) that appealed to the engineer in me.

I know a fair few CS majors - most are men. But there are easily as many women as hardcore star trek style geeks. Some of the most hardcore geeks are women.

I really think this is a lot more complex than star trek :)
One can train his/her fingers to press those small buttons precisely with some exercise & learning. Remember we all must learn to use any novelty. There are some really fine muscles on fingertips which are adjustable to perform any task.
Some sort of layout problem with your footer when the browser window is a little short. The footer overlays the pager area. Works okay if the window is tall enough, or short enough. Only causes a problem if just a little short.
This is with Chrome 4.0.249.11.
Large Hadron Collider roars to life
Why not target both IE6 and IE7 users to upgrade?
Definitely try to speak to the PM.
Javascript is my favorite language, but building very large systems composed of interdependent modules is still very tricky and everybody does it differently (especially when you leave the browser and talk about the various server-side JS offerings).

The problem is that various ECMAScript standards committees never really considered "programming in the large". The CommonJS project is important because it aims to fill this gap and create a real JS ecosystem by:

1) Creating a standard for interoperable modules that handles scoping (i.e. module X can't mess with module Y) AND dependency resolution.
2) Attempting to define a set of standard APIs for binary data, files/sockets [streams], and anything else that you might want in a good standard library.

I encourage everyone who writes a lot of JS to join the CommonJS discussion group. Currently, the module API spec is mostly complete (and there are a good number of working implementations). The hot topic now is the Binary data API, which is extremely important because it will be used as a base for all subsequent modules that want to manipulate binary data.
Though one wonders what the dollars would have done in the private hand, if they had not been taxed away in the first place.
Pork grown in laboratory
If this were true we would see a reduction in visit times, costs per visit, patients per doctor, patients per nurse, medical errors etc. Instead we see the opposite.

The point of the research is that none of these benefits are supported by the data we have available. Individual anecdotes are the exact opposite of what we should be thinking about after reading this paper.
Just signed up, smanek :-)

Looks well polished. Try to let business owners upload their own offers, that will make it easier for you; instead of hunting for bargains or waiting for users, you can just buy a mailing database and do a blast to those who care (or scrape the contact emails from Google Local, like I did.)

Also, try to define "bon's" somewhere; does it stand for bonus or coupon? The tag line could explain "shop. save. share <whatever it is we're sharing>"

One more thing, spill the beans on the architecture ;-) what do you have behind nginx? Hunchentoot? The html source doesn't look like cl-who, it has comments, perhaps a template system of sorts.

I already have most of your site's functionality somewhere in my private repo, and I am sure many people do too. It's a pity we all have to write it from scratch.

Cheers and good luck! :-)
>... forensic science has become linked with the CSI TV show ....

Indeed, this is commonly referred to as the CSI effect: ( http://en.wikipedia.org/wiki/CSI_effect ).
If their basic data manipulation utilities are written like this, one wonders how the source of their climate modeling software looks...
I have a friend who manages a hospital IT department.

He said that problem is that American private hospitals already are highly computerized, it's just that the computer systems are focused entirely billing and not at all on medical records management.

When they decide to get an EMRS, hospitals turn to their billing software vendor to provide them with something integrated with their billing systems. The vendors tack something on to the billing software without adequate requirements gathering amongst the actual nurses who will use it, so the result is a system that simply does not have the proper workflow for managing patient medical records.

While EMRSes like the Veterans Administration's VistA program exist and are well-liked by nurses and doctors, they provide no functionality to ensure that you get billed $20 for each tongue depressor used. That functionality is, of course, of primary importance to private hospital administrators. So effective EMR software gets passed over unless it integrates with hospitals' existing billing infrastructure, and the hospital billing system vendors build terrible EMR software.