Comment author: JonahSinick 29 March 2014 11:09:16PM 0 points [-]

Thanks.

Do you have a reference point for the magnitude of the impact? Would you expect someone to be able to do more good doing these things than as a software engineer? Is the effect on the same order?

Comment author: luminosity 30 March 2014 09:03:36PM *  0 points [-]

As John_Maxwell_IV says, it really depends on the project. A good recent example is the knockout javascript library. My last job was focused on building javascript/REST-API driven dynamic admin interfaces. Without knockout, having to use just jquery & native JS I don't think it's an exaggeration to say I may have been an order of magnitude less productive. Some of the more advanced features I was able to deliver would probably have been too complex to manage.

Of course, not everybody working away at their own new great idea should expect to be able to have anywhere near that level of impact, but I think it gives a good estimate of the sort of impact that is within grasp for the most successful experiments / projects.

Comment author: ChristianKl 30 March 2014 11:42:14AM *  1 point [-]

1) Get involved in big, professional open-source projects with small bug-fixes, documentation, and bug reporting.

For a high school student it's not straightfoward to know the step by step process he has to go through to contrubute bug-fixes or even documentation.

If you want to edited an Wikipedia page that's a lot more straightforward than editing the documentation of an average open source project.

I personally have edited Wikipedia plenty of time and can't remember contributing to open source documentation because the complexity of figuring out how to go about contributing is too high to bother in particular cases where I see something that might be fixed.

A step by step guide about how to go about fixing a simple bug would be very helpful.

Comment author: luminosity 30 March 2014 08:59:30PM 0 points [-]

An easy first step is to just report the problem with the documentation when you find it. Something can't get fixed if it's not found, and reporting bugs should be pretty simple through the github interface for your standard project.

As for contributing fixes, you'll need to have a little experience with forking, creating pull-requests etc, but the nice thing is that these are basically free to play around with for open source projects on git-hub (or bitbucket). Most documentation will be in one of a few basic formats in the project's source code (markdown is popular, as is re-structured text for python projects). These are usually designed to be relatively easy to edit, and are fairly simple to find tutorials and introductions for.

Another way you can help out without fixing bugs is by triaging existing bugs. Not all projects need these, but a lot of larger ones have a problem with just sorting through bugs to find what matters, what's urgent, what's a duplicate, or a won't fix etc. Many are more than happy to welcome a new volunteer on board who can just read through new tickets as they come in and set labels such as 'duplicate' or 'blocker'. Being involved in the process in this way, you can then follow along seeing how the existing core developers go about fixing bugs, and pick up from there.

Comment author: luminosity 29 March 2014 11:01:54PM 4 points [-]

Programming libraries and making them freely available, as in a large number of open-source projects seems to me like a definite positive. For instance, the jquery javascript library is freely available, such that learning it is a transferrable skill between jobs, a foundation that other projects can build upon, and means the messy work of ensuring cross-platform javascript compatibility only has to be performed in one place, instead of again and again. There are many other examples of useful pieces of programming infrastructure provided for by volunteer work, from graphics frameworks, to programming languages and so on.

I'd also contend that there is a lot of room for volunteer work within open source, for those looking to contribute in these ways. The project that doesn't have more issues in their bug trackers than they have people can handle is rare, and often many of these bugs are simple enough that even a relatively new programmer could contribute.

Comment author: [deleted] 06 March 2014 10:50:18PM 12 points [-]

Side point: Quora has the annoying popup that allows you to only read part of the top answer to a question if not logged in, so many people categorically ignore it. Also, there's no compelling reason to use it over reddit or other forums.

Comment author: luminosity 08 March 2014 12:32:14AM 21 points [-]

Quora hack: Add '?share=1' to the end of the url, and you can read everything.

Comment author: NancyLebovitz 03 February 2014 03:31:52PM 8 points [-]

Do you take notes when you read non-fiction you want to analyse? If so, how much detail? On the first reading? Just points of disputation, or an effort at a summary?

Comment author: luminosity 03 February 2014 08:51:00PM 1 point [-]

Usually I'll read it in depth first, then once I know if it's worth taking notes, I'll return to it and scan through quickly for those points I know are worth grabbing.

Comment author: luminosity 02 February 2014 12:02:46PM 6 points [-]

If you want to gain personal skills, a good avenue for spending money is removing distractions that decrease the time you have to devote to these skills. For example, hire cleaners or gardeners to free up the time spent on necessary chores.

Comment author: IlyaShpitser 16 January 2014 06:46:15PM 4 points [-]

Good post. I was just talking to Luke the other day, and wondering why is it that the more senior a researcher becomes, the more (s)he resembles a manager.


Different professors earn roughly as much, have roughly the same social standing,

Probably true for salary, not necessarily true for social standing: superstars are much more highly regarded.

Comment author: luminosity 17 January 2014 01:05:30PM 1 point [-]

wondering why is it that the more senior a researcher becomes, the more (s)he resembles a manager.

It's not the only profession where this is the case. Programming is notorious for having no career progression after your first decade unless you want to get into management and stop or slow programming activity.

Comment author: luminosity 23 December 2013 12:43:57AM 12 points [-]

Fantastic post. Usually with posts along the lines of AI & epistemology I just quickly scan them as I expect them to go over my head, or descend straight into jargon, but this was extremely well explained, and a joy to follow.

Comment author: pianoforte611 07 December 2013 05:04:31AM *  0 points [-]

Does it make you feel less cold in general? I'm considering doing cold showers, but I'd like to know if the discomfort is worth it.

Comment author: luminosity 08 December 2013 01:02:57AM 1 point [-]

Purely anecdotal, but since I started taking cold showers, ~20 degrees C has gone from being switch to warm clothing territory, to fine in a t-shirt instead.

Comment author: luminosity 22 November 2013 08:07:45AM 36 points [-]

Taken the survey. Thanks for doing this, Yvain.

View more: Prev | Next