OOP - lesson 7 | HackIndia Skills

Key point

Proof beats claims

Your repo is the proof. A recruiter should see the feature, run it, and understand your object model in a few minutes.

Do not submit only class diagrams or copied notes. Submit working code with a small, real feature.

Pick one feature

Choose a feature small enough to finish and large enough to show objects working together. Think hostel room booking, UPI expense split, canteen order billing, event registration, or library fine calculation.

Your feature should have 3 to 6 classes. It should show composition, interfaces, or clear SOLID choices from earlier lessons.

Your to-do

Repo checklist

Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.

Create a public GitHub repository with a clear name.
Add your source code in a simple folder structure.
Add tests, or add a sample run command with expected output.
Write a README that explains the feature, classes, and how to run it.
Commit small changes with messages a human can understand.

0 of 5 done

Example

README starter

Use a short README. Avoid long theory. Explain the model like you would to a senior in your college coding club.

# Canteen Order Billing

## Feature
Calculates the bill for a canteen order with items, quantities, taxes, and payment method charges.

## Object model
- MenuItem stores item name and price.
- OrderLine combines a MenuItem with quantity.
- Order contains many OrderLine objects and calculates subtotal.
- PaymentMethod is an interface for payment-specific charges.
- UpiPayment and CardPayment implement PaymentMethod.
- BillService uses Order and PaymentMethod to create the final bill.

## How to run
python main.py

## Sample output
Subtotal: 120
Payment charge: 0
Total: 120

## Why this is OOP
The feature uses composition because Order has OrderLine objects.
PaymentMethod keeps payment rules separate from billing logic.

Tip

Use AI carefully

You can ask ChatGPT, Gemini, or Claude to review your README and object model. Ask for clarity, not for fake complexity.

Check every suggestion. Remove extra patterns, unused classes, and words you cannot explain in an interview.

Prompt:
Review this README for a beginner-friendly OOP project. Tell me if the object model is clear, if any class looks unnecessary, and if the run steps are missing anything.

Paste README here.

Common mistake

Do not hide failure

A repo with code but no way to run it feels unfinished. A repo with a broken command wastes the reviewer’s time.

Before you submit, clone your own repo into a fresh folder and run the exact README steps. If it fails there, fix the README or the code.

Your to-do

Submit on HackIndia

Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.

Push your final code to the public repo.
Open the repo in a browser and confirm it is not private.
Copy the repository link from the browser address bar.
Submit the link in your HackIndia project submission.
Add a short note naming the feature and the main OOP idea used.

0 of 5 done

Your to-do

Do this now

Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.

Choose one feature you can finish today.
Create the public repo and add a README file.
Write the object model section before adding more code.
Add one test or one sample run with expected output.
Run the README command once from a fresh folder.

0 of 5 done

Build and submit your repo

Proof beats claims

Pick one feature

Repo checklist

README starter

Use AI carefully

Do not hide failure

Submit on HackIndia

Do this now

Quick check