3 ms·
1) Go to Github 2) Browse the Javascript projects 3) Look for projects which are active with many follows/forks 4) Click on the Issues tab 5) See what
by Ologn 12y ago
1) Go to Github
2) Browse the Javascript projects
3) Look for projects which are active with many follows/forks
4) Click on the Issues tab
5) See what open issues there are
6) See if the maintainer is active and applies pull requests
7) Pick an issue you can fix, fix it, write a patch
8) Send a pull request
9) See if the maintainer has any comments
10) Go back to step 1
See - you're solving problems. This is the kind of stuff you'd have to deal with on the job, and is the kind of stuff you'll deal with with your own projects as you or your users discover problems.
I know exactly a problem you can solve right now with Javascript.
* Go to this website - http://maps.huge.info/zip.htm
* Move around the map so you can see where various San Francisco zip codes are.
* Now try to do this on your phone
I'd love for this to be a mobile-friendly website, but it isn't. It's a useful tool, it looks like it's just a mashup of Google Maps and ZCTA's. A perfect project and problem to solve.
- jakobegger 12y agoYes! There are so many comments in this thread and the last one makes the most sensible suggestion: get involved with an open source project! There is absolutely no point in starting your own projects from scratch when you've never seen other projects. Fixing random bugs in open source software is great for two reasons: 1) you'll need to read large amounts of code to find bugs, learning things about coding style, design patterns, architecture along the way 2) What you do actually has a purpose. There's nothing more boring than programming for the sake of "practice"