DEV Community: CatNight A

Learning Java Became Easier When I Stopped Memorizing Code

CatNight A — Thu, 18 Jun 2026 03:37:29 +0000

I’m a software engineering student, and when I first started learning Java, I thought I had to remember a lot of code
examples.

Classes, methods, syntax, collections, constructors, interfaces.

I tried to remember the exact code.

But the problem was simple: if I forgot one line, I felt like I forgot everything.

Later I found that what helps me more is remembering the structure behind the code.

For example, when I look at a Java class now, I do not start by memorizing every line.

I ask myself:

What data does this class hold?
What behavior does it provide?
What should be private?
What should be public?
What is created in the constructor?
What other class depends on it?

That helps me understand the “shape” of the class.

The same thing happens with collections.

I do not try to memorize every method first.

I try to remember the idea:

List: ordered data
Set: no duplicates
Map: key-value relationship
Queue: processing order

After I understand that, the methods are much easier to search and use.

For backend Java, I think in layers:

Controller receives the request
Service handles the logic
Repository talks to the database
DTO moves data
Entity represents stored data

When I understand the flow, the code becomes less scary.

I still forget syntax.
I still search method names.
But I feel less lost, because I can rebuild the code from the structure.

For me, the difference is:

If I memorize code, I can only repeat it.

If I understand the structure, I can recreate it.

Do you also learn programming this way, or do you prefer memorizing examples first?

I think I track learning too much like a todo list

CatNight A — Wed, 17 Jun 2026 15:29:33 +0000

Lately I realized I track learning almost the same way I track tasks.

Watch this video.
Read this doc.
Finish this course section.
Build this small thing.

I check things off, and it feels good for a minute.

But a few days later, I still have the same question:

Did I actually get better, or did I just finish some stuff?

For coding, this feels especially weird.

I can spend a week jumping between docs, bugs, tutorials, Stack Overflow answers, and little experiments. By the end of the week, I definitely
did things. But it is not always clear what improved.

Maybe I understand async a bit better.
Maybe I got faster at debugging CSS.
Maybe I learned one database concept.
Maybe I just watched too many videos.

A todo list does not really show that.

I have tried notes, Notion pages, spreadsheets, and GitHub commits. They all help in some way, but they still feel more like a record of
activity than a record of skill growth.

I am not sure what the better system is yet.

Maybe it is a weekly review.
Maybe it is tagging learning by skill.
Maybe it is some kind of visual map.
Maybe it is just writing better notes.

Curious how other people think about this.

When you learn something technical, do you track what you finished, or do you try to track what you actually got better at?

How do you track your learning progress as a developer?

CatNight A — Tue, 16 Jun 2026 08:33:28 +0000

When learning as a developer, I find that "I studied today" is easy to know, but "I am getting better at the right things" is harder to see.

I have seen people use very different systems:

GitHub commits
Notion databases
spreadsheets
Markdown journals
Anki stats
project milestones
issue trackers
no tracking at all

I am curious what actually works after the initial motivation fades.

For developers who are self-learning or learning alongside work:

What do you track?
Where do you track it?
Do you review it weekly or monthly?
What made you abandon previous tracking systems?
Do visual systems like heatmaps, skill trees, or progress bars help?

I am exploring this problem for a small tool, but this post is mainly to understand real workflows. I would rather learn from how people already do it than assume another dashboard is the answer.