This repository has been archived by the owner on Dec 18, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We recently had a candidate come into the backend interview set up to work in Ruby on Rails. That's fine and dandy except the candidate leveraged a Postgres database and the Rails ORM to do all of the heavy lifting. I think having such a bare example in this repo can set the wrong expectation coming into the interview, so I've added an
Allocator
class stub here that could hopefully clarify the expectation that we will ignore the web framework for a portion of the interview.I wanted to also add something like
to emphasize work to be done in-memory, but felt like that might be a bit too suggestive - thoughts?