louischatriot

Very interesting thesis. But why did you use the two very specific examples of the factorial and fibonacci sequence? They don't strengthen your (again, very interesting) point but rather dilute it.

I especially like frustration detection. Such a great way to react at the right time and stop a user's anger at the right time. I wonder if this could be possible on computers too, by using an ambient movement sensor or simply the webcam?

tldr version of the article: http://tldr.io/tldrs/50c993061bfffa6a5e000730

Unfortunately (for the labels) this is completeley useless. Even if they managed to block it everywhere in the world, another torrent sharing site would appear right way (and that would be history repeating itself).

tldr version: http://tldr.io/tldrs/50c222ad1a39f34847000d06

I personally don't like pairing very much. I like be in the zone and crank out code. Then I do a pull request and get one of my teamates review the code. He can spot mistakes, show a trick I could have used and so on. I think we get most benefits of pair programming without having to be 2 guys on 1 screen.

Probably just a matter of opinion though.

Very interesting proposals overall, not too sure about the localization (don't most programmers speak English ?) though.

That's interesting, with two caveats: - Many people may be wary of giving an idea for which they see a huge potential, but it may not be a problem for side projects - I don't see what the people giving their opinion would gain. Maybe it's just the thrill of being pitched new ideas regularly?

Cool idea in any case.

I also agree that the most important first step is to find content that's interesting to you. Coming from France (a country well-known for its crappy language learning methods), I learnt english as a teenager because I wanted to understand comic books I had found on the Internet. Later on I subscribed to english speaking magazines such as the economist.

Pirating is part of how I learned to make software. To me it was a game at the time but disambling programs/debugging them while they run was a great way to understand how they work.

You're right we may be posting to many of these these day. That's not pure self-promotion as re really think they help people get the gist of very long articles (remember the immortal jellyfish story?) but of course we shouldn't spam HN.

Yes, the "fear of being perceived as spam" is certainly something we all have. I really feel like stating what our company does would be like "Hey I'm company X trying to sell you Y you don't care about".

tldr versioin: http://tldr.io/tldrs/50bb074fcfbff44a4d000b00

Impressive, hard to believe things such ad "cloaking a building to seismic waves" can actually be done!

tldr version: http://tldr.io/tldrs/50ba19a9cfbff44a4d000441

I can relate to most of it even though I don't work in the Valley. Especially the "make friends and listen to their insights" part. We are friends with a few more experienced team and everytime we talk I learn something.

tldr: http://tldr.io/tldrs/50b76494ada40f0817000160

It seems to me that most of these problems are communication problems. You just got a backing of XXX hundreds of thousands of dollars and don't want to disappoint with some bad news, but that's a poor long term strategy. People are surprisingly forgiving if they feel like you're telling the truth and you're doing your best to make good on your promise.

The scary thing is indeed that most software companies do not have security experts nor the means to hire ones and are basically defenseless against such attacks. Kind of reminiscent of patent trolls.

tldr version of the article: http://tldr.io/tldrs/50b6e4acbb22039977000f5b

tldr version: http://tldr.io/tldrs/50b6a7a7bb22039977000ced

I enjoy writing client or server Javascript (yeah, really!), but some of these new features (such as generators) are something I very much look forward to.

If you don't have time to read this very long (albeit great) piece, the tldr version is: http://tldr.io/tldrs/50b64589bb2203997700060f

Quite a long (although interesting) article. tldr version: http://tldr.io/tldrs/50b62f8abb22039977000471

Here is a tldr of the interview: http://tldr.io/tldrs/50b61713bb2203997700013f

TIL how to use Chrome. Thank you.

Exactly. Offering the possibility to filter out these jobs is not enough, they simply shouldn't appear, because they hurt your platform's credibility. As paradoxical as it sounds, I think you should be picky about the jobs you accept, so as not to be viewed as cheap shitty platform. Nice idea nonetheless, I look forward to see where you're going.

Very accurate points, in my opinion. The money quote: "In general whenever a X-guy enforces solving a problem with X everyone should step back and try to analyse it objectively".

All three of us at tldr.io are coders, so we indeed jumped in the code and built (what we thought was) a great product. We thought the product would be viral, and of course it wasn't. So now we are in a two weeks long "no code" period, and this forces us to go outside of our comfort zone.

I can also answer that as I've a fair bit of Rails experience. This time, we built our API using nodejs/expressjs for the first time, so we had to learn it plus the ins and outs of handling user login, sessions, CORS and a lot of small things Rails does for you. So we wouls probably have been faster with Rails.

If we need to build another product from scratch again though, we'll definitely be faster with nodejs. I understand that nodejs programming seems strange/hard to do in a non-spagetthi way to some people, but really, after a few months it is not hard.

Totally agree. The simple question "do I really fear doing that" is very useful too. I quit my management consulting job to start a company when I asked myself this and answered "anyway I'll always be able to live comfortably so why not"

Exactly. It's so easy in fact, and so amount of SVG you need to learn to build great graphs so small that I almost never rely on a high-level graphing library (e.g. Highcharts) anymore.

We really didn't make the choice to prepare for millions of users. We like having complete control over our code, and nodejs+express gives us that. I'm sure we make some mistakes Rails would correct for us and we take a bit more time on development, but we also learn a lot.

That's a tradeoff, and overall we're happy with it.

Good guidelines overall, altough I find that learning 5 client MVC frameworks may be a bit too many :)

Challenge accepted: we have an API up and running at tldr.io :) We don't have a gazillion hits everyday for sure, and it may not be as complex as Twitter but: - It works perfectly - It really wasn't that difficult to build

Interesting project, but if you're only building an API, using a much more lightweight combo such as nodejs + express seems better.

Probable mistype, you mean tldr.it right ? Just saying that as a cofounder of tldr.io, whose goal is similar to that of SkimThat: provide human written summaries ;)

Nice article, and really stresses the tradeoff between flexibility/control and development time. Being control freaks, we use plain old Express at tldr.io , it's true that you need to tie everything yourself but in the long-run I think we actually save time by knowing exactly what we do and why we do it.