​

I’m learning Java as a beginner, and I tried to make my first "Hello World" program easier to understand by breaking down each keyword with simple explanations.

I covered "public", "class", "static", "void", "main()", "String[] args", and "System.out.println()".

Instead of just memorizing the code, I want to understand why each part is used and how it works.

I’d love to hear feedback from experienced Java developers and fellow learners. What should I improve in these notes?

#Java #LearnProgramming #CodingForBeginners

Sorry about the long read. Your suggestion would mean the world.

I’m 27 and recently left my Customer Service job at Amazon. I graduated in 2022, but my degree has nothing to do with CS or tech.

I’ve always wanted to get into software development, especially backend development, but for a long time I couldn’t really afford to take the risk because of financial responsibilities.

Things are in a better position now. I live alone and my brother supports my family, so my main expenses are basically my rent, food and feeding my cats. I also go out and deliver food for Zomato around 3 days a week.

It makes enough to cover my rent and food and lets me save a little without touching my existing savings. I have around 1.5 years of savings if I need it.

The main reason I finally left Amazon is that I felt completely stuck. The growth opportunities were honestly pretty shit. I was told by my manager about a program called ATLAS that Amazon had to help non tech employees move into tech roles.

I thought this was finally my chance, so I stayed for another 2 years hoping I would eventually get selected.
Never happened. No exams, no interviews, nothing. Every time I asked, I was basically told the slots were filled.

This went on for years and I eventually realized I was just wasting time waiting for something to happen.
So now that I’ve left, I finally have time to actually invest in myself.

I’m currently working through Java fundamentals then plan to cover OOP, DSA, SQL, Spring Boot, REST APIs, databases, Git and eventually building proper backend projects.

But I honestly have no idea if I’m being realistic here.
Can someone who has actually worked in tech or made a similar transition tell me if I have a real chance of getting an SDE job in the next 1 to 1.5 years?

If yes, how would you spend that time if you were in my position? What should I focus most on and realistically, what are my chances if I actually put in the work consistently?

I know the degree situation is probably going to make things harder, but I’d rather hear the harsh truth now than waste another 1.5 years.

Thank you so much for reading.

What do you think?

Going to join college, is software development worth it

hey This is my first post in Reddit.

just wanted people who are from java springboot .....

I made this to study and thought I'd share it:

https://jhb010311.github.io/dev-learning-lab/en/

You change the settings, click Run, and step through what happens. Free, no sign-up.

If you spot something wrong, let me know.

https://github.com/jhb010311/dev-learning-lab

I’ve been learning Java and building projects, and I want to start contributing to open source to improve my skills and gain experience working with real-world codebases.

Which actively maintained Java projects would you recommend for someone getting started? I’m particularly interested in backend development, Spring Boot, databases, and related technologies.

I’d also appreciate any advice on finding beginner-friendly issues, understanding an existing codebase, and making my first meaningful pull request.

Is is pragmatic??

https://github.com/Java-eject-sustainable-unlimited-system/Jesus_system

https://github.com/Java-eject-sustainable-unlimited-system

someone built an open-source Java watchdog for service resilience. What would you improve before using it in a production environment?

I wanted to see this one with my own eyes, so I typed it into jshell. Output is below with notes in between.

jshell> class Point {
   ...>     int x;
   ...>     Point(int x) { this.x = x; }
   ...>      public boolean equals(Object o) {
   ...>         return o instanceof Point p && p.x == x;
   ...>     }
   ...>     u/Override public int hashCode() { return Integer.hashCode(x); }
   ...> }

jshell> var set = new HashSet<Point>();
jshell> var p = new Point(1);
jshell> set.add(p);
$4 ==> true

Nothing odd yet. equals and hashCode both use x, which is what most IDEs generate.

jshell> p.x = 2;
jshell> set.size()
$6 ==> 1

jshell> set.contains(p)
$7 ==> false

jshell> set.remove(p)
$8 ==> false

This is the part that surprised me. The set says it has one element, and it says it doesn’t contain the exact object I’m holding a reference to. remove fails too.

jshell> for (Point q : set) System.out.println(q == p);
true

Iteration finds it. Iteration just walks every bucket, no hashing involved. contains and remove compute hashCode() first (now based on 2), go to that bucket, and find nothing. The object is still sitting in the bucket picked when its x was 1.

As far as I understand it, there’s no error because HashSet never learns the object changed. It only looks at the hash at insertion time and again at lookup time. If the two differ, you get a silent miss.

So the object is still in the set but unreachable by key. That’s the part that would be annoying to debug in a real codebase: size is right, iteration is right, lookups are wrong.

Things I’ve seen suggested for this:

• keep fields used in hashCode final (records do this by default)
• if the key has to change, remove it first, change it, add it again
• use an immutable key type, like a String or a Long id, instead of the whole entity

Question for people who’ve worked on bigger projects: do you ever see this with JPA entities used as keys in sets, where the id is null before persist and set afterward? I’d guess it’s the same problem in a different outfit, but I haven’t tried it.

Hi everyone!

I’ve created a tutorial showing how to design a modern School Management System Dashboard using Java Swing, step by step.

The tutorial is useful for Java beginners, computer science students, and developers who want to improve their Java Swing UI design skills.

If you’re interested in desktop application development with Java, feel free to check it out!

I’d appreciate your feedback and suggestions for improving the design.

What do you think about building modern desktop dashboards with Java Swing in 2026?

#Java #JavaSwing #DesktopDevelopment
👇👇👇
Watch it Here

Hey everyone!

While working on my Java projects, I got annoyed at how often I had to write the same kind of code for everyday file operations and text processing. Reading and writing files, appending content, copying files, counting words, searching directories, and getting file metadata started feeling repetitive.

So I decided to build FilzaFiles, a small Java utility library that wraps these common operations into reusable methods.

Some things it currently supports:

• Creating, reading, writing, appending, copying, moving, and deleting files
• Creating file backups
• Counting words, Unicode characters, lines, paragraphs, and approximate sentences
• Replacing text in strings and files
• Recursively searching by filename or extension
• Inspecting file metadata

I have released v0.1.0 with a downloadable JAR. I also tested it with a separate Java application and ran 22 integration checks, all of which passed.

Project: https://github.com/Peshimam-Ashar-Mohammed/FilzaFiles

Download: https://github.com/Peshimam-Ashar-Mohammed/FilzaFiles/releases/download/v0.1.0/filzafiles-0.1.0.jar

It requires Java 21 or later. It isn't on Maven Central yet, so the README explains how to integrate the JAR into a regular Java project or a Maven project.

I'd genuinely appreciate feedback from other Java developers:

• Does the API feel intuitive?
• Are there any design decisions you'd change?
• What edge cases or tests am I missing?
• Are there useful file or text utilities you'd want to see added?

This is my first release of the library, and I'm hoping to improve it based on real developer feedback. Criticism is welcome!

Thanks for checking it out!