skysight-inc/HackerNews huggingface dataset:
Ask HN: Family albums in 2012, what do you use?
I'm at the age now where my peers are starting to have children. Digitally documenting a baby's life from pregnancy to kindergarten has created a storage and sharing problem for many -- especially among the early adopter crowd.

I have spoken to some new dads who say they have filled more than 2TB of space already. Shooting HD video and RAW format on that new Nikon seems to have created a storage problem not easily solved by the cloud.

I ask HN -- are you in this group? Do you think the 2TB dad is an edge case?

What are new moms and dads using to manage the family photo album these days given the file sizes, delivery formats, and sharing problems?
"When you're a fresh grad right out-of-college"

It's called being wet behind the ears. Most people in that situation simply don't realize how much they don't know. And guess what you aren't going to be able to read about it and know either. You will find it out through life experience.

The upside is you aren't jaded and you will try things that older people will avoid because of their wisdom and experience.
The last paragraph that should be on top:

"If you’re looking to speed up page load times in your own projects, start by profiling. Then identify the hotspots and defer them until the furthest point of intent — where you know the user is about to perform the action you need to set up."
The ability of trademarks to protect against commercial re-use of intellectual property isn't a good measure of how much they can replace copyright protection. If I write a fantastic book, trademark protection isn't going to help protect me from someone just duplicating it wholesale and changing the name.

Bad things are done in the name of copyrights (and patent protection). That doesn't invalidate the whole concept, it just means reform may be needed.
Sure, but context shapes behavior. People should be eating better too, but that's a lot easier to do when you have a fridge full of vegetables than a cupboard full of Doritos. Test-driven development forces me to think about code from the outside first.
If it were EventBaker (no 's') I'd like that, otherwise I think Amusely. I kind of go with names that are easy to remember and make sense. I know with Eventsbaker I would keep forgetting to add the 's' in there. Example: If you had a site to create and sell cakes would it be Cakesbaker or Cakebaker?
A couple years ago I decided to learn Python. I took a quick look, saw Python 3 was the "latest", and started working on my app, using http://docs.python.org/py3k/ as my guide.

It wasn't until a month later when I went to deploy that I discovered Python 3 wasn't what everyone was using. It was a small app, so it only took me a a day to port it to 2.6.

My point is go ahead and learn Python 3. The hurdles of back-porting are pretty minor when you don't have any version specific habits.
15-year-old Teenager Hacked National Space Agency of Kazakhstan's site
15-year-old schoolboy Murmansk, Alexander was cool hacker. In the summer of 2010, he managed to crack the site of the National Space Agency of Kazakhstan. Hacker is looking for employees with the Kazakh and Russian Security Ministry secret police. And until recently they were confident that they are dealing with adults.
What about NumPy + unittest + all other Python libraries?
Adobe Photoshop Touch & iPad
You might want to check out Chrome Canary. The checkbox has been moved to the left, and there are several other improvements as well.
I use a 2010 MBA (with SSD). Not super-fast, but not ancient either.

I would love to be able to scroll while other tabs were starting their loading!
: HELLO ."Hello YCombinator " ;
It is, but as bug crop up you can add tests to ensure they don't crop up again. While it's not possible to ensure perfection, it does help ensure you don't 'revert back' to past problems.
Where I Am Not Checking-in
I'm going to take you seriously even though you don't deserve it.

Any rip on a state with 50 million people in it is somewhat in jest. Anyway, there are a lot of great things about "California culture". When applied to technology, an open-minded and experimental "Let's try it" mentality is great. Necessary, even. When applied to management without enough attention paid to the fact that some of the people posing ideas have bad intentions, some awful ideas get into implementation and it damages companies. It hurts people. So more conservatism in selecting what to implement is in order, and discussing ideas that might be harmful (with thousands of people) until they've been explored is a bad idea.

The problem with Google is that it's got the conservative New York culture technically (I mean, even Scala isn't allowed) and the California culture with respect to hare-brained managerial ideas like downslotting-- the exact opposite of how things should be.

Put it this way: technological and managerial innovation are utterly different. If you do a tech demo and it's slightly rough around the edges, that's fine. You're awesome for having the courage to put yourself out there. If you're putting forward suggestions that are going to affect the way thousands of people work, the traditionally sloppy (for tech, I mean "sloppy" in a positive sense) tech demo is not how you should be communicating.
I write tests today to make sure it works tomorrow. As projects progress, inevitably no matter what kind of ninja coder you are, a requirement that is beyond what you could have imagined will pop up. You can either say, no we can't do that... loosing a competitive advantage. Or you can can code without fear. Because when you're done, you have a full suite of sanity tests waiting to make sure you didn't mess things up. Unit tests can make an average guy like myself appear to be that Ninja coder those job ads are always asking for, the guy with the oakley glasses.
I do the testcases based on where the project is at that point in time.
Here are the three stages, that can help you decide how much tests needs to be there.

[1] Initial stage where we are trying to make things work. At this stage code base is very small < 1000 lines. This is like prototyping. It works with limited functionality. No tests needed at this time.

[2] Heavy development phase. At this stage, we have proved the concept. Now we are adding a lot of new features. We identified some features as must have. Also, code is getting re-factored/re-designed based on what we learn. At this stage, we add tests for the must have functionality. Thus, we can ensure that important features are not broken by newer code.

[3] Mature phase. The code is mature. Most of the features are working fine. Code base may be large 100000+ lines. At this stage re-factoring/re-designing is not easy. Mostly incremental changes are happening. At this point, we should have upwards of 70% code coverage. Typically, the test code will be more than the code when we have 70%+ code coverage. But, it is very important to have tests, since it ensures that all features are tested even when a minor code change is made.
There are many ways to improve code quality. Using an automated test suite is only one of them, and while it's one that is widely useful, it is of very limited value in some circumstances and I think for some developers it instils a false sense of security. Not having an automated test suite that covers a particular part of your code does not imply that the code is "untested" or of no value. It just means some other approach is needed in that case.
Also several have said they'd apply to YC (they have money, but not startup industry connections, or at least not current ones). Remember, the deadline is March 28th...

I'm pretty sure that after working for Goldman, you don't go work for another large bank, you go work for the Goldman of another field. Otherwise it would be like going from MLB to a farm team -- not an upward move.
Unknown Tech Company Defies FBI In Mystery Surveillance Case
I have also thought about this lately although not exactly in terms of being taken seriously as a developer but I am noticing more and more that, the "publicly seen" portable computer of choice is Mac OS X. In more and more recorded video tutorials, presentations(seminars)- you see the developer using Mac OS X. Sure I know it doesn't matter what you use as long as the job gets done. However sometimes you wonder why a mentor or someone you learn from change from say a Linux box to a Mac. You want to know what tipped the scale in favour of a Mac.
I think it is an interesting point that people get more value out of your product when they are invested in it.

When friends call me for marketing advice, I enjoy talking about it, and am always willing to share some insight for free, but this makes me wonder if I am doing them a disservice.

Odds are, they just resent the advice, or even if they agree with it, how likely are they to use it if it's free.

Seems like sharing ideas and free advice is a lose-lose.

If you really want to help people, make them pay for it!
Are you a UK lawyer? I'm not. I don't feel like I can productively argue this point with you. What I can say is that the citation of that law and the conclusion that O'Dwyer should be tried for violating it came from a UK judge; I linked to the ruling upthread.
Go libraries are statically linked and inlining works across libraries.
The drug companies don't need to shut down trials, they just need to spread their bets sufficiently to ensure there are some winners. Sort of a VC model, except they have a clearer victory condition in FDA approval. Once a drug is approved, the pharmaceutical equivalent of retail shelf space is assured and the marketing machine can kick in to guarantee profitability. And the FDA has little incentive to prevent marginally effective drugs from reaching the market as long as no better alternative treatment exists. Which it won't, if big drug companies can keep churning out pharmaceutical 'hits' without much regard for efficacy. The system is a self-sustaining money machine for them.
The following is a wishing metric:

"If it charged just $10 for access to the update, that would be $150 million if only half of all users wanted an official update."

Few would pay for an update. Especially when the phone is likely to have even more bloatware added each update. Those who would want the update would install a custom rom, especially if it was unlocked by default. The only incentive to upgrade is when someone can't run the next big game.

More importantly, that new handset locks the customer into a new contract. That's the priority. Hopefully some egghead executive will realize that offering software updates, replacing batteries, and reducing monthly fees for loyal customers can earn them even more money.

Along a similar thought, I have very little desire to pay for Android software because developers have a habit of screwing their customers. I have purchased games with zero permissions to avoid adware in the past, only to have updates add a plethora of unwanted and unneeded security permissions.

Paid apps should not be allowed to add security permissions without giving the option for refunds and/or an honest Google code review.
Try logging out and then reading. I'm on iPhone 4 / iOS 5.1. Endless redirects for me, all the way down..
Homeworks? Lack of a sign-up link? Interesting that they have grammatical errors on this page considering their goal here (to compete with other top universities doing the same thing)
Innovation in China: From brawn to brain
>But if you have both IPv4 and IPv6 interfaces, your slower getaddrinfo() calls are probably slowing down your browsing experience.

Disables IPv6 interfaces.

-IPv6 adoption is too low!!
Why would the site owner allow this?
It might be that things never change and all attempts to bring back the good ol' culture are just reactionary, but that doesn't mean people shouldn't speak up when they feel disgusted by what's going on around them.

Fear(s) motivate(s) people pretty well to do just about anything, including to keep silent (as you recommend), but I'm glad that people are brave enough, or stupid enough, to say what they think is right, even in the face of such fears. It might also turn out that the people who agree with the dissenters outnumber the powerful incumbents who they oppose.
Well, that and the 3GS is still being sold. Previously, Apple would retire the phone that came out 2 years previously when they brought out the new model.
One of my friends had a housefire last year. Lost hundreds of books, letters, notes from old classes, you name it.

Not a single document from his gmail archive or dropbox folder was lost.

If I want to keep something safe, paper definitely isn't my preferred medium.
> I believe the only reason 3GS owners got iOS 5 was because of iCloud.

I think it's more because they're still actively selling the 3GS, as their $0 entry-level iPhone.
Actually, when you put it like that, it does sound likely. I am speaking from the point of view of a person who knows very little about these "Kernel wars".
It's important to note that unlike older phones and Macs, Apple is still currently selling the 3GS.

The original iphone and the iphone 3G stopped receiving updates 3 years after release[1]. It's important to note, though, that in both cases the update cycle continued for a significant amount of time after the devices were no longer available in stores.

The original iPhone received its last update 1 year and 6 months after the device was discontinued: iOS 3.1.3 was released February 2, 2010 while the original iPhone was discontinued July 11, 2008.[2][3]

The iPhone 3G received its last update 5 months and 18 days after being discontinued. In this case, given that it had the same specs as the original iPhone except for the 3G modem, I think that iOS was rapidly becoming too resource intensive to continue updating for this device, considering that by 2010 the majority of the hardware was already 3 years old. That said, iOS 4.2.1 was released November 22, 2010, and the 3G was discontinued as of June 4, 2010.[2][3]

Contrast this to Android where some flagship phones don't even receive security updates after even a year (the chart in my references only includes notable Android devices, and ignores cheaper ones that go after the free w/ contract market etc.)

Paying for updates is not the solution. Unfortunately, unless Google or consumers grab the vendors by the balls, the only thing that I honestly think will do anything at all about this situation is a rather nasty worm that manages to do some serious damage to devices that haven't gotten timely updates. I don't want to see that happen, it would really hurt Android's reputation in the eyes of those who won't understand that the HW vendor is to blame for the problem, not Android the OS.

[1] Chart of device updates published some time ago:
http://theunderstatement.com/post/11982112928/android-orphan...

[2] iPhone discontinuation dates and final iOS version: http://en.wikipedia.org/wiki/List_of_iOS_devices#iPhone

[3] Release dates of iOS versions: http://en.wikipedia.org/wiki/IOS_version_history
Dynamodb emulator
First, I am happy that the US does not have laws against offensive speech.

Second: your analogy is imperfect. The defendant isn't charged with violating a UK/US law in the UK. He's charged with violating it in the US. Two sets of judges apparently considered the jurisdictional issue here and both concluded that the harm alleged occurred in the United States, and that O'Dwyer should therefore be tried in the United States.
Cool! I wish I could ever travel there.
Well, you're right. Eventbaker is not available. Thanks for feedback!
But what Apple did to Microsoft and Dell is make a better product, which is exactly what Jony Ive is talking about.
Jasmine is a behavior-driven development framework for testing your JavaScript code. http://pivotal.github.com/jasmine/
"I don't think as a founder at a company that has not yet been funded you have the luxury (time, brain power, etc.) of thinking about these things"

Agreed, albeit to an extent. It's one of those things that must be taken into consideration, because the magnitude of the downside is so potentially massive. But to a large extent, 100% agree with you, it's not something you have the luxury to ruminate on for any appreciable length of time.

Ergo, I'd suggest that the time to do the rumination is whenever a big org shift or financial event is on the horizon (major funding round, new board appointments, major new hires -- especially if there's any overlap with your own responsibilities -- etc.). Each major shift of this nature deals some new cards, and it changes everyone's hand in the game. It's helpful, if nothing else, to take stock of how things will change for everyone before the change takes place.

[Of course, I'm not suggesting that founders become preoccupied with this sort of thinking. That's a recipe for paranoia and a poisonous political climate, and it may end up creating a self-fulfilling prophecy. Rather, all I'm suggesting is that some nontrivial degree of thought be taken.]

Come to think of it, there was a great article on HN about 6 months ago about how to structure a founders' agreement. It seems especially relevant to this conversation. Wish I could remember the title or author.
I believe Jonas is approaching it from his position as a web developer and Django author who's spent a LOT of time dealing with requests from people who've had trouble with PIL and generally only use 8-bit RGB.

I'd be reluctant to condemn a project which is a few days old. Having spent time wrestling with optimizing the horror which is the PIL code, I'd definitely suggest that having a pure Python implementation will make it much easier for people to experiment with API and performance improvements.
It seems to me that less in the way of UI tweaks and more standardization of drivers would solve the problem. Does anybody really buy a phone for Touchwiz or Motoblur? Could some of these tweaks be delivered as apps that can simply target Android releases instead of specific devices (with some sort of basic DRM to keep the average consumer from installing them on other manufacturer's devices)?

It shouldn't be so hard; the PC industry got this mostly right decades ago.
It's pure fiction, but highly entertaining.
I find they do help there. Having unit tests makes me trust my code better. Confronted with a "it does not behave as I would expect" issue, that trust helps me focus attention away from the implementation of those functions.

Problem with that is that, to get that trust, I need to know that unit tests exist, and, preferably have spent time writing or reading them. Question then is whether that time would not be spent better on reading the existing code. I think that, often, the answer to that is "no", but I cannot really argue that.

Perhaps, it is because writing unit tests puts you explicitly in "break this code (that may not have been written) mode". Writing a unit test that calls a function with some invalid arguments and verifies that it throws is often simpler than reading the code to verify that. Also, unit tests may help in the presence of bug foxes and/or changing requirements. Bug report/Requirements change => code change => unit tests break => free reminder "oops, if we change that, feature X will break".
(find-grep-dired DIR REGEXP)

Find files in DIR containing a regexp REGEXP and start Dired on output.
There's a lot of truth to this. I work in a project with a lot of separate assemblies, because we have many applications that share similar functionality. Unit tests are critical to making sure I don't break something for one application while making a change for another. However at the same time, It can be a real pain to load the entire application to test it. Unit tests have actually increased my productivity in some areas where doing a test has about a 1-5 minute overhead (compiling than loading a file etc)
The video provides no additional information. I would suggest you skip it.
Ask HN: To keep or not to keep a paypal checkout option?
I started out with only a paypal checkout option. But, now I'm moving to accept credit cards directly on my site. We had SO many users who did not want to use paypal.

Now, I'm debating on whether to keep the paypal option or remove it. Because of the way paypal express checkout works, keeping both options, will make the UI less than optimal. But at the same time I'm wondering what is the % of internet users who would only checkout with paypal.

Anyone with experience on this issue? What's the percentage of users you had preferred PayPal checkout vs Credit card?

UPDATE:

In my case the UI will be "less than optimal" because on my site you can upgrade several different items and pay for them on monthly or yearly basis:

With PayPal express checkout these subscriptions will have to be separate (the user will have to add/remove items separately going through paypal's interface each time). I won't be able to combine them in one subscription since they only allow 20% increase of payment on each subscription.

With the direct credit card, they will be able to add/remove items on my site and then enter their credit card once.

Combining the above two in one interface while doable will reduce the user experience, and might confuse some people too.
I think you're right. Something like banknote paper --maybe not the same, but in that direction. In some places, I've heard, banknotes are steamed and pressed as they are recirculated, so they look like new.
"New basecamp requires IE9 or higher." They just lost a sale with that.

Finally made the decision to use redmine(http://www.redmine.org/) instead.
Python Language Summit Report - PyCon 2012
Why? Long term viability -- a concept that many large successful companies seem to increasingly, and mistakenly, assume is assured by their sheer mass. This, despite plenty of recent examples to the contrary.

With no suggestion of altruism or the like, it is simply good business in most markets to invest in the satisfaction of your customers. Since they were brought up, Apple is an excellent HIGHLY PROFITABLE example of this correlation to the bottom line -- possibly the poster child of the foreseeable future. There are other good examples to be found, very likely in the form of far smaller enterprises in your own area.

Pleasing your new and incumbent user-base is certainly no guarantee of success, but can anyone produce data that supports the idea that it would be net loss in the long run, all things considered? I mean, if the definition of a business is intent to profit, doesn't it stand to reason that the longer you operate, the more profits you generate? (In the most generalized sense, not discounting the possibly complex specificities of a large operation nor the vagaries of human behavior and progress...)
My personal experience with the highlight iphone app
Even before I deleted my Google+ account, this was a problem for months. As far as I can tell, nobody at Google is seriously approaching major UI annoyance in Google+ - it's all about the flash and ads.

Unsurprisingly, since deleting my account I've had no reason to regret that decision and have enjoyed the complete lack of notification spam.
I'm an emacs coder myself, so I'm wondering.. why no mention of cscope?
To understand why Google isn't what it used to be, one has to understand what happened in 2009-2011. This is the era when Google decided to get "real managers" and they hired a bunch of executives from places like Oracle, IBM, and Intel. If Google had told them to wipe their fucking feet off before tracking shitty culture into the place, it might have survived. It didn't.

You were only there for 6 months in 2011. That hardly makes you an authority on what happened in 2009-2011, or about how the company is managed. Perhaps it's time to consider the possibility that the problem was more with yourself than with Google.
That's not ASCII.

EDIT: Is it? Text files should be readable by everyone, which rules out special characters like "" (I can't even write it).
Why you should get Adobe Shadow