3.Read it over 5 times before you ask for help. Trust me.

2.Ask for feedback often. You don’t want this to be annoying, but it’s healthy to seek out feedback regularly and not just once a year during your review, because odds are by that point it’s too late to make any changes

1. Find at least 2-3 mentors (different levels of seniority) that way you get multiple perspectives on navigating your career

We talk a lot about how to prepare for the technical interview, but not enough about how to stay employed once you land the job Here are 3 helpful tips ——>

No one becomes an expert without time and practice. Said best by Danish physicist Niels Bohr “An expert is a person who has made all the mistakes that can be made in a very narrow field”

For more free tech resources visit codebysophy.dev

5. Write and read more Set a goal to read and write more daily offscreen! All it takes is 5 mins a day.

4. Ask for a review Get a second pair of eyes to review your work or presentation before getting it to its final round. This allows you to get feedback on possible holes in your explanation

3. Be thorough More often than not, people have no clue what you’re talking about because they are so focused on their work. Don’t generalize your explanations, the bug you’ve been staring at for the last week is likely nonexistent to the person you’re asking for help

2. Practice Practice truly makes perfect, so go out of your way to practice your communication. Ex) Set a goal of asking 1 driving question per meeting.

1. Preparation is key: Prepare for everything. From an informal 1:1 to a scheduled meeting. Ensure you know what you’re working on, and why.

The software engineers that get to lead teams and make impact are technical in nature but more importantly, outstanding communicators. Here are 5 tips to help you improve your communication style:

4. Read before lecture. This will allow you to actively listen during class rather than mindlessly try to figure out what the professor is talking about.

3. Limit the highlight. Studies show that highlighting does little to nothing in helping you retain information.

2. Re-read your bullet point notes when you reach the end of each page. This is vital to ensuring you actually processed what you just wrote down

1. Take bullet point notes. For every important concept, write 3-5 word bullet points. Ex) Python is a dynamically typed language with automatic garbage collection •Python • dynamically typed • auto garbage collection

There’s a common misconception that you have to be naturally smart to make it in the STEM field and that’s simply not true. The key is learning how you learn and being the most effective with your time. Follow these 4 rules to cut your study time in half: