Originally Posted by
copeg
I don't want to detour you from that route, just let you know it could be a tough one. An alternative is to take something you wrote and really improve upon it...create proper documentation, write comprehensible code, and most importantly use principles such as design patterns to allow the code to be readily adaptable and easier to change at a later date - write reusable components, abstract things that might change, etc...I can't speak for the employer, but this knowledge and demonstration of that knowledge is very important. I have some code that does unique things, but I wouldn't dare dream of showing to another soul given I know how poorly written it is. Just my .02
Thank you for your reply. I did actually do something like what you suggested for one of my latest projects. It was a Software Design assignment project so very focused on the documentation, I was planning on showing it because I'm very pleased with the documentation but the program itself was very simple and I'd like to have something more complex to show off.
EDIT: think I'm going to scratch the banking program with SQL database idea as like you said the worst thing possible is to show something done terribly. I think I'm going to try something I definitely can achieve and do it step by step like I would with an assignment...so basically your second suggestion but with a new program...once I've thought of something haha.