7 FAANG Coding Best Practices & Tips (from an ex-Googler)
7 FAANG Coding Best Practices & Tips (from an ex-Googler)
Advertisement

LEAVE YOUR COMMENT

LATEST COMMENTS

@TechLead Says:
The first 500 people to use my link will get a 1 month free trial of Skillshare https://skl.sh/techlead01241
@user-zu4ft8yw9e Says:
1. Understand the Problem: Before diving into coding, ensure you fully grasp the problem statement. Break it down into smaller parts, identify the key components, and think about how you can approach solving it. 2. Design and Plan: Create a clear and concise plan for your solution. This will help you stay organized and focused while coding. Consider data structures, algorithms, and any potential edge cases. 3. Write Clean and Concise Code: Keep your code simple, readable, and maintainable. Use meaningful variable names, follow standard coding conventions, and avoid unnecessary complexity. 4. Test Early, Test Often: Write unit tests and test your code at every stage of development. This will help you catch errors early, ensure your solution is working as intended, and make debugging easier. 5. Optimize for Efficiency: Pay attention to the time and space complexity of your code. Use efficient algorithms and data structures to optimize performance. 6. Handle Edge Cases and Error Checking: Be mindful of edge cases and unusual inputs. Make sure your solution handles these situations gracefully and doesn't produce unexpected results. 7. Refactor and Iterate: Continuously review and improve your code. Refactor when necessary to make it more efficient, readable, or maintainable. This will not only help you grow as a developer but also showcase your dedication to high-quality work. Remember, these tips are not just applicable to FAANG companies, but can be useful in any coding scenario.
@laquainbeckford9393 Says:
Im just gonna say this, if all else fails and we get replaced by AI (our own creation) two words…. Build Malware and sell it DUHHHH
@horoshuhin Says:
great delivery btw. any soft skills tips from a techlead and an employee perspective?
@33mazzystar Says:
Facebook btw
@nyustdent Says:
techlead. we need more of this. even a course that goes into much more detail. super awesome stuff. better than leetcode bs
@arkkiargh9012 Says:
Bob Ross was probably the most consistent artist
@mihaiciobanu2665 Says:
Man, just so you know, the whole eastern Europe is rofling over your existance.
@lukealadeen7836 Says:
I enjoy your more philosophical videos but this is why I subscribed. Lets GO!
@PicyPoe Says:
Please please make a video about ObsidianMD! Programmers f*(&ing love this app, would love to see your ex-Google, ex-Meta honest opinion (roasting) of it!
@shahriyar_alam Says:
Can i chat with you i have a problem
@micbab-vg2mu Says:
Thank you great tips, my strategy is to learn programing enough to be able to ask questions to LMMs to write code for me :) - it works with simple projects.
@SunggukLim Says:
this is actually very basic. documentation and comments are easily outdated. but people who rarely write code prefer to write comments. especially managers
@GoogleAccount-wy2hc Says:
There’s a book called code perfect where it says that max number of lines of code should be 5, though I think it can be more as long as it’s easy to understand what’s going on in 1 minute. So if you name your functions properly, it could be an easy to follow story.
@airiliacats3873 Says:
no longer millionaire?
@jhrhew Says:
came to see if anything special but only found common sense. however, the hardest thing to do is to follow common sense especially in firefighting.
@skeginaldp1533 Says:
Let the AI code for you.
@Denzelzeldi Says:
TechLead finally coming back to his senses? 🤓
@mjm1986bk Says:
Thank you so much for a POSITIVE code video. I will be applying this at work tomorrow. I don't even watch your negative, trolling, comment-seeking videos.
@kevin26exe Says:
Thank you very much for this! :)
@brahmazengi55 Says:
yes i still want to code, contraire to your suggestions in the previous videos. So... thank you!
@radu9150 Says:
Heeeey! i’ve just dropped my CS major due to your last video!! I want my money back👊🫣
@n8ged8 Says:
What about Design Patterns in Coding? I have a master degree (Geoinformatics) but those were not taught. I think they are relevant.
@F336 Says:
10m19...Bro !!!
@seniorsergeanttomcroydon6401 Says:
How's million token going? Should I wait til it hits $1 dollar before buying?
@catrinacraft Says:
Do you know anything about ML Lead or ML Engineer?
@chidimbamalu3490 Says:
Codiing is dead. Crypto is Alive. Now coding...
@kameronbrooks2372 Says:
I forgot that he made coding videos
@AnthonyMarchenko Says:
sir, where is the keyboard from the previous video?
@cathrynm Says:
Total agree on the 'never refactor.' It is a total junior move to want to refactor everything.
@Rocketbunny180sx Says:
Any thoughts on game development as an intermediate path? It falls under Digital Media, but still requires (some) coding.
@simhgamedev Says:
Sometime You could come here: I program as well... this would be in HungarY, not all that complication thanks to aircraft tecnics. I am circa 120 KM from Budapest. Not all that big dial.
@NathanVu Says:
FAANG? More like FAAG. What's Netflix doing there? Netflix is a one product company and that one product is unsustainable.
@piff57paff Says:
I agree with almost everything mentioned, except "never refactor". Code structure is often a result of requirements and assumptions. Both can and will change over time, if the product is existing long enough and is evolving. This leads to your code base reflecting an outdated view of reality that can manifest itself in weird or inefficient call patterns or structure that doesn't fit anymore. In that case refactoring should be done, to reduce cognitive load. It shouldn't be risky, if you are using the tools the IDE provides, and anyway you should have good test coverage, that would uncover issues.
@jeremystanley9395 Says:
Dead coding society lol😂, deleted 300000 lines of code, that’s 300000 people that do not like you😂
@chris_ea Says:
Thanks
@elcapitan6126 Says:
dunno why but after years of seeing knowing practicing and developing "best practices" it all seems a bit meaningless and things come full circle back to "everythings a tradeoff and its never clear what set of tradeoffs were actually valuable for any project at any given point in time given the context within a wider rather chaotic business and economic world. people (especially online) really overcook and oversell "coding" and software engineering in general. such is life (it's quite similar to other practical disciplines in this regard)
@standaterziev5511 Says:
Not only has this genius worked for couple of months in Google, he is a millionaire. As a millionare, he gives you this very vAlUaBle advice. Better listen dear coders. tHiS iS TecHLeAd himself. Glorious
@demonwaterdemonwater4993 Says:
who invented calculus archemedes? or just random people in eall over the world..
@BrayanMartinez-wp9vh Says:
Does anyone know which programming languages he knows?
@ilyabogretsov7028 Says:
Don't agree about comments. It is a bad example in the video. Your comment should explain not WHAT it does, but WHY.
@parikxit Says:
sorry, where were you Tech-Lead at?
@rbalsdldiify Says:
These kinds of contents are the reason why I subscribed to this channel in the first place. I really appreciate you TechLead.
@cybersphere Says:
Yesterday: Coding is dead. Why I am not a coder. Today: 7 Top FAANG coding tips
@KalebSDay Says:
Nice seeing this side of you again TechLead, wishing you a Happy New Year! Appreciate the insight/tips to keep in mind. The don't refractor one just to make it look pretty is a really good one that I might not have considered as heavily before hearing it from you.
@weishi5286 Says:
After I watch this video, YT auto play ▶️ recommended me to watch his "coding is dead" video 😂
@UncleFreedom777 Says:
Great Video
@user-di4bt7qu2i Says:
Wow, these are some excellent coding tips. Thanks for posting!
@svintheanajones88 Says:
I only comment my code with TODOs. It's helpful to know what you need to do, and potentially where it should go. I rarely add other types of comments. In the 90s I did comment my code because all of my variables were nondescriptive. That was the style back then and all of those lines of code should be deleted.
@DaveStewartLondon Says:
When did you get so nice!?

More Programing Videos