From my experience, we can take every stage of implementation as an opportunity for documentation.

1. When you write code, adding good class, function level documentation string, adding dev notes to breakdown complex logic works as a great means. Using meaningful names for classes, functions etc will also help other engineers / the future go through the code quickly.

2. The next step is, when you’re going to submit your merge request, this can be used to capture few more important details. I use the following framework in all my MRs:

   1. Changes Description:
   2. Testing strategy:
   3. document details about manual / automated testing (unit/integration/e2e)
   4. Commands run:
   5. Evidence of changes:
   6. failures / exceptions raised
   7. edge cases
   8. successful / green path cases


1. Finally, in order to capture the larger decisions like framework choices, schema design etc, I would recommend to create a Wiki page / Confluence page before you start working on the code. Update the page as you conclude your analysis. This way, the research is done and you’ll capture it on the way instead of separately taking time to create the wiki (as you mentioned speed is critical in your project).

Senior Software Engineer @ Nvidia

curious-soul

How do you plan your day-to-day work to make sure you’re not burning out and managing meetings?

Any frameworks or techniques that you follow?

How do you develop new interest and work on them on the side?

Eg - you mentioned about ML and exploring on the side, can you provide feedback ideas / frameworks to explore? 

Interest may be tech or non tech related that’s fine.

What are you suggestions for someone looking to decide if they want to grow to a staff engineer role or engineering manager role ?

1. How would you start increasing influence in a new company?
2. What things should one focus on growing from Senior Eng to Staff Eng & Senior Eng to Eng manager level?


If I told you that you can make $10,000+ just sending a couple emails, would you do it? Definitely yes right? This is why you should always negotiate your offers. Use this collection to learn how you can navigate these awkward, high-intensity conversations to get the pay you deserve.

[Taro Top 10] Pay Negotiation

Alignment

Neogtiation - Sal

Performance Review Tips

Promo

I asked every step of the IC engineering ladder a simple question: "What is the most important skill for success at your level?"

The result is an engineer from each of the 7 levels sharing their candid reflections about the most important skill, along with advice. Companies represented: Meta, Slack, Qualcomm, Gusto, Instacart, Cruise, and Pinterest.

Asking 7 Levels Of Engineers The Most Important Skill

Stocks related

This is one of most important interview rounds, especially for engineers targeting more senior levels. However, so many engineers struggle in these interviews due to poor communication skills.