As an intern, sometimes it's hard to know what to do next.
Manager asked me to spend more time looking at the code.
I can spend all the time i want staring at the code, but all it does is cause anxiety when I don't know what's happening.
There are 2 ways to approach this problem:
1) Learn more about the language, framework
- con: can go down tutorial hell
- pro: you build confidence
2) learn more about the code you're looking at by pairing with someone on a PR review or tickets
- con: the discomfort of being vulnerable to communicate and ask questions
- pro: save up on time and confusion bc colleagues will likely know
Option 2 is necessary as an intern because the one thing you've got to get used to is feeling vulnerable as an entry-level developer. Odds are, your team WANTS you to ask questions rather than float along with duck syndrome.
Even in the worst case scenario, if you don't understand and the person you work with isn't helpful, it's still a good idea to get as much exposure as possible.
You'll never ever know everything! Everyone has to go through this process to grow. Might as well jump in and be kind with yourself.
Note: This post was started a while back (~2 yrs ago), but never published.
Top comments (0)