Portfolio Ideas?
I started working on a portfolio a couple of months ago in anticipation of getting my Associate Degree in Computer Programming.
However, I can't think of any projects to work on. I have a few small projects up, but nothing really impressive; just a List class, a Tic-Tac-Toe game, an (incomplete) sample bank system, and a link to my wiki, which will eventually contain all my code snippets and solutions to common problems.
I just can't think of anything to work on. Can anyone suggest something?
I know the following languages:
- C++
- Java
- Python
- X/HTML
- CSS
- JavaScript
- PHP
- MySQL
Looking forward to any replies. Thanks.
However, I can't think of any projects to work on. I have a few small projects up, but nothing really impressive; just a List class, a Tic-Tac-Toe game, an (incomplete) sample bank system, and a link to my wiki, which will eventually contain all my code snippets and solutions to common problems.
I just can't think of anything to work on. Can anyone suggest something?
I know the following languages:
- C++
- Java
- Python
- X/HTML
- CSS
- JavaScript
- PHP
- MySQL
Looking forward to any replies. Thanks.
Last edited on
closed account (1yR4jE8b)
Pick a popular open source project and write some patches/new features for it.
I've never done that before. Do you know of any guides that can help me pick my first project, within the scope of my abilities, and find something about it to patch? Also, how to "patch" it, meaning how to submit my update.
I would prefer my own project, though.
I would prefer my own project, though.
closed account (1yR4jE8b)
Just find a program that you like.
First check if there's a forum or mailing list Usually the website or the maintainers will have a README on how to get the source and their particular process for submitting patches, or they'll just replay to you with a short email on how to get started.
Check the site's issue-tracker for an open bug that sounds simple to fix, get the source and try to fix it. It's actually not that difficult, once you get to it. It could be something as simple as translating some strings, or changing the color of a button. The beauty of it, is that it's all work that needs to get done and the core maintainers usually don't want to do it, so it's win-win for everyone because even n00bs can start small and work their way up.
Being able to show that you can integrate into existing teams, follow their processes, and use their tools -- all in real-world scenarios -- will be much more valuable IMO.
First check if there's a forum or mailing list Usually the website or the maintainers will have a README on how to get the source and their particular process for submitting patches, or they'll just replay to you with a short email on how to get started.
Check the site's issue-tracker for an open bug that sounds simple to fix, get the source and try to fix it. It's actually not that difficult, once you get to it. It could be something as simple as translating some strings, or changing the color of a button. The beauty of it, is that it's all work that needs to get done and the core maintainers usually don't want to do it, so it's win-win for everyone because even n00bs can start small and work their way up.
| I would prefer my own project, though. |
Being able to show that you can integrate into existing teams, follow their processes, and use their tools -- all in real-world scenarios -- will be much more valuable IMO.
Last edited on
Topic archived. No new replies allowed.