So your goal in reading this should be to identify the pieces of what he says that you should incorporate into your own judgement. Otherwise, you're going to give yourself a sort of writers-block.Ģ) "How do I write good code?" is fundamentally a matter of engineering judgement. So if you can't ignore the timer and reliably pass leetcode-easy problems, then focus first on the basic ability to manipulate strings/lists/dictionaries and write functions. If you are starting your learning-to-program journey, then it will make you overly self-critical.
Consequentlyġ) Read it only after you're confident in your ability to write code at all. It is a well-written and thoughtful example of that genre.
It falls into the genre of "opinions about how to write good code". Building Billion user Load Balancer at Facebook: Īdded some of the links/resources people commented.Youtube channels/playlists that I found helpful: Here's a consolidated list of company-wise engineering blogs:.Grokking Algorithms (free to read online).Elements of Programming Interviews" by Adnan Aziz, Tsung-Hsien Lee, and Amit Prakash (2nd edition).Programming Interviews Exposed" by John Mongan, Noah Suojanen (3rd edition).The Google Resume by Gayle Laakmann McDowell (1st edition).Designing Data Intensive Applications by Martin Kleppman - this is a more in-depth book, and you can get it on Amazon/libgen.Distributed Systems for Fun and Profit - free book, 100 pages or so, but excellent content.Cracking the Coding Interview by Gayle Laakmann McDowell (6th edition).Catalog of all FAANG interview information on Rooftop Slushie.Grokking the System Design Interview *this isn't free but widely used.My goal is to create a master list so everyone knows about which resources might be helpful.
If you have any resources that worked for you, let me know and I'll add it onto this list. With the holidays coming up, I wanted to share some mostly free resources (well the books and some courses aren't free) that I've used for preparation in the past. We could always do with more help and wisdom, friend! The better the FAQ, the harder we can come down on lazy posters with low-effort OPs, which means a higher quality subreddit experience for you.
Please don't start new threads about these topics without getting mod permission first, lest we be forced to. In addition to a chat thread that's newly spawned every day, we have a daily rotation for threads for certain topics. These are only posted by mods, following the schedule listed in the FAQ. More info about the salary survey can be found on the subreddit wiki. Share your current compensation and review the data submitted by other users in the two links above. These are the old responses to the previous survey The survey and response spreadsheet have been updated as of November 23, 2018. Tl dr: darker colors = more posting experience here. Noticed some cool user flair around? Take a look at this thread to see what it's all about. Second: Check out this awesome "quick answers to common questions" threadįourth: Search for prior posts on the subject Please note that we, the CSCQ mod team are not in charge of this discord. Please check it out for your chatting needs: DiscordĬSCQ regular u/Kevincav runs a discord called CS Career Hub. Please keep the conversation professional, adhere to the reddiquette, and remember to READ OUR RULES.
Here we discuss careers in Computer Science, Computer Engineering, Software Engineering, and related fields. Welcome, one and all, to CSCareerQuestions!