Skip to content

Latest commit

 

History

History
100 lines (65 loc) · 4.55 KB

README.md

File metadata and controls

100 lines (65 loc) · 4.55 KB

Mission Dotlas 🌎

📆 Summer 2024

Python version contributions welcome License

Anaconda Jupyter Pandas

⚠️ Warning

Applicants will be disqualified if they make a public fork of this repository. Create a private fork instead.

Overview

About us

At Dotlas, are building a platform for optimizing & growing retail businesses through AI-driven insights. We've been refining and revamping this assignment for a while now, and we're excited to see what you can do with it! Optionally view past assignments, along with stats in the archives

The Mission

Your mission, should you choose to accept it, is to transform, process and analyze our dataset of Restaurants in The State of California, USA.

Restaurants in San Francisco, according to their Dress Code, height indicates count

We've uploaded our dataset to an interactive map on Foursquare Studio. Feel free to explore it.

Star Wars Map

Getting started

Create a Private fork

Let's create a private fork of this repository:

Install dependencies

python -m pip install -r requirements.txt

You may install any additional dependencies!

Get crackin'

Your mission's details are displayed in mission.ipynb.

Once the repository is created on GitHub, clone it onto your local system! You can solve the assignment from either your local system if you have Jupyter, Python and other dependencies - else you can use Google Colab by uploading the notebook, working on it there and then downloading the notebook back from Colab for your submission.

Refer to HELP.md for some resources to help you get acquainted with the tools you will need.

Evaluation

Submission

Once you're ready for evaluation, invite us as private collaborators to your private fork!

You can invite the following github handles to review your assignment. Ensure to add all handles as collaborators:

Criteria

Submissions will be judged on:

  • Methodology & approach to the solution
  • Readability & maintainability of code (Use of "best practices") by adhering to the Pythonic way

Submission Guidelines

  • Do not create additional branches on your private repository with the submission. Keep all changes on the main branch.
  • Add your answers to the same jupyter notebook file.
  • Do not delete markdown sections of the jupyter notebook. Feel free to add as many sections for documentation or otherwise as you need but don't delete sections already present.

Students copying

May the Force be with you!