eperoumal

I so much feel the same. At the time I was writing Perl, each line made so much sense, as if I was speaking my mother tongue. It was clearly an extension of my brain. Never had that feeling with any other programming language, and it took me years to eventually let Perl go and try to wrap my head around Python.

Can you please elaborate ?

How do you plan on controlling fake profiles ? For instance, if I create a bunch of fake profiles linked to a real profile and I post randomly on some fake profiles, access posts from fake profiles from the others, what could be preventing me from doing this (and keep all the advertising money to myself) ?

"Jesus, what does the fox say ?"

soooo not signing up !

For all the reasons mentionned in this thread (interface consistency, performance, ...) hg is far superior to git. But, as long as git would get the cool tools - namely, gitlab / gitlab-ci - people won't bother looking at hg. I started a new project with collaborators a month ago, we had to chose git mainly because of gitlab, as it would ease the process of managing consistently our codebase in a visual and simple way, not to mention the continuous integration goodness that comes with gitlab-ci. There is, to my knowledge, no close equivalent for hg.

I would definitely add "Nudge" by Thaler & Sunstein to the list. It really helps understand how people choices are motivated, thus how to make good design choices.

There are many companies that use SOAP for historical reasons or because "it's business-ready as it uses XML" (I've really heard this one, trust me).

I'm surprised no one quoted Arrow yet...

Bound parameters with prepared statements is the winning combination in any programming language.

Did you know that "GoLio" in French slang means retarded ? That's a really weird name for a programming language...

Hey HP, you used to have a smartphone, a good one by the way. Does the name "Pre" ring any bell ?

"Debuggers are not like washing machines where you can throw in your code and some soap, go get some coffee and watch TV, and then 30 minutes later the defect is removed." IMHO this first sentence shows that the author has a false perception of what should a debugger do. Above all a debugger is a tool to find bugs in your code, not a box fixing things with magic. Having used extensively the Perl debugger (while debugging Perl, of course), I hardly see any other way to get shit done : you can put breakpoints in your code, see the value of your variables, and so on... largely more effective than putting print statements on the wild, or calling Data::Dumper.

On the opposite, I work in an office with enormous windows, and people always turn the light on even if the sun is bright and shinning outside. SO DEPRESSING.

Good point here, I've run in too many gibberish commit messages. He could also have mentionned "use good syntax and grammar".

Already posted ? http://news.ycombinator.com/item?id=4171401