tags:

views:

144

answers:

4

I am about to start my internship at the IT department of a big company next week. I would really like to impress the relevant people there so they offer me a permanent job after I graduate in Fall this year. I am good at programming and very hardworking, most importantly I enjoy doing it, but since this will be my first experience making something outside of my classroom for an actual real world problem, I want to know how I can excel at it.

I don't yet know the details of what platform, language etc I would be working with or I would include them here. Any pointers on how I can really do a great job? anything people just out of school with no real world experience need to know? If you have had interns work for you what were the most common qualities/skills you thought they were missing? pretty much anything you can tell me at all will help, I want to prepare and hit the ground running from the first day.

ps: I know this is not a career site but I feel like this is where I will get the best answer to this question so please don't close. thanks

A: 

Having just been in your shoes (just graduated after having a two year internship) my advice would be to work hard, which sounds like you are already good at. Namely, don't be afraid to jump into projects and try your hand at anything they offer and throw your way. The best way to impress the bosses and the powers that be is to show that you are willing to work on any project.

My other bit of advice would be to start reading technical books. Once you find you what language you are going to use, read some books about that language. For Java, I would suggest Effective Java for instance. Also, read Pragmatic Programmer. It is a great book to prepare you mentally for some of the struggles of working for a big software company.

kratos2488
how "hard" you work is irrelevant, effort != results. And results is what gets you a perm job. If you work 60 hour weeks and don't deliver on time, or buggy un-maintainable code, you are no better off than working 20 hours to produce the same failure.
fuzzy lollipop
Actually, you're worse of, unless you think that working is a virtue.
Yar
A: 

My first days as a real programmer were not too long ago. My suggestion is not to be afraid to impress them with what you know. If you think you know better than them, speak up! On the flipside: if you don't understand something, ask for help! Asking for help looks MUCH better than sitting around getting nothing done. They won't expect you to know everything so don't pretend. As an intern, you're there to learn; so make sure you learn heaps!

Duracell
+1  A: 
  1. Learn to be efficient at everything you do. ( this does not mean code performance or premature optimization ) it means "using the least amount of effort to obtain your result"
  2. Learn how to listen and ask questions to fill in what you don't understand.
  3. Learn how to fit into the team, this is critical, people will work with someone they like and help teach them over some one that they don't get along with and is more knowledgeable.
  4. Read things like Joel on Software and the book.
  5. Have opinions but don't be dogmatic.
  6. Learn the difference between arguments and "animated discussions".
  7. Learn how to use a debugger, logging is the last refuge of the lazy.
  8. Learn how to use tools to make your job more efficient.
  9. Always remember neither you nor anyone else actually knows as much as they think they do.
fuzzy lollipop
#4 which book? #7 you mean using System.out and inspecting instead of using a debugger is lazy? Could you explain that (in a footnote?) #8 he wants to make software, so it should say "use and MAKE tools to make your job more efficient."
Yar
#4 Joel on Software is a book#7 like it says, logging anything other than fatal errors right before you System.exit(1); for debugging is lazy and in-efficient, breaks rule #1#8 no use tools to automate your work for you, there are very few reasons to make your own tools with the OSS community like it is now. Very few people have unique enough problems that they need to make tools unless that is what your company does, making tools that is.
fuzzy lollipop
Fascinating as your answers tend to be: thank you!
Yar
+1  A: 

Be yourself and do not hit the ground running, as it is dangerous :).

Yar