Quote:
Originally Posted by Fox
Courses are a good option, there are lots you can learn. When I switched from mainframe to PC dev I had a friend that was a senior developer/analyst who did walkthrus of the code and design documents I wrote and I wrote a small program for a friends business for free ,that he never used anyway, BUT it was a full project from concept, design, coding, QA and approval and it cost me a few beers and dinners. I used all the free tools, templates, database tools and design patterns I could and made sure the walk thrus covered everything. Having someone with that much experience beat me essentially, when I got the job I was looking for I was soon in charge of fixing the contractors code and reviewing/fixing and QAing their work.
Another point, I just had to look at a bunch of Waterloo COOPs for winter term and resumes are important and some really STINK!!!! Each resume needs to be honest BUT needs to highlight the why you should work here question by expanding on or emphasizing a skill they are asking for.
Like I said, think about what you would get paid at and enjoy and Good Luck
P.S.
A couple tips for when you do get in besides the usual work hard:
1) document everything, remember the order of blame (contractor, new guy, guy that left and THEN the actual person responsible),
2) don't volunteer or question the vendor if they are integrating (I did, off the project soon out the door... I was familiar with the problem from previous work and in the first meeting I asked questions the PM and Vendor didn't like, never invited to another meeting even though I was the S/A... in the end project failed huge write off.) only explain to the internal staff later, IF they seem willing to listen. They have big money involved even just starting a project and unless you have a sponsor in the company they may view you as unneeded.
3) extra hours for a newbie aren't an option, they are a requirement but if it is a gov't job don't outshine the existing deadwood. Deadwood in a company usually is someone that knows someone and can cause you problems.
4) layoffs happen, been there done that a few times....at one company when I was off the day they did the layoffs (almost 50% of the staff) I was called at home and told I was fired.... that was less than 2 weeks after I had got an award for leading a team and project and meeting a real tight deadline. My manager was trying to get them to keep me was also in the group layed off.
5) Short term contracts can be extended .... again and again and again.... better to be working.
