# Drivy Backend Challenge

## Guidelines

Fork this repo.
Solve the levels in ascending order, an commit your code at the end of each level.
You can have a look at the higher levels, but please do the **simplest thing** that could work for the level you're currently solving.

Disclaimer: the levels become more complex over time, so you will probably have to re-use some code and adapt it to the new requirements.
A good way to solve this is by using OOP and adding new layers of abstraction only when they become necessary.
Don't hesitate to write [shameless code](http://red-badger.com/blog/2014/08/20/i-spent-3-days-with-sandi-metz-heres-what-i-learned/) at first, and then refactor it in the next levels.

For higher levels we are interested in seeing code that is:
- clean
- extensible
- robust (don't overlook edge cases, use exceptions where needed, ...)


## Things to know

- all prices are stored as integers (in cents)
# Drivy Backend Challenge

## Guidelines

- fork this repo
- solve the levels in ascending order
- commit your code at the end of each level
- once you are ready, add someone from drivy to the repo so that we can review your code

You can have a look at the higher levels, but please do the **simplest thing** that could work for the level you're currently solving.

Disclaimer: the levels become more complex over time, so you will probably have to re-use some code and adapt it to the new requirements.
A good way to solve this is by using OOP and adding new layers of abstraction only when they become necessary.
Don't hesitate to write [shameless code](http://red-badger.com/blog/2014/08/20/i-spent-3-days-with-sandi-metz-heres-what-i-learned/) at first, and then refactor it in the next levels.

For higher levels we are interested in seeing code that is:
- clean
- extensible
- robust (don't overlook edge cases, use exceptions where needed, ...)


## Things to know

- all prices are stored as integers (in cents)
Fix typo, make guidelines clearer
Fix typo, make guidelines clearer
