3
jdreg95
8y

I'll soon start as a web dev intern, I'm looking forward to it, though I'm also a bit anxious/insecure about it.

Do you guys have any tips for my intern period etc?

Comments
  • 4
    Try to learn as much as possible.

    Ask questions, but take notes. If I have to tell you something 2-3 times, you weren't paying attention.

    Accept the fact that you won't get along with everyone. It's probably not you, it's them.
  • 3
    First, congrats!

    Remember that it's ok to make mistakes, but expect to be asked to fix them.

    Also, you're not going to learn everything you need to know right away. Accept that some things take time to learn, and do your best while being yourself.

    Best of luck!
  • 3
    Great advice here so far!

    Definitely try to learn as much as you can and don't be afraid if a task or project seems too difficult at first. If they throw you right into something hard then they probably expect that it will be challenging for you but that's usually a good thing since those projects tend to be more meaningful, IMO.

    And have fun!!
  • 1
    Congratulations. Don't be afraid to ask questions if you are unsure, it's better to show a desire to improve than to stay quiet and not progress. Try to take in as much as you can the first time you're shown something - you're a developer so you should be detail oriented.

    Stay sharp and keep working hard! 👍🏻
  • 1
    Congrats!

    Besides the great advice from post above, try to filter the information you hear to just remember info which is relevant to you. There's a lot of info being spread but not much very relevant to someone new. If you don't filter you end up with a filled brain without any energy.

    But most of all - have fun!
  • 1
    Have fun! If not u have a place to rant
  • 1
    Congrats! Definitely ask questions - remember, you're there to learn as much as possible. Also speak up if what you're doing isn't challenging enough - not in a complaining way, but in a constructive way. You will be much more appealing of a candidate after the internship if you can speak with enthusiasm of something you learned and worked on.

    Make sure you understand the problem before suggesting improvements. Non-classroom coding rarely looks like what you've written up to this point. The people you're going to work with would probably would like to make a lot of changes to the code and know it's not perfect. However, when someone new points out things that are wrong it's like insulting someone's child. You've got to understand their pain before bashing it. A non-judgemental question like, "can you tell me some of the issues you've had with this code?" gives you background of the battlefield and devs the ability to rant (which we love).
Add Comment