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.
Subscribe to RSS Feed
= f037147d6e6c911a85753b9abdedda8d)
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?
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.