skysight-inc/HackerNews huggingface dataset:
What's also interesting is the bias that appears when the same topic is covered in different languages. Take the English and Spanish articles about the Battle of Vitoria:

http://en.wikipedia.org/wiki/Battle_of_Vitoria

http://es.wikipedia.org/wiki/Batalla_de_Vitoria

You don't need to be able to speak Spanish - just check out the list of the battle commanders. (And if you do speak Spanish, you can see how the description of the battle differs quite radically too...)

I'm not sure what the solution to this and the main article's problem is, though, other than vigilance.
In the end, most people do what they do for the people around them. I suspect that motivation would hold just fine.
1) Self taught from breaking stuff and trying to fix it. Started out creating games in BASIC, then hacked around with PHP and got into writing bespoke plugins for a phpBB community. I also wrote a few patches for OpenTTD and learnt some C doing that. Next I got "The RSpec Book" and learnt about testing and Rails. I then went and did a CS degree, however I feel it didn't really give me anything I didn't already know - I have never needed to know what a red-black tree or hill climbing is in my professional life, although I'm sure if I didn't do it I would regret it [0]. After that got a proper job doing Rails and learnt a lot more from working with others.

2) 2002

3) 2009, although if I didn't do three years of university it would have been sooner.

EDIT:

[0] I think university is also good for life experience, and I still think it holds true that most companies (even non super-mega-corp) prefer people to have degrees.
This sounds really cool. But, personally, is it possible to design a "neat appearance" and more "future"? It seems no difference to other motorbikes in market. As a Superbike, it must be distinctive.
So yeah... not standard.

Assuming they implement typed arrays in their implementation then your criticism goes away doesn't it?
Having written software for Arduino[1], I see this initiative succeeding for two main reasons:

1. JavaScript means developers don't have to understand manual memory management to program their hardware (and many developers simply _can't_ grok manual memory management these days)

2. node.js gives access to the npm package ecosystem - which opens up a huge potential "common lib" to hardware developers (potential because incompatibilities e.g. node.js network support vs luasocket will need to be handled)

Hardware hackers are generally a very curious bunch - they're not afraid of learning a new language on the software side, so it's not really _JavaScript_ per se that is Tessel's advantage here.

Straight to Lua could have been a second choice, but the package ecosystem in LuaRocks is hugely immature.[2] Because Lua execution in a LuaRocks-supporting environment is the exception, not the norm, most developers continue to manually bundle dependencies[3], which again doesn't encourage the package ecosystem to grow.

[1] https://github.com/snowplow/snowplow-arduino-tracker
[2] http://luarocks.org/repositories/rocks/
[3] https://github.com/snowplow/snowplow-lua-tracker/tree/master...
Except I'm not sure how well that would work since it would then be compiled down to Lua...

And of course, C++ isn't exactly a great choice for making hardware programming more accessible. I hear tell that's how a lot of it is done already. ;-)
Isn't the upnp feature of most home routers enough?
Set up a fab lab. It's missing over here.
Whatever javascript does, it does not make Lua's default global variables look any better
Yes, but he's not going to break into your office and knock you out...

I guess the social interactions and the emotions about being attacked contribute to a higher than average stress level. The emotions will be heightened by stakeholders in your organization who look and behave a lot more likely to knock you out or do some other harm to you.
I am "self-taught". Started in 1981 when I was 10 years old and my mother bought me a sinclair zx81 instead of the Atari 2600 I wanted for Christmas. It came with a bunch of games in the form of 3 books. After my initial shock and disappointment wore off I started to input the games and became hooked on programming.

I did study a uni CS and EE for a couple of years, but left because my school was way behind what was happening in the real world at the time. I was consulting in the IT world, and thought at the time that the CS stuff was hopelessly outdated. I realised years later that I should have stuck with it because now I know that some of the theory is universal and timeless and would have stopped me from reinventing wheels a lot.

I've mainly learned by doing, solving problems using technology. I learned in the beginning from books and usenet, then gopher was my friend and eventually of course the web. I still find a good book is the main foundation I use for learning, supported by things such as forums and MOOCs (I've yet to find a MOOC I agree with, mainly because I am personally not a big fan of video learning - I still like books the most)

I've worked on and off in the IT world for 25+ years, currently I am an English teacher, I do IT projects on the side and I'm about to tackle e-learning head on with a new start-up. I would have trouble finding a job because I have no formal degree (people toss my CV/resume) and I am late to the world of github so nowhere to point people to see my work as most of the problems I have solved are internal problems businesses have. So most of my work comes through word of mouth recommendations, and I only take projects nowadays that have an new, interesting angle for me - point in case I am learning NoSQL and Graphing DBs to create a recommendation system for a network of insurance brokers. (I think the problem could actually be solved trivially with Postgres and judicial use of statistical analysis, so I am creating 2 solutions in parallel to see which one will perform better at scale as well as more accurate). I've never done rec systems before, but I'm a big fan of AI and ML, so this seems like an interesting problem to research and look into, as well as having the opportunity to be a little profitable.
Thanks a lot. I do appreciate all the hard work, you are putting into open source community. It's people like you, that make this open source community wonderful. And yes, will surely ask for your help, as my hands are weak in UI part. :)
>I could go on.

You should, and in the way cite some statistics or else you would be falling for this common logical fallacy:

https://yourlogicalfallacyis.com/anecdotal
* I learned from books and some online tutorials. I would use coursera and similar tools, but the were not available in 2000. I made some friends online trough irc & xmpp but beside that i had no contact to fellow programmers during the first 4 years.
* I started to work as a programmer around 7 years later. First i finished school than i worked in an unrelated field for 2 years (great experience).
I am a CS Student, but I have been programming years before I got into college.

1. Self taught from internet resources and experiments. I still remember stuffing my 128MB flash drive with HTML pages so that I can read them at home. Originally got into programming to cheat in some games. Started with making trainers/ memory editing and bot for MMOs.

2. 3rd year of middle school. Around 2005, I think. Accessed the internet for the first time.

3. Not yet. but I have been trying to learn more about the topic ever since I realize whats possible with it, and my decision to learn more seriously about programming led me to taking CS degree in college.
you said "one of the most reputable colleges in India"... and your statements stand true for those kinda colleges... Let me remind you - those are few - very few.... for all the other colleges - I agree with the author - Those "other" kinda colleges are in huge numbers - they produce quantity without quality and as a result many people see India's out-of-college talent "unusable" ... and they result into bad programmers/(engineers/lawyers/doctors/whatever-profession)... and they also result into bad teachers - and the loop goes on...
all of which will exist in 42 years of course
I started by writing BASIC code on my TI calculator in high school. First I just dumbly recopied some sample code in the manual, then I started tinkering with it and adding functionality. I was so bored in high school that I spent most of my time on my calculator writing code.

When the BASIC started to feel too slow and limited I switched to C. I never really learned the language "formally", my original code was filled with GOTOs and local variables (I was coming from BASIC after all). Then with practice it gradually improved. I still fondly remember the "wow" moment when I understood the point of function-local (stack allocated, but back then I didn't know what the stack was...) vars.

Now I write low level C code for embedded systems for a living.
As someone who was lucky enough to be in similar situation three times ($30k, $80k, $200k, at each time - a lot of money for me)

1. There are a few books on the subject on Amazon - written especially for inheritors and by people who professionally help them manage their wealth - go and check them out.

2. Whatever you decide to do with money, keep a journal. I've got a google spreadsheet open, and once in a while I note down all my assets plus all the decisions I make in regards to them.
This has two benefits - one is that it removes a bit of emotion from the decision-making process when you have to write it down. It forces you to use logical arguments.
Second benefit is that you'll be able to get back to your decisions from a couple years back, and either see whether they still hold true, or see why you made a mistake you did.
For example, I bought Nokia shares a year ago. I noted down the reasons for that (WP7 and Lumia being undervalued), and now I see the reasons no longer hold true (Nokia no longer has Lumia)- I'll need to find new reasons to keep my shares, or sell those shares.
Editing Wikipedia Pages for Med School Credit
I learned almost entirely from books. Reading computer books now is an addiction :-) the only real thing I learned from technical college was the very basics of relational databases... And even then when I revisited the concepts I'd been taught a lot of misconceptions.
"Or I may decide to bike home from a nightclub because there are no taxis at 2 a.m"

So, you're biking home without a helmet, after (probably) drinking at a nightclub? Great idea. Enjoy the coma and TBI.
Also, I'd say - disregard anyone who says "20% for this, and 30% for that" without knowing your situation. It all depends on your risk tolerance, your age, your monthly expenditures and so on.
How is Betfair unethical?
No, not really. My point wasn't about a checkbox item on a feature chart.

The point is the language has evolved for quite a long time in a direction very different from talking to hardware. Basic capabilities like the ability to work with bytes are a foundation that a lot of other constructs are built on top of, and adding it in late in the game doesn't undo all that came before it, or provide all that should be built on top of it.

It's not that you can't do this kind of work with JavaScript (obviously you can). It's just that it seems like very bad fit (even if you ignore its history with browsers), when there were a lot of other choices that seem like they'd have made things easier for programmers getting started in this area.
> Hint: if you think JS sucks because of browser incompatibilities, what you really hate is bad implementations of the language, not the language itself.

At the risk of going slightly off topic, this is true only if you have purely academic interests.

A programming language, fundementally, is just a document with a spec (for the sake of argument, let's ignore the languages that have a reference implementation as a "spec"). That spec is all there is to it for PL geeks.

Us engineers, however, we want to use a language. I don't care what's in a spec, I care about whether it works, and how. Whether it works is completely related to the implementations of the language that I need to consider, and completely unrelated to the language spec.

Besides bad JS implementations, Python is a fun example. It effectively has two mainstream implementations: CPython 2 and CPython 3. If you want to support both, you face all kinds of hurdles, much like cross-browser JS programming.
Does this mess badly reflect on the language itself? Hell yeah.
I learned to program in C in the late 80s, before the web, and then went on to do a CS degree at university.

Learning to code was very difficult in those days.

1. There were no free compilers outside of academia.

2. Compilers cost hundreds of dollars

3. Programming books cost $50 each

I used to buy $5 shareware disks that claimed to have compilers and tutorials on them and they never had exactly what was advertised.

In the end I managed to buy a second-hand slightly out-of-date compiler (Turbo-C?). I still seemed to spend any spare cash I had on books.
federated wiki

http://www.wired.com/wiredenterprise/2012/07/wiki-inventor/

HN : https://news.ycombinator.com/item?id=4199260

from the Wired article:
"The federated wiki is an attempt to solve these problems. As a starting point, he has built a new piece of software — dubbed The Smallest Federated Wiki — to demonstrate the concept. The radical idea of the wiki was to put an edit button on every page. The radical idea of the federated wiki is to put a “fork” button on every page."

"The similarities between the federated wiki and GitHub are not coincidental. “The radical code sharing that’s implicit to GitHub was an inspiration,” Cunningham says."
Gartner tells IT shops that it's 'game over' for BlackBerry
I just got obsessed with it while still in grade school and spent all of my spare time learning and trying stuff. I started hundreds of little useless projects, all of them out of my league.

Pre-planned courses never appealed to me at all, maybe because of some slight ADD tendencies. They try to titrate knowledge in a steady, regulated, and pedagogic way. That just bores the shit out me. The only thing that even remotely excites me is diving into doing things that are too difficult for me, failing, beating my head against my desk, asking real people for help (not supervisors or TA's), making tiny exhilarating steps of progress.

I'm generally very skeptical about all kinds of teaching, upbringing, and so on. Like when parents and educators try to ensure that their kids turn out good by adhering to various "time-honored" methods and curricula, and fail to realize that they're just locking their kids up for decades, ineffectively preaching at them while they wait for the break so they can talk about whatever they're actually, genuinely, vitally interested in.

Maybe I'm just weird, but to me joining a MOOC seems like tying oneself up in chains to learn how to walk. There does seem to be people who actually find sustainable motivation in that sort of thing, but the statistics seem to say they're not as many as those who only think they will.

By all means dabble around with some courses to get your feet wet, but don't expect to become a good programmer by following other peoples' curricula!
WebRTC: Update and Workarounds
Hmm, I'm not able to reproduce that. Did you happen to paste anything in? Currently the contenteditable div gets a little jumbled when you paste in anything that isn't plaintext.
Autism employment and distributed computing
1) Self thought from copy pasting code and changing out parts until it works, moved on to books later. What was always most important for me was to have a goal in mind, something that you build towards or really want to accomplish, with brute force and excessive Googling if necessary.

2. Read my first programming book when I was 15, on ASP of all things but I had been learning HTML on my own prior to that, following tutorials online. My school also offered a short course on Turbo Pascal.

3. Got my first job as a Flash programmer when I was 18 and I'm soon turning 27, employed as a Full Stack Developer (don't hate) without having a CS degree. I do have a bachelors degree in Media but it's essentially worthless and has nothing to do with my work.
Wow... thats so true!
Plain Lua FTW
Well, if anyone wants a very practical lesson on bias I can highly recommend:

http://www.conservapedia.com/Conservapedia_proven_right

http://www.conservapedia.com/Conservapedia_proven_wrong

I sometimes wonder if someone would end up with a better world view by reading http://uncyclopedia.wikia.com
Why Namedar (one of my startups) Failed
This is amazingly useful. Every site I work on needs a contact form but it has to be styled, validated with JS and on the backend and then configured to be sent to my customer. I can do this all with my eyes closed, but it still takes time. Can't wait to use this.
> I think that's the issue exposed by this post -- if these really basic things are broken, why would anyone believe that the actual tricky stuff has been tested?

So, I think it is relevant that LWT is still a very new feature in Cassandra and not something basic to it at all (arguably counter to a lot of its original design goals).

Personally, I was much more concerned by the server side timestamps only using millisecond granularity (and even that is somewhat understandable given the JVM's limitations).
The tone of the presentation is like this: "Hurr durr, look at the dumb EEs, using bits. They probably even design and validate their stuff before implementing it, how retarded and un-agile!"
Introducing Sprinter: Manage your dev environment(s) easier
"I thought I'd share that this particular choice, if anything, undermines the goal."

but that isn't what you shared. All you had to share was vague old man gripes about a language, with the only concrete example being something that is only really half true.

For christ's sake, you suggested Java and Objective-C for the task. How do you expect to have any credibility after that? For a novice language, why are you expecting a typical task would be decoding a binary protocol?

To claim that you are just sharing your wisdom here is intellectually dishonest.
Programming is a Terrible Job
might be nitpicking a bit here, but "information" != "data". It is hard to tell how little or much information I can extract from any amount of data. data + context = information
I'm self-taught and a relatively late starter. I've also never studied computer science in a formal setting (i.e. at a university).

I started programming when I was studying for a PhD (in mathematics) around 2006-07. I was 23 at the time. That was mainly in Matlab and Fortran. My code from those 3-4 years is, frankly, pretty horrifying.

When I got my first job in industry (quant at an investment bank in 2010) I had to learn Java, and a language called Q[0], which is a very fast array-processing language with a functional feel and a built-in query language for the KDB database. I also picked up a little bit of R, mainly because I was building a lot of statistical models and it was far easier than doing it in Java.

That piqued my interest in functional programming, and I subsequently learnt Haskell using the book Learn You A Haskell[1]. I picked up Python around the same time when I was trying to write a web scraper, and finding it painful in any of the languages that I currently knew. For that I used Learn Python The Hard Way[2].

When I started a new job in 2011 I started writing Matlab again, causing me to finally learn it properly. Around that time I decided to try and learn a low-level language, so I picked C, mainly because there was an interesting edX course [3] that I wanted to try (the Harvard course CS50).

I'm at a weird in-between stage now. I can write comfortably in half a dozen languages, but there's a whole swathe of programming that is completely alien to me (web design, networking, and any kind of formal software architecture). I've written a lot of heavily numerical and mathematical code, but never written a CRUD app or a web page. I still don't know Javascript.

[0] http://en.wikipedia.org/wiki/Q_(programming_language_from_Kx...

[1] http://learnyouahaskell.com/

[2] http://learnpythonthehardway.org/

[3] https://www.edx.org/
I'd like to see examples on how this compares to regular run-of-the-mill post-process sharpening. If the "before" images were straight from the camera, the comparison isn't really fair.
It is available though pip.
It certainly does and it never claims otherwise. However, even though it shows examples that are biased mostly to one side it points out and describes the techniques used to create the bias, so you're free to use the knowledge gained to help yourself recognize the other sides attempts at creating a bias.
Time invested doesn't even remotely imply greatness.
Forty-something programmer (diversified into various forms of consulting). Self-taught from printed matter before the Internet existed. Started coding on a ZX81, moved up to Apple ][, then to Macs. Dropped out of college to start working as a coder at 20. I started out as a freelance games programmer but that was a bit beyond my business (not coding) skills of the time, I took a job at a startup(ish) instead.

Nearly all of my learning happened on the job, as a result of taking on projects involving technologies that I had no clue about when I started and mostly mastered by the time I finished. Pretty much what is now called a "full stack" developer as a result.
I'm a self-taught programmer, my background is actually in Financial Economics.

I believe the best way to teach yourself is to solve your own problem or build something you're truly passionate about. You can either do something new or improve something you currently use. This is how I taught myself to code in PHP, although now I can also write applications in Python.
Episode Seven: One Char to Rule them All (C++)
Almost all of my knowledge is fully self taught with internet (no books) except for proper OOP like in cpp. That I did when they taught me in college. But I learned html5/css3/js/php/mysql/unix command line etc on my own. I was "introduced" in 10th grade in high school when school wanted to make a website. I took up the offer and they were glad their student was making it. It looked hideous (at least the first iteration did) used tables and in-line js but this was like 2008 and I had no previous knowledge. I never really looked back since then. I keep doing something. There was always something I was looking forward to learn/do. I wanted to solve my own problems and find solutions or make things easier for myself. Now I make things easier for others and it feels great. I spent most of my time on Google/SO. I had to work very hard. I remember it very well, it was never easy (it still is not) but work is now a lot less frustrating. The most important thing I learnt myself was probably ow to solve problems. With google primarily, but ability to find solutions to your coding problems via google is very important. And I learnt it the hard way. And college is fun because I have basic html in my next year of college but I know that stuff for at least 4 years. So it should be fun.