skysight-inc/HackerNews huggingface dataset:
More important is who you write for. Different audience-writer feedback systems optimise for different things. Pithy, data-heavy, and ephemeral HN comments won't port handsomely to a foreign policy op-ed, which values flow and lucidity less than brevity.

I am most proud of my short essays, often on humanitarian or mathematical topica, emailed to a few close friends, colleagues, and academics. Perhaps this is out of nostalgia given how much my long-form writing has degraded over the years.
Trqditional roles are really quite a weak notion. There is huge variance among parenting styles across the population.

Just no being a drug-addicted and not having a debilitating mental disorder is enough to be an above-average parent.
MS becomes so hateful with the secure boot trying to control everything. I will never buy any machine with secure boot enabled and will boycott any MS product.
Private companies / IPO research firm PrivCo actually foresaw all this in 2011 pre Groupon IPO. Boy were they right. Just looked up some of the research I read then that made me a believer to avoid Groupon stock and its IPO. A taste, pretty good crystal ball, good solid analysis of the numbers:

http://bit.ly/Y3hfft

But firing Andrew Mason does not fix Groupon's problems, whose business model is fundamentally flawed. And the problem now: Eric Lefkofsky's Super-Voting Stock (many times public shareholders) means he's still the same guy in control, though now has the CEO title too. So nothing will improve at Groupon. Andrew Mason was only a puppet CEO. Lefkosfky called all the major decisions. IPO investors: boycott ALL IPOs with supervoting stock! This is exactly why! Shareholders should be booting Mason AND Lefkofsky. (Zynga has the same problem: Mark Pincus gave himself 70x-to-1 supervoting stock before the Zynga IPO...stock's down 70% from IPO in barely over a year, yet you can't get rid of him). Don't buy these IPOs. (Also some thing PrivCo and others have advised clients, and I'm one of them.) No matter how tempting the IPO sounds, don't do it. Go on to the next IPO...I'm an active IPO investor, and there are always great new ones on the horizon....just wait for the good ones.
Read the article, it's not about exiting it's about what tools we use to make our lives easier as founders. Thanks for the blind comment though!
Whoa, this isn't a puppy.

You don't adopt a child when you have a partner without even mentioning to them, let alone discussing it.

I mean that's insane, and I don't get the downvotes.

Who the hell adopts a kid while in a long-term relationship without even asking their partner?

It's all good because it turned out okay but seriously who does this? It's a massive life-changing event. You plan these things, otherwise it shows a complete lack of respect.
Oh man that is some sweet irony.

Just wait till the next waive of spam from SEOs trying to get competitors penalized then the competitors firing back and contacting you. Google stirred up a hornets nest because they couldn't figure out how to effectively devalue these links completely.
+1 for strong editing features. All the fancy stuff came after Emacs became an OS for editing text. Nail that, the rest follows.
Interview with HubSpot Founder, Brian Halligan
2012 Interview with Brian Halligan, co-founder of HubSpot. Produced / compiled by Latif Alam.
Racial social identity in inter-racial families is a hugely important issue, and ignoring it is deeply harmful to a child, who faces harassment from peers and strangers, internal confusion, etc.
Ahhh... I see I was mistaken. Both are projects by Armin. I thought Psyco became PyPy
Later books by the author suggested "one less hamburger" would do a lot and, iirc, about half the book is about her research into how foreign food aid made locals dependent on diets they could not afford and stuff like that.
3 hours left - Support Redline Smalltalk
for domains I'm actively using, I use Route53. For domains I'm not actively using, I don't mind name.com is parking.
$25 IPO stock about to become an OTC stock.
As a Swiss I'm curious how the name has come to be. Is the team related to ETH Zurich?
This is very neat. Imagine if you are trying to tune the server parameters, the instant results from the service gives you a quick feedback on how your parameters are effecting the throughput. Very nice indeed.
I think the general fund is the most important option right now. I don't actually want to end up deciding who gets my money, I'd much rather see donations spread out among people who need them, based on medical urgency if possible (as opposed to who is most photogenic or who has the most touching story).
Have you been residing in the U.S. doing independent contractor work and selling support for your open-source projects from the U.S. to other U.S. states, Germany, Australia, G.B., etc.? If so, let me know, and I'll definitely send you something. It would be terrific to have help!

I'm more interested at the moment in just basic things like the legalities of dealing with these states, if I really need something to help with the various sales, etc. taxes and what kind of plan to get or whether I can farm that out via some reputable e-commerce solution that handles these things already, how to make contracts and quotes for these companies. How to translate "work for hire" and "you are not paying me for copyright for code I write in this open source project". Whether I need to be incorporated to do business with them. I know LLC is primarily to write off taxes, and that I'm fairly sure that I need business insurance, because I don't want to lose my life savings in a lawsuit.

Basically, I need an accountant with lots of U.S./Int'l experience, an international lawfirm, a psychoanalyst, a friend with similar experience, and a few advisors.
They mainly use a program called xrumer to spam and it mostly works with your typically install of vbulletin or other popular forum software so custom software won't get hit. Kinda security by obscurity.
Nail.head.hit
The defense of honor was a kindof tongue-in-cheek response.

The reason I posted this here is that I think it speaks more to a systemic problem with open source.

The great thing about OSS is that it's always possible to fork, but then you're fragmenting communities and investments in time.

I really wish github (and OSS in general) was more democratized.

Every popular repo out there has half a dozen PRs sitting open -- some of them good, a lot of them bad -- but code rot is alive and well in the node.js community and there is no reason for it.

> It is not a reasonable to assume that others are
> obliged to work with a pull request submitter.

I do disagree with this. If you're going to release software publicly, then it's your responsibility to make it the best software it can be, and if you can't, you need to hand over the reins.
Free market, democracy. Federal regulations and banking regulations. That's my point, actually.
And? I would probably fail way sooner, and that wouldn't mean that making a funny departure letter should save my ass if I misled people.
Aaaannd cue internet vigilantes: http://cjwworld.cu.cc/?p=216#comments
Pretty over-the-top. Best line: "It might just be one of the biggest 'bet-the-company' moves to create a culture of innovation that we’ve ever seen in Silicon Valley."
I'm in a bright[1] office with an rMBP. I'm imagining everyone with displays that give less brightness / contrast is going to have a bad time.

[1] It's a Japanese office. These people really like their cold bright neon. I think it has to with dark east asian eyes.
This argument comes up every time somebody suggest an unpopular tool, and I think it's inherently flawed. The core problem is that popularity does not imply--and does not even necessarily correlate with--quality! Just because something is in some real sense better does not mean people will adopt it.

Most people are not willing to learn something fundamentally new. They might be content going from something they know to something very similar, say Java to Python, but they will resist anything truly novel and different. And the others? They're mostly the ones already advocating Haskell or Lisp or Forth or what have you!

Also, people have some really odd reservations when switching to a new technology. They are often not willing to take any visible steps back: the new might be better in a whole bunch of non-trivial ways, but if it's obviously worse on some easily identifiable property, people will avoid it. A new language might have a long list of advantages, but if it has an inefficient default string type, or slightly wonky syntax, or a sub-optimal packaging tool or any other superficial but obvious shortcoming, people aren't willing to make the switch.

Another problem is that there are different kinds of productivity. There are "dense" productivity changes: if you have to write your own JSON library or deal with a broken build system, you'll be spending a contiguous amount of time on it. You'll have to devote maybe a whole day or even a week to getting around this problem. There is no way to miss this. On the other hand, if a language improves productivity in a "sparse" sort of way--say you spend 20% less time writing code and 30% less on debugging and maintenance--you won't notice quite as easily. And yet, over any reasonable time using the language, you'll come out far ahead even if you have to sink in days working around problems and libraries.

A particular--and particularly important--example of this is in learning. As I said above, one of the main reasons people resist new technology is that they don't want to learn. They're too busy to spend a whole week or even month picking up something new. And yet, learning time is essentially a constant expense. Productivity gains, on the other hand, are at least linear in how much you program. If a language makes your code simpler, the gains can even be super-linear (that is, you get more benefits as you write bigger programs). These will dominate any learning time as soon as you actually start using the new technology widely. And yet, since the amount of time spent learning is obvious and the ambient productivity gains aren't, people put a larger than warranted cost on the former.

Coincidentally, this does not only apply to programming languages. I've seen exactly the same sort of behavior in adopting any kind of new, non-trivial technology: Emacs, Vim, Git, Linux...etc.

In short, don't trust popularity. This probably makes me sound elitist (and, to be fair, I probably am), but it's just like music or literature: the popular stuff is usually not particularly good and the good stuff is usually not particularly popular.
In the future, browsers could also do xz; they'd just need to advertise it in their Accept-Encoding header. Google could put this in Chrome any time they like, and nothing would break.
"None of this shit is easy, and no one is going to handhold you through the process."

Thanks for giving the straight up answer on this.

We all love to read about the people doing it but the reality is that the time and effort that is really involved is just tremendous. I am reminded of the story of a person asking a famous piano player that they would really like to play like them. The answer that was given to the person was - "No you don't. You don't want to be sitting in front of a piano for 4 hours every day for years, practicing and practicing. You say you want to play like me but you can't/won't put in the time to get to my level of skill."

We all like to read about starting a company but at the end of the day, no one but you is going to get you out of that couch. Especially this notion of "I don't have a an idea". There's a simple answer to that. Make that your intention, make it your job to get an idea.

I love James Altucher's daily practice : http://www.jamesaltucher.com/2011/02/how-to-be-the-luckiest-...

Just spend time every morning coming up with ideas. Heck there's going to be hundreds of shitty ideas coming out but at some point there might be something akin to nugget of gold in there. Even with that nugget, not much will come of it, if its not cleaned, processed and made something of it. It's the same with the idea, go ahead and apply Steve Blank's methodology on it. Maybe in a span of one or two years, you went through a handful of junky ideas that didn't turn into anything (and hopefully not much was lost - especially if you followed Steve's approach) but perhaps you might have enough of a business to work for yourself and have a couple of employees.

Now, does this mean that if you follow this approach, you will succeed? Who knows. That's the beauty of it, the journey is the fun part. If you've done it right, you might succeed gloriously (but please, don't think you can be the next Dropbox, Groupon, etc. bringing home 200-500K net income from your business for yourself is a very comfortable lifestyle). Just don't fail gloriously. Baby steps, until you know that the big step you want to take (such as quitting your full time gig) will have a good outcome.
Asking for the nations paper of record to use English properly isn't so bad.
You're right, and it should be just "follow your dreams".

Doing your own thing has a lot less to do with it, and just happens to be a part of my dream.

Also, I'm not exactly "doing my own thing" -- I'm simply getting to work with a team that's a lot better at making our collective "dreams" a reality as compared to our respective previous situations.

Sorry for the 1-sidedness -- and you're right about there not being much analysis to the thought. This was a more personal, than logical, post so please take it as only such.
The hosting companies I've used (eg: Linode, Dreamhost for smaller projects) all provide DNS services. I trust them to manage a DNS infrastructure more than I trust myself.
Drone Journalism is coming
A lot of solutions simply mean breaking down a problem into further derivates than you think.

"becoming attractive to VC's" wouldn't be a solution, there are about 100 details you'd have to get right first. Brainstorm those details and focus on them, instead of the goal that ends up being a summary of those details :)
I love how candid he is in this letter. Good stuff.
15 awesome chemistry GIFs
Why Ruby devs should be looking at JRuby
A tiny suggestion: the field where you type the route should say "Or type it and click go", not just "Or type it and click." It's a little clearer. I see that you fully spell it out at the very top, but I skipped past that, and I suspect a lot of other people will, too, because it's so small.

This is impressive, though -- good job.
That sounds very interesting. I wonder what kinds of transforms would improve compressibility by DEFLATE. I know a bit about PNG's predictors, but not enough about DEFLATE to confidently guess. If you ever work on this, please let me know. I'd like to collaborate.
I'm in the same place you are, and this book is helping me out: Design for Hackers: Reverse Engineering Beauty[1].

I'm mostly interesting in typography and color and this is a great read that covers all that and more.

[1] http://www.amazon.com/Design-Hackers-Reverse-Engineering-Bea...
I liked it too, but I almost went blind when I came back to HN.
I'm curious why he was "fired" rather than given the "opportunity to resign."
Kim Jong Un watches basketball game with Dennis Rodman
Compress data more densely with Zopfli - Google Developers Blog
Good point. But I wouldn't say it's more important, for the simple reason that you can write for the wrong audience or with the wrong tone, and still get writing practice and slowly sharpen up your writing skills.

But if you don't know what to write about, you might very well never get started at all.
That's solarized dark. I actually just switched to it for my personal blog because I really like it. Apparently I'm not alone. I spend most of my day in a fullscreen terminal with a solarized dark colorscheme with AnonymousPro as my font.
In fact, admitting you failed may be even harder when you're accustomed to being wealthy and in a position of command.
Not at all. http://en.wikipedia.org/wiki/John_Birch_Society , the Ron Paul fans, and anyone else against the Fed.
I'd like to think that the judge in this case was (very pragmatically) wanting to avoid having the infant in foster care for any longer than necessary. I'm happy that it seems to have worked out.
Hey, that's sharp.
Lode Vandevenne wrote the blog post and the code. LinkedIn says he works at Google Zürich.
Or here's a novel idea: instead of looking for things to write about (like, “My Top Ten Rails Tips” or “How This Single Mom Made Bank From Home Only Three Hours A Day”), why not just only write when you have something to write about?

That is to say, wait until you have something that is so important or cool to you that you have to show the world!
The difference between the popularity of Emacs, Vim, Git, Linux, and a programming language is that it doesn't matter if anyone else on the planet uses Vim Git, etc., they will work the same to me. But the difference in productivity from pre-made libraries for using Ruby (52,220 gems cut since July 2009) vs. scheme (http://planet.racket-lang.org/) is vast, especially when you consider that the power of the two languages is not that great.
As Jach points out above, Mozilla has had a bug[1] open about it for 6 years.

[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=366559
How cloud and Big data might win the hacker war
I think this roughly reflects my philosophy in languages as well. You basically have two options: you can bend your problem to your language or your language to your problem. The former is epitomized by Java and Python--all Java and Python code looks the same, regardless of what it's actually doing. The latter is the domain of Lisp and Haskell and Forth and so on.

I'm unabashedly in favor of the latter.

Ultimately, it's easier to reason about some domain in that domain. I would love my code for any particular project to look very similar to what I would write on a whiteboard when solving the problem. If I'm solving something inherently mathematical, I want the code to resemble math notation. If I'm writing some parsing code, I want it to resemble a grammar. If I'm writing an interpreter, I want it to resemble the operational semantics of the language. This fits into more "practical" domains as well: if I'm writing a web app, I want the routing to look like, well, routing and the database code to look as close to the database structure as possible.

Any details in the implementation rather than the domain should be separated from the domain logic. If you're trying to make the domain logic mirror the domain itself, this is essentially inevitable. This makes your code more general and easier to debug. You can redirect your domain logic to a different backend, and it's much easier to figure out whether you have a problem in the implementation or the logic.

More generally, such a strict separation of concerns is extremely important. The difficulty of a problem increases exponentially with its complexity: all the parts affect each other. If you manage to neatly split a problem like this in two, each sub-problem will be less than half as difficult as the main problem. So splitting away the high-level logic from the IO and the memory management and the other implementation details is inherently valuable. In fact, this is valuable even if the sum of both sub-problems is a bit greater than the original problem.

The malleable language approach gives you a very natural way to split your problems up: one part is implementing the DSL, modifying the host language or writing a library--creating abstractions. The other part is actually using these abstractions. I find this sort of split to not only be very useful but also very natural; it mirrors how I usually think about things.

One very interesting recent development taking this idea to the extreme is OMeta. There your program is essentially a tower of DSLs, with the base language just being a simple way to specify the DSLs. This idea really is extreme: for example, the code for implementing TCP is actually the ASCII art diagrams describing it! [1]

Of course, all the usual suspects like Lisp and Haskell are also worth looking at. Embedded DSLs in these langauges can go quite far, and they have some of their own advantages to consider.

[1]: http://www.moserware.com/2008/04/towards-moores-law-software...
Full-text search for your Twitter archive (Go + AngularJS + PostgreSQL)
I actually clicked on the comments to post how much I enjoyed the experience of reading the post (though I was going to put an "off-topic" disclaimer. To each his own, I guess, but I really enjoyed the reading experience of the theme.
I see your intention, but the issue is not this post alone. Take a look at minm's comment history and you'll see 90% of his posts are promoting Tonido: http://news.ycombinator.com/threads?id=minm

I didn't downvote his post at first because it sounded like a genuine suggestion. I consider myself deceived.
Ask HN: How can I realize my dream of working for Google with a limited resume?
I'm a talented 20 year old developer from portland with 10 years of programming experience, but only 2 years of realistic things to put on my resume. I've known for a very long time that working for Google was one of my biggest life goals, but feel right now that I'm stuck worrying about ruining my chances by applying with a resume that truly doesn't showcase my full talent or ability.

I'm currently working for a portland startup where I am not undervalued, but I feel somewhat trapped.

I know where I'd like to work for Google, I know what I'd like to work on, but I can't seem to get any google employees to give me any solid direction beyond "submit your resume".

What do you guys suggest?
This is not a good idea for a simple reason: you need the practice.

The only way to get better at writing is to write. So I strongly suggest you make an active effort to regularly find things to write about, instead of just waiting for inspiration to strike.

Now on the other hand that doesn't mean you necessarily need to publish everything you write. If it sucks, keep it in your drafts folder and maybe revisit it later.
Morris Worm Incident Report #1 (1988) [pdf]
By design, Watsi will never "make a dollar".

As it is operated by a not-for-profit company, never making a dollar is part and parcel of its purpose. Hopefully it also helps many people in the process.
You should run it by a lawyer. Legal documents like confidentiality agreements often (re)define terms like "knowledge" and depending on what you signed when you joined up, you may be in violation of it. Better be safe than sorry.
You can already get 3% more compression out of zlib by giving it a bigger dictionary like 7zip can optionally do.

code.jquery.com/jquery-1.9.1.js

original 268381

gzip 76070 (32KB dictionary, 128 word size)

Zopfli 75730

340 bytes is not worth a 20x time increase for compression.
I'm really surprised that integration with external credit cards (and banks, but especially credit cards given their importance in the US) isn't on the top of their priority list. I understand that they'll miss out on the extra data they get by being partnered with their bank, but it would let me drop mint.com with its dated ui, and make it much easier to use the goals mechanism (and daily spending limits would be a lot more relevant). Alternatively they could just launch a Simple credit card, give me 1% cash back / rewards and I'd feel comfortable moving most of my spending onto their card, which would let me continue to maintain my credit score and extract a bit of that merchant fee.
"There's 0% chargeback risk with Bitcoin"
That is problematic for much of what currency is used for.

"and 0% risk of fraud"
This is completely untrue, because it assumes the motives of both sides of a transaction.
xz is essentially LZMA2. It definitely beats bzip2:

http://pokecraft.first-world.info/wiki/Quick_Benchmark:_Gzip...