-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Interview Questions #59
Comments
I think we should be cautious about how we structure this One thing I want to be wary of is how bloated this book becomes. Based off of my observations from this sem, students use the coursebook to brush up on/learn core concepts and work on MPs/prepare for quizzes. I think this issue should be a comment under #48 and #48 should be implemented by having a questions section at the end of every chapter (like textbooks generally do) I think that #47 could also be implemented by having "spot the bug" sections in some chapters. |
They don’t have to be solely focused on getting you a job. One of the things some instructors see in this course that is lacking is the “applied” section. Like we tell then what malloc is and what are a bunch of allocators, but never pick their brains as to what is the best allocator for X and Y (we may still use the game development anecdote for the malloc section). Basically trying to stoke CS students analytical skills with coming up with interview-y questions (we have a few stored up in that realm). To be honest at this stage, I’m fine with more content that can be moved to optional chapters. The book is like 300? Pages including all the extra content. |
I definitely see why you want to include them, I'm just saying that we don't want the book to become a chore to navigate and as the size of the book increases, we should be tactful in how we present information/content. |
I'm thinking another chapter, like post mortems. |
While the coursebook should primarily be a coursebook, the staff have accumulated a -- non-nda protected -- list of systems questions that some companies like to ask in addition to content covered like systems design. It'd be cool to add some answers that staff would give, and encourage people to break down the topic and use the tools learned to solve it.
The text was updated successfully, but these errors were encountered: