Write
Start with the smallest version that can work.
SOFTWARE / DATA / SYSTEMS
Software,
with a point of view.
Always in progress.
FIELDNOTE / VISUAL STUDYFIG. 01
JAVA / FIELD STUDY
CLASS → OBJECT → RUNTIME
01 / 01
WORK IN PROGRESSTHINK → BUILD → REFINE
THINK.MAKE.LEARN.
01 / THE SHORTLIST
Proof of work,
not a list of buzzwords.
Three projects. Three different kinds of thinking. Start with the one I’ve been building most recently, then explore two earlier experiments.
FLAGSHIP / 001CORE JAVA
TaskService.javaLOCAL BUILD
01Map<Integer, Task> tasks;
02 createTask(task);
03try { save(task); }
04catch (Exception e)
05 learnSomething();
OOP / COLLECTIONSBUILD · DEBUG · DOCUMENT
MAKE IT
MAKE SENSE.
A SMALL APP. A LOT OF LEARNING.
MAKE SENSE.
THE FEATURED BUILD ITERATING
Task
Manager.
My first proper Java project: a command-line task manager built to understand classes, responsibilities, task states, and how to handle failure without hiding it.
01 Separate the model and service02 Make state explicit03 Document decisions, not just methods
WANT TO READ THE CODE?Explore my GitHub ↗
02 / PYTHON + SQLITE
₹
A LITTLE SYSTEM WITH REAL RULES.
PERSISTENCE · OOP · SECURITY BASICS
Command-Line
Banking System ↗
A practical exercise in keeping state, storing records, and hashing PINs rather than treating them as plain text.
03 / DATA + EXPERIMENT
KOLKATA / WEATHER SIGNAL
MACHINE LEARNING · VISUALIZATION
ForecastML — Kolkata ↗
A forecasting experiment using historical weather data, Random Forest regression, an API, and interactive charts.
A NOTE FROM MY DESK
Still learning.
Very deliberately.
I started with Python and data projects, joined hackathons, then realised I enjoy Java’s structure and the discipline of backend work. I’m not trying to look like a senior engineer. I’m trying to become a good one.
CURRENT FOCUSCore Java → Spring Boot → APIs
02 / THE WORK LOG
How I get from
“it compiles” to “I get it.”
One night recently, my Task Manager took shape through the ordinary loop: implement, compile, read the error, fix it, document it, push it.
Break
Trace the error instead of guessing.
Refine
Separate responsibilities and document decisions.
Ship
Push it, explain it, then improve it.