├── LICENSE ├── README.md └── assets ├── bridge.png └── duck.png /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2020 Stefan Feješ 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # remote-internship-advice 2 | 3 | > friendly remote internship advice so you make the most out of it this summer ☀️ 4 | 5 |

6 | 7 |

8 | 9 | With many remote summer internships starting in about a month, I wanted to share a few pieces of advice that helped me have an enjoyable experience and get return offers from last 4 internships and land my 5th at GitHub this summer. 10 | 11 | - Reach out to your manager if you haven't already, say hi, introduce yourself and share the excitement about the internship. Don't overcomplicate it; they're just individuals like you and me. Getting to know people before starting to work with them is a great start. 12 | 13 | - Ask for a project-specific tech stack and look for stuff that you might not be familiar with. One month is enough to cover the basics of anything you didn't learn at University and will save you lots of time (and stress) once the internship starts. (eg. for my last internship that was RxJS as whole application state management was done using Reactive observables) 14 | 15 | - Don't be embarrassed about asking for help. To get where they are now, your teammates had to go through the onboarding process and stuff you're facing now. They're willing to help. 16 | 17 | - Define with your team when you should ask for help. You'll run into obstacles every day. Some might take 30 minutes to solve, and others might take forever. Find a balance - You don't want to interrupt the whole team every 30 minutes, but don't let one problem turn your internship into an unpleasant experience. 18 | 19 |

20 | 21 |

22 | 23 | - Practice [rubber duck debugging](https://rubberduckdebugging.com/). You don't want to schedule a 30-minute meeting with your team and 2 minutes into explaining the problem you get to the _aha!_ moment where you figure out the solution to the problem. 24 | 25 | - In a nutshell, before asking for help, try to explain the problem you're having to a random object. Most of the time, during this process, you'll get new ideas and solve a problem by yourself without needing somebody's help. 26 | 27 | - Most likely, you won't be micromanaged, but it's a good idea to keep everybody updated on your progress. Doing this, your team might offer some useful advice based on your progress or prepare you for upcoming obstacles in the task. 28 | 29 | - If something isn't right, don't be silent. Your teammates aren't wizards, and they can't read your mind. If something is bothering you, you're stuck or not comfortable doing something. Just talk. Everybody is willing to help, but you need to let them know first. 30 | 31 | - If time allows it, plan virtual pair-programming sessions with your teammates. Once a week, pick a short task and try to solve it together. Doing this, you will pick up domain-specific knowledge faster, learn how to navigate new codebase efficiently, and improve your problem-solving skills. 32 | 33 | - Socialize with other team members on Slack channels like _#random_ and _#watercooler_. Just because you're new to the team doesn't mean you shouldn't participate in casual conversations with other employees. They are social beings too and are probably looking forward to getting to know better new colleagues. 34 | 35 | - Meet and share the experience with other interns. Just because you don't share the same office space doesn't mean you shouldn't meet each other. Organize weekly chats, talk about work, life, favorite movies, shows, games, books. Make a shared Spotify playlist. **Socialize**. 36 | 37 | - > Moving to a different side of the globe and doing an internship in San Francisco was supposed to be a big move for me this year. A big part of it would be getting to know awesome people from top US / Canadian Universities, exchanging our career experiences, having fun, and planning for the future. Just because the internship has to be a remote one due to COVID-19, don't let it stop you from new connections. 38 | 39 | - Step up your asynchronous communication game. With your teammates not being in the same office, or even the same time zone, it's essential to give your best at communicating things. 40 | - Go over long domain-specific messages you're about to send. Make sure there is enough information for the other side to understand you. If possible, use markdown-like syntax inside Slack for better formatting. 41 | - Don't be late for meetings. If in a loud environment and not speaking, mute your microphone to avoid unnecessary background noises 42 | - If possible, show instead of write. Use toolks like [Loom](https://www.loom.com/) or [illuminati](https://github.com/zeke/illuminati) to record a short clip of your screen with a voiceover where you cover the problem or progress. This approach will help your mentor understand your process of thinking much more than a huge chunk of plain text. 43 | - Write clear and meaningful commit messages and nicely structured PRs. Self-review pull requests before sending them over for review and make sure they don't include mistakes such as typos. 44 | 45 | _Repository maintained by [@fejes713](https://twitter.com/fejes713). Contributors welcome._ 46 | -------------------------------------------------------------------------------- /assets/bridge.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/fejes713/remote-internship-advice/b95c550c01dd08b83892d6e5c11d0f8f9ccd1cad/assets/bridge.png -------------------------------------------------------------------------------- /assets/duck.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/fejes713/remote-internship-advice/b95c550c01dd08b83892d6e5c11d0f8f9ccd1cad/assets/duck.png --------------------------------------------------------------------------------