Vigyata.AI
Is this your channel?

Every Software Engineer's Biggest Fear | My Biggest Fear As A FAANG Software Engineer

452 views· 31 likes· 8:35· Aug 5, 2023

🛍️ Products Mentioned (6)

Knowing what I know now, how would I start over as a software engineer? What steps will I take to start my journey as a software engineer? 💻 Google Coding Certificate: https://imp.i384100.net/zNjB4r 📌 Software Engineer Tech Essentials: https://tinyurl.com/bdhywpj4 🔖 Stay Safe Online with Aura: https://aura.com/sandra 🔒 Get 3-months free with ExpressVPN: https://expressvpn.com/withsandra My Camera Gear: https://amzn.to/3zJqFIA Follow me on IG: @techwithluca Brand/Collab Email: techwithluca@gmail.com Tech & Boba Podcast: https://tinyurl.com/4ehpxak Disclaimer: This video is not officially endorsed by the employer. The views, opinions, and experiences expressed herein solely belong to the subject and do not represent those of the employer. tags: software engineer,programming,software engineering,new grad software engineer,computer science,day in the life of a software engineer,software developer,faang internship,internship,interview,data structures,leetcode,microsoft recruiting,internships,learn to code,python,learn to code for beginners,how to learn to code,how to learn programming,job search tips and tricks,how to become a software engineer,How to learn coding,learn coe,how to code for beginners 00:00 Intro 00:15 Quitting Vim... 01:30 Learning C 02:53 Coding Interview 04:38 Migrating files or copy/paste 05:40 bugs 07:08 Outro

About This Video

In this video I share five of my biggest fears as a software developer (and yes, even as a FAANG engineer). I start with the most relatable trauma: quitting Vim. Back in college I literally couldn’t figure out how to exit, I tried random “:q!”-type commands, and it turned into this whole quitting-without-saving mess. That experience gave me nightmares and honestly pushed me toward IDEs because I just wanted to focus on coding, not fighting the editor. Then I get into the fears that actually make your life harder on the job: segmentation faults when you’re writing C (the ultimate “code sweats” moment), and the dread of getting a dynamic programming question in an interview. For a long time I tried to avoid DP because it felt like too much time for one topic—until an interview forced me to face it. After I finally studied it properly, I even got a DP question in a Google interview and solved it, which taught me that avoiding fear doesn’t fix it. I also talk about copy/paste mistakes during migrations (weird characters, off-by-one strings, template files where compilers won’t save you) and the most annoying one: bugs that aren’t reproducible. My takeaway is simple: choose your battles—avoid what you’ll never use, but if it’s part of the path (like interviews), you have to confront it.

Frequently Asked Questions

🎬 More from Tech with Luca