Forgot your password?
typodupeerror

Could a Reputation System Improve Wikipedia? 216

Acidus writes, "There is an excellent article in this month's First Monday about using reputation systems to limit the effects of vandalism on public wikis like Wikipedia. It discusses the benefits and weaknesses of various algorithms to judge how 'reliable' a given piece of text or an edit is. From the article: 'I propose that it would be better to provide Wikipedia users with a visual cue that enables them to see what assertions in an article have, in fact, survived the scrutiny of a large number of people, and what assertions are relatively fresh, and may not be as reliable. This would enable Wikipedia users to take more advantage of the power of the collaborative editing process taking place without forcing that process to change.'"
Censorship

Wikipedia Won't Bow to Chinese Censors 504

truthsearch writes "Jimmy Wales has defied the Chinese government by refusing to bow to censorship of politically sensitive Wikipedia entries. He challenges other internet companies, including Google, to justify their claim that they could do more good than harm by co-operating with Beijing. Wikipedia has been banned from China since last October. Whereas Google, Microsoft, and Yahoo went into the country accepting some restrictions on their online content, Wales believes it must be all or nothing for Wikipedia. 'We occupy a position in the culture that I wish Google would take up, which is that we stand for the freedom for information.'"

Who (Really) Writes Wikipedia 175

Nico ? La ! writes "Aaron Swartz questions Jimbo Wales' (Wikimedia's founder) belief and evangelized truth that only around 500 people are the most important contributors to Wikipedia. Whereas the truth is that they probably are the people who do the most editing. From the post: 'For example, the largest portion of the Anaconda article was written by a user who only made 2 edits to it (and only 100 on the entire site). By contrast, the largest number of edits were made by a user who appears to have contributed no text to the final article (the edits were all deleting things and moving things around).'" Which ultimately means that Wikipedia in some ways much more closely mimics a real encyclopedia, with many contributors writing the bulk of the content, but a small group massaging that text to insure standards compliance with the overall work. Interesting thing there and worth your time, although the super-computer thing doesn't make a lot of sense to me.

Comment my own 2 cents... (Score 2, Interesting) 715

I will pass you the very, very boring details about the economics behind it all but here's a couple of points you may find interesting that I garnered during my *exciting* academic career studying the economics of the software industry:

- Yes, jobs are moving abroad. But most of the time they are what are known as "low value-added" jobs - not the leading edge, cool, revolutionary new programming but the mundane old stuff such as debugging, maintenance, hotlining (gasp), etc... A lot of what is done abroad is actually adapting American or European programs to local languages.
- High value-added jobs will probably still be found in the states for a few years to come. Why is this? Well as mentioned above, the training you will receive in the US will always carry some kudos (here or abroad) because of the US's reputation as a technology leader. Secondly, knowledge in IT tends to be geographically concentrated (see Route 128, SV, etc). This is in large part due to the *nature of knowledge*. I'll pass you the boring theory but basically, interaction with your peers, frequently possible in such an environment as SV, has been found to be very important in learning about new techniques, languages, etc. Also as there is a concentration of skilled labourers in those areas, firms keep wanting to settle there (self-reinforcing geographic concentration)
- Excellent coders will always find work. All right, you may have to compromise and be willing to move abroad if required. But if you're good at what you do, keep up to date with the latest languages etc, you will always find work.
- IT is everywhere. Even if you do not end up working in the industry per se, ALL industries use computers, and there are a lot of possibilities in that. Take for example the bio-technology industry: there is a shortage of biologists who know how to code, so a lot of their bioinformatics development is done by IT graduates.

Now my advice to you, young grasshopper: go into IT if you really want to. Believe me, unless you love it, the many many years at college as well as the hours devoted in your spare time learning new languages and garnering experience on your own projects etc, will be pointless: you'll end up not liking your job, and chances are you won't be very good at it (there is a strong element of passion required, I believe, to be the best at your job). If you want money, go into consulting, bio-technology, or run for Congress.

If this is what you really want to do, my tips would be:
- Start learning now: there is no substitute for experience. You can already pick up the basics - it will make college easier anyway
- Keep up to date. Languages evolve, and it's always worth keeping up to date with what is relevant in the marketplace nowadays
- Open Source software is an excellent opportunity to learn (if not only by looking at code other have written and seeing how stuff works, but also by adding your own bits and getting feedback on your work). Your contributions also work as a signal to the marketplace: when writing your CV you can add that you contributed to X/Y/Z project, and your potential employer can actually track down what you wrote and be astounded by how wonderful you are, decide to hire you on the shot, and give you a billion dollars (well maybe not the last part)
- And just to be safe, learn mandarin...

Slashdot Top Deals

No problem is so large it can't be fit in somewhere.

Working...