Feature #1: Missing Items and Multiple Totes

Background: The Feed integrated a state-of-the-art robotic picking system to fulfill orders. Robots pick items into totes and deliver them to a human to pack the order.

Goals:

• Support high-volume orders that need to be picked into multiple totes
• Allow a Packer to indicate when an order is missing items

Skills: Schema Design, API Integration, Refactoring, UI/UX

Demo:

In this video you can see the interface for a Packer gathering multiple totes that are part of the same order. You will then see the Packer indicate that items are missing for the order. Finally, the Packer stores the order while the missing items are picked.

In addition to the UI, I implemented a large refactor in the backend to support an order's association to multiple totes. I also implemented the API requests to the robotic picking system to pick the missing items.

Feature #2: Floor Pick Batches

Background: The Feed wanted their human workers to be able to hand pick orders to supplement their robot pickers when order volume was particularly high or the robot system needed maintenance.

Goals:

• Direct Pickers to the best storage location to hand pick items
• Require Pickers to scan the item(s) once to confirm the item is correct
• Batch orders so that a Picker can complete multiple orders simultaneously
• Create an index of batches sorted by number of orders

Skills: Query Optimization, UI/UX, Collaboration, Project Management

Demo:

In this video you can see the index of all batches of orders grouped by common products. You will then see the Picker start a batch, scan the item once to confirm it is correct, and retrieve multiples of the product to complete 7 orders at once.

Feature #1: Slack Attendance

Background: When students are not in class they indicate they are present for their school activities by responding to a Slack message.

Goals:

• Automatically record student attendance through a Slack message link

Skills: API Integration, Feature Design, UI/UX

Demo:

In this video you can see how an instructor can take attendance by copy and pasting a Slack message link. The application will make a call to the Slack API to determine whether a student was present, tardy, or absent.

Feature #2: Zoom Attendance

Background: Turing students participate in classes via Zoom. The Zoom API does not provide unique identifiers for meeting participants outside of the organization, so the application uses the participant name to identify a student. This presents a unique challenge for the application since students can change their names in Zoom meetings.

Goals:

• Automatically record student attendance through a Zoom message link
• Allow instructors to associate multiple participant names in Zoom with a student record

Skills: API Integration, Schema Design, Polymorphism, DRY Code, Refactoring, Perserverance

Demo:

In this video you can see an instructor resolving an issue where a student changed their Zoom name to include their pronouns.

Feature #3: Populi Transfer

Background: Instructors are required to record attendance data in a separate Student Information System called Populi. This process can be very tedious when done by hand.

Goals:

• Automatically transfer attendance records through the Populi API.

Skills: API Integration, Background Jobs, Retries

Demo:

In this video you will see the Populi transfer process. The instructor manually creates the default attendance records in Populi and then completes the automated transfer.

Feature #4: Reporting

Background: Turing needs to generate attendance reports for students across date ranges for the Department of Education and their accrediting body.

Goals:

• Create attendance reports with the option to download as CSV
• Break down attendance reports by eligible hours, earned hours, and type of credit hour

Skills: Schema Design, Query Optimization, Project Management, Collaboration

Demo:

This video demonstrates the app's functionality for generating student attendance reports.