Vigyata.AI
Is this your channel?

How To Grow As A Software Engineer | The SECRETS To Become A Great Software Engineer

1.1K views· 39 likes· 10:44· Aug 26, 2023

🛍️ Products Mentioned (6)

Is always interesting to see the difference between coding and software engineer. So what does it take to become a great 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/4ehpxakc tags: software engineering,getting into faang,learning to be a software engineer fast,learn to become a software engineer,learn computer science fast,get ahead of 99% of software engineers,learn to code,learn to code fast,coding is hard,how to get a coding job,how to learn javascript,how to get into tech,how to make money as a software engineer,getting into microsoft,getting a tech internship,study for tech interviews,How To Be A Great Software Engineer 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.

About This Video

In this video I break down the difference between being “good” at coding and being a great software engineer in the real world. When I was in school, projects were super clearly defined, I worked alone, and nobody really cared if my code style was messy. Then I got into my first job and realized the tech stack was already in place, the codebase had patterns I didn’t understand yet, and there wasn’t a professor or TA whose job was to guide me. I had to ramp up fast, unlearn bad habits, and build the most important skill: the ability to learn. I also talk about the stuff school barely trains you for—embracing ambiguity, making trade-offs, and thinking beyond “it works.” A lot of engineering is deciding between approach A vs B: ship fast vs build for scale, hardcode vs design for future features, and how much risk your team is willing to take. Great engineers don’t just deliver; they leave the codebase better than they found it by caring about readability, documentation, design docs, and maintainability for the next person. Over time, it compounds—like interest—and you start absorbing patterns faster, especially when you learn from senior engineers and study solid design patterns.

Frequently Asked Questions

🎬 More from Tech with Luca