skysight-inc/HackerNews huggingface dataset:
Relevant:

> I’m not trying to cherry-pick data. I’m simply observing, based on Apple’s sales data and Google’s activation data, that the tablet market doesn’t today look anything like the smartphone market ever did. The iPad didn’t enter the tablet market. It created the tablet market. The iPad’s role in the tablet market much more closely resembles the iPod’s role in the digital music player market a decade ago than it does the iPhone’s role in the 2008 phone market.

> http://daringfireball.net/2011/07/ipad_dominance

> There’s an iPad market, and the iPad could be classified as a tablet, from a hardware-centric viewpoint. But the market for non-iPad tablets is about as big today as it was before the iPad, which isn’t nothing, but it’s close enough to nothing that Apple doesn’t need to worry about it.

> http://www.marco.org/2010/12/31/there-really-isnt-much-of-a-...
The same incentives apply to long-haul truckers and international passenger bus drivers - but there somehow regulation works, and they're not allowed (at least in EU) to drive nearly as much as airline pilots, due to the same fatigue concerns.
It's trivial to deny airlines the possibility of scheduling pilot shifts with '5 hours sleep in the last two days' as in the original article - the regulators simply have to do it, and as it will apply to all airlines, then even the low margins will accomodate the extra cents needed for less flexible scheduling of pilots.
How to Win Friends & Influence People by Dale Carnegie has been recommended to me several times

http://www.amazon.com/How-Win-Friends-Influence-People/dp/06...
You're absolutely right. That people could hold these two ideas in their head at the same time still boggles my mind:

1) Tablets are the future of personal computers
2) The tablet market is more like the media player market than the phone market.

This was absolutely a popular belief just a couple of years ago, although the people who said this have become quite silent.
Semantic UI Style Grids in Zurb Foundation
FWIW my biggest intelligence boosts are as follows: sleep, exercise, proper diet, no depression.
Please offer some kind of reference supporting your claim that the arm chip in the iPhone 5s is power inefficient.
I'm too honest to go down that road.

And as I understand it, Finnish people tend to pay their taxes proudly. (Might have something to do with the majority of their workforce being employed in the public sector.)

So I don't think this will really be an issue anyway.
Strange. I did some research and found some numbers.

The energy density of Kit Kat is 22 MJ/Kg (5.2 Kcal/g) http://www.wolframalpha.com/input/?i=%28Kit+Kat+calories+to+...

TNT has 2.8 MJ/Kg in an explosion and 4.2 MJ/Kg in a combustion. It has too much Carbons. In an explosion, it doesn’t react with the oxygen in the air, because it’s too fast. There is an interesting discussion in http://en.wikipedia.org/wiki/Trinitrotoluene#Energy_content

In general, the explosives have to explode without using the Oxygen in the air, so they have a lot of Oxygen and Nitrogen atoms inside. The fuels for slow combustions can have almost only Carbon and Hydrogen atoms to store the energy more efficiently and get the Oxygen from the air.

Nitroglycerin has less Carbons, so has more energy density. Mixed in dynamite has 7.5 MJ/Kg and alone has 6.4 MJ/Kg (Is this correct? I expected a bigger value).

I found a list of these values for a wide range of materials. In particular it says that green wood has 10 MJ/Kg, air dry wood has 15 MJ/Kg and oven dry wood has 20 MJ/Kg. http://physics.info/energy-chemical/

Other values: Gasoline ~45 MJ/Kg, Methane 55.5 MJ/Kg, Hydrogen 142 MJ/Kg
> That's not how TDD works

if you are looking at Ron Jeffries Doyen of the Agile set, and saying "well of course he did not get the results, he was doing it wrong" the we are well into id-protecting, religious territory.

if one of the leading exponents gets the process wrong there is something wrong with applying the process to the real world

TDD really seems to me to be two parts:

- Design up front, disguised as writing an API

- Ensuring you write repeatable tests before commuting
That illustrates a very serious problem with TDD, the idea of coverage.

100% code coverage is not 100% coverage of every different possible code path. In fact, for most software systems it is not even remotely feasible to achieve that level of code path coverage. The "100%" figure can easily lull less experienced devs into thinking they have sufficient test coverage when nothing could be further from the truth.
Top 5 Best Windows Phone 8 Messaging Apps You Can Download
Noone was saying anything about shameful professions; but, just like if I was a passenger in a sail-ship, I wouldn't like the ship captain to interrupt whatever I'm doing in my cabin to state what is the wind direction today; I wouldn't also like the air-ship captain to interrupt the movie with the notification about airspeed and air temperature up in the sky. Let him worry about the majestic flying, and let the passengers mind their own business.
As a Romanian I feel compelled to say that we're far from the poorest economy in EU/Europe. Romania is still a standard Eastern European/post-communist hellhole (although slowly improving), but not _that_ poor.
What were you using for python tests. I used nose on a project[1] and it seemed to do everything I needed.

Your second sentiment is the exact same thing that happened to me. I got that revelation moment where I'm like "holy crap" we made changes and merged everything and it's actually working. Which, sadly, wasn't the case before we went into the TDD model. I mean even if the test cases were added after the code was written, I still noticed a lot faster development cycle and a lot fewer bugs on the projects that were using TDD.

[1] - https://github.com/joeblau/sample-url-shortner
Heartening story, but I can't get over this line they stuck in at the bottom

>• Blue lights installed at train stations have reduced suicide by 80 percent at those stations. How or why this works, nobody knows.

I can't stop thinking about this. I've tried to puzzle out some type of reason, but I'm just not getting anything.
TDD is like any other tool. Abuse it and you'll get terrible results, use it well and it will save you time and effort over the lifespan of a project.

The big tricks are: test modules on interface boundaries, tests should test one thing and one thing only, don't overdo it and realize that tests are code and will need some maintenance.

Then when refactoring time rolls around you'll be a happy person.

If you overdo it or test in other places than at the interface level you'll find out that with every change half your tests will fail and that maintaining the tests is more work than maintaining the code. Tests will be 'brittle' and will test code at a level that is not useful.

Too much of anything is wrong.
Wait, wait. So in a quarter where the newest iPad is 6 months old, there were less iPads sold than every Android tablet manufacturer in the world combined?

APPLE IS DOOMED
My puppy has declared war on unhappiness... he takes it very seriously.
Periodic Table Of States
After 140 years, time called on European Rail Timetable
Smart ad.
I suspect it is done with higher order functions in a manner analogous to what Rich Hickey has done with map and reduce here:

http://www.infoq.com/presentations/Clojure-Reducers
For those who do journaling: how do you do it?

Paper? Software? Either way, what kind of system do you have for organizing your notes?
Habari mpya
I used a Logitech Trackball for more than a decade due to De Quervain syndrome. My specific experience in this topic is that the TB allows for high speed macro motions (RTS control), often easier/faster than a mouse; but for high speed precision (headshots), the mouse wins every time.
The Inevitability of Geoengineering
I don't understand the claim the the outputted Javascript is hard to read. Whenever I have a problem with Coffeescript, the first thing I do is look at the output, usually in the Chrome devtools. If it doesn't compile, I'll yoink the offending code out and feed it into the linter at coffeescript.org. It is by far the least odious part of my workflow.

Part of me wants to claim that if Coffeescript is getting in your way, you're trying to do too much. I consider it a code smell and start to wonder what needs to get refactored.
Also relevant: the dates of those posts.
Right, Bulgaria is poorer.
if you're inspired by Thoreau, I recommend you check out Dick Proenneke's little film "Alone in the Wilderness".

First 10 minutes here: http://www.youtube.com/watch?v=iYJKd0rkKss
If you want to go more of the Psychology route:

Predictably Irrational (Dan Ariely, he has some TED talks as well)
http://www.amazon.com/Predictably-Irrational-Revised-Expande...

Influence, the Science of Persuasion (Robert Cialdini)
http://www.amazon.com/Influence-ebook/dp/B002BD2UUC
Good open source stack for running Analytics on large semi structured data?
True, though while RMS did not have these things when he started, he presumably did before Linus started.
Symbolic Exploit Assistant (SEA)
Did he try Settings > General > Accessibility > Reduce Motion? I don't have that particular problem but still like that option because several of the motion effects — most notably icon parallax — aren't implemented well enough to make it out of the uncanny valley.
QNX is really beautiful and powerful at the same time..

Its equivalent to a haiku poem of OS code and design

I wish it was trully open source.. maybe now that Blackberry .. (we dont know for sure what will happen to it) they maybe
could share to us all.. so this nice enginnering effort coudl have a great future?

Anyway, just one of the things on my wish list :)
However, TDD encourages – ideally – a style of programming where 100% branch coverage is likely to mean the program is correct.

That's part of the idea of the "unit" in "unit test." You decompose the program into units for which correctness is relatively simple – and testable.

How to do this properly is not obvious, and for teams on which TDD is imposed without this understanding, it will all become a bizarre and useless ideology.

When it is understood, the resulting program will have properties that resemble those of purely functional programs, especially composability and correctness.
In general, workers have achieved 5-day work week for almost a century and the conditions you describe fit a third-world sweatshop. Maybe it's time for USA to stop being a third-world sweatshop for so many its citizens - take a look at the Fair Labor Standards Act you had in 1938, maybe you can try to achieve at least that standard if you pressure your congressmen enough.
I'm tired of people asserting that TDD results in better X, while simultaneously stating that TDD does not guarantee good X. What does that even mean? It sounds like a non-falsifiable statement, that aims to blame the person whenever your methodology fails.

Another issues is that no one ever qualifies what exactly is TDD better than? Better than someone vomiting hundreds of lines of code into a single file with no systematic approach? Better than test-last development? Literate programming? Better than Design by Contract, advanced type systems and static verification?

In blogs, TDD proponents often completely ignore the difference between unit tests and integration tests, pretending that there is none, and that TDD will automagically produce both, even when their methodology does not provide any guidance for designing integration test. (The article does this too: "The test suite, that you grow along the way, will help get those features implemented, and bugs fixed, without breaking other features." Uh, not necessarily.)

And what I'm really, really tired of is the assertion that TDD produces not just more reliable, but better-designed and otherwise better code. What I've seen in real life is that TDD encourages developers to bulldoze through the problem by constantly spitting out code and tests without bothering to think at the higher level. That results in a lot of "enterprise Java" style abstractions and fractured code that is extremely hard to read and debug. (Yes, it's easy to understand what every particular unit does, but it's not at all clear how they interact and why we need all of them.)

Here is a simple example of deficiencies of TDD that uses the infamous prime factor Kata: http://insideofthebox.tumblr.com/post/52002125683/prime-fact...
There is a great question in that article: which solution would you rather work with if you had to modify it?
What can be modelled as a graph can be modelled as sets and relations and vice versa; they're both equally powerful. But just as any two Turing-complete languages are equally powerful, the discussion doesn't end there.

It's still the same problem: you have mixed the logical model and physical structure of your data together. You are privileging one view of the data over all other views.

I consider switching to a full graph model a complicated workaround for the limitations of trees. You now introduce new and exciting paradoxes and you will need to litter your code with special cases (B means C, but only when A is not an ancestor, otherwise it means D). Ask C++ programmers about the joys of multiple inheritance.

In some cases the logical model is a graph and in those cases you should absolutely model it as a graph. But modelling all problems as a graph is inadvisable.
They've had an accessibility setting since release which allows you to reduce motion. It's a surprisingly big aesthetic win since the effects do nothing useful but distractingly fake.
gpg encrypted vim file.
Right, but if you're never going to look at the method again and/or remove it next week for whatever reason, you've just wasted a bunch of time that could be spent on more valuable things.

My thinking is definitely more focused on early stage start ups/personal side projects than bigger mature projects.

But what I'm trying to get across is that I'm starting to wonder if "big clunky code base that's hard to support, maintain and understand" is in the same class of good to have problems for early stage start ups/side projects as "I chose a technology that is tough to scale to 500 million users" as long as you have a comprehensive test suite.
Well, that's more or less what I'd meant by 'focused on "working" rather than "right"' - GNU was trying to do what theoreticians suggested made the most sense; Linus was trying to do what had worked before. Both have pros and cons, but the latter is "safer" and certainly seems to have paid off here.
Can you elaborate about "you aren't really picking up your child from day care"? I believe that if you aren't age- and gender-discriminating, then it should be that a noticeable percentage of your workforce do leave every single day at no later than exactly X'o clock to pick up their kids from daycare, and that is how it should be.
I assume you've seen Dark Days?

http://en.wikipedia.org/wiki/Dark_Days_(film)
The first time I tried to do this, it forever changed the way I write Javascript.
The Problem with Rich People and Ethics
Hey! But why should the author miss an opportunity to justice rage on these chumps to inflate his own prestige and notoriety?
Free Pitch Deck Presentation Template for PowerPoint and Keynote
Only sorta. They've written a TON of valuable code, released and used by millions. They've yet to put together a competitive system of only GNU code, though nowadays Debian does let you install Hurd underneath (I'm not sure how much this breaks, but at least many things work).
We Like You So Much and Want to Know You Better
Nobody is going to get it right on the first try, after decades of neglecting data security.
Apple is far from doomed. But those who were saying that Apple would dominate the tablet market forever were wrong. PS please don't answer "but look at the profits". They will come down too, as it's only right in a competitive market.
I think phrases like "no one" should be understood as no one modulo a small number of exceptions that does not noticeably affect the majority trend. Always.
There must have been some hypothesis or they wouldn't have studied the result. Probably got lost in translation.

EDIT: When an english speaking reporter can't figure something out in a foreign country they often say "nobody knows ..." but really they mean "I couldn't find a source to tell me ..."

EDIT 2: I'm sorry, I didn't realize this was discussed in the movie. I just got to that part. Clearly the author of the film knows plenty of Japanese people and knows this subject well. At the same time there was still a scientific reason for installing them: other posters are pointing out that there have been studies measuring blue light showing it is a "stimulus for acute melatonin suppression" . Interesting!
Is this iOS 4 on the 3G all over? My wife refuses to ever update iOS because she saw what happened to my 3G (it became so slow it was barely usable)...
I didn't check with the literature, but in my opinion, the biggest misunderstanding of TDD is that lots of people take it to mean literary Test-First Design.
As I understanding, in Test-DRIVEN-Design, you are writing the implementation code in PARALLEL to testing code. You write a tiny bit of test, then a tiny bit of implementation to satisfy the test. If you notice something you'd missed previously, you refactor BOTH tests and implementation. You repeat and expand a bit...
Just a bit before I hustle out of here to coach hockey all day (don't have kids unless you want to do the same :)

So Mach's VM was being done around the same time as the SunOS 4.0 release which had Sun's VM system (that implemented mmap() and friends for the first time) as well as Sun's vnode virtualization of the file system. As a side effect almost all of the buffer cache vs page cache mess went away (for those who don't know in the distant past pages were one thing and file system buffers were another. Ponder that for a minute and tell me what's wrong with it. Hint: bcopy()).

I was reading all those papers from Joe Moran and Rusty Sandberg and Steve Kleiman; I really really wanted to work at Sun, to me it was the Bell Labs of the day, so I was slurping in everything I could find to read and think about.

I read the Mach papers and later had a chance to wander through the source code. The best way I can say it quickly is that with some things you don't get it and you wander around for a while and eventually the fog clears and you see the architecture. Sun's stuff was like that, when it snapped into focus it was a thing of beauty. The Mach stuff never snapped into focus, for me. Maybe someone else can see how awesome it is but all I saw was a mess. Yeah, it worked, but so do a lot of messes. The good stuff is architected in a way that leads you to respect and maintain the architecture.

Gotta run, here is betting Bryan C will find this thread and add to it :)
In the spirit of the OP's message, I am bookmarking this page, with Ctrl+D.
Yes, my bad. (They're so damn similar acronyms >.<)
TDD was a step we took to learn how to create testable code that was decoupled and had a single responsibility.
It also taught us that we needed automated user level regression tests.
But, TDD is like training wheels. After you have gotten those things from it, it does start to hold you back.
There have been hundreds (maybe thousands?) of independently operating research groups at Universities and government labs, working since the 1950's all of them studying fusion. None of them has come as close to attaining controlled self-sustained fusion as the NIF. That is the entire point of large grand projects, they do what small groups aren't capable of. Simply because the NIF hasn't yet attained self-sustained controlled fusion doesn't mean its a failure.

What do you think is reasonable price tag for the development of an entirely new form of clean energy?
Scientist determines optimal Starcraft 2 strategy
I have committed professional suicide on more than one occasion by voicing my doubts about the whole TDD and worshipping at the alter of "unit testing school".
TDD works when problem is well defined but complicated e.g. a datetime library. TDD is a tool to get the grunt work out of way and take care of occasional forgetfullness/regression, but beyond that it is a pile of code that becomes more and more unmaintainable with each passing day. I have seen unit testing code which grows into a snowball over a period of time and people wasting their time to maintain tests that they don't know a thing about. IMHO you shouldn't write a single line of code if you can get away with it e.g. if you need to write unit tests for your add(int i, int j) then I guess you have bigger problems to solve.
I always take comfort in something a colleague said long time ago while coming to my rescue in one such outburst "are there any unit tests for *nix, vi, emacs etc, the kind of software I dont see crash very often"

Disclaimer: My TDD worshipping friends seem to do better in their professional lives, which I will shamelessly put down to industry trends/religion rather than the true merits of the methodology ;-) It suits me better...
Gevent looks like a nice system, but as far as I can tell doesn't support Python 3. Does anyone have a sense of when support is planned?
Thanks for providing such a nice post. Article and examples were explained well.
I agree, a developer in 100% control of their site would probably notice something is wrong and either build their own form, use an unofficial form, or re-write their ajax calls. There is no requirement to use the official embedded Subscribe form.

In my case, my product is a WP plugin, so I have relatively little control over the host site. The MailChimp form makes my product look broken (although the affected code is perfectly correct).
I've read the Microsoft paper, and I'm not clear on something:

The paper is comparing TDD vs non-TDD groups... but what are the non-TDD groups doing? Are they test last? Are they ad-hoc? Do they test at all?

Did I misread something?

Also, Greg Wilson's video is excellent.
Wow, he's a really good writer. I didn't expect that to be such a pleasure to read.
Hofstede conducted a study in the 60's 70's by submitting questionnaires to IBM employees all over the world in order to compare the responses for cultural differences.

Japan ranked highest in the world for masculinity, [masculinity-femininity (task orientation versus person-orientation)]

Assuming Hofstede's reflect reality. Could this have something to do with the high suicide rate?

Another musing,

Could it have something to do with Confucian cultures and a great deal of pressure to fulfill one's filial piety?
This movie is great. There is a sequel I've been meaning to watch.
5 Americans who used NSA facilities to spy on lovers
If you are working for months with a bunch of rocks (as the NASA rover team is), then you need a way to distinguish rocks from each other, and to accurately reference which exact rock you mean in both documents and conversation.

Names are more memorable than numbers, and names with some meaning to you are more memorable than random words - that's it.
Ask HN: Are there still Lisp and Scheme jobs?
Optional: if you have one where do you work (country or business) and what do you work on?
Yeah I am skeptical myself, but this isn't definite proof that the site isn't as old as he says, just could mean IA-Archive bot was blocked from indexing up to 2009...