Task Manager.

My first proper Java project—and the moment class boundaries started to feel useful.

PERSONAL BUILD · COMPLETECORE JAVA · OOP · COLLECTIONS

GitHub repository ↗

TaskService.java

01 Map<Long, Task> tasks;

02 createTask(task);

03 try { save(task); }

04 catch (Exception e)

05 learnSomething();

01 / THE PROBLEM

A small build, designed to stay understandable.

I wanted a project that would force me to use classes for a reason—not simply write one giant main method. The goal was a small task manager with a clear model, a service layer, and a straightforward command-line flow.

02 / DESIGN DECISIONS

Task model

Keep the task data and its status together in a small, understandable model.

TaskService

Put create, read, update, and delete operations in one service instead of burying them in menu code.

HashMap

Use an in-memory Map for the first version. Persistence can come later, after the core flow is clear.

Error handling

Make missing tasks and invalid operations explicit so the program can explain what went wrong.

← Back to the project explorer Talk about a project ↗View Sayan’s GitHub profile ↗