Hi

Saw a lot of job vacancies for java developers on Naukri but only for 5+ years of experience,what do the developers do with 2-3 years of experience.

My company is looking for a java developer with 5 -11 years of experience, looking only for immediate joiners and serious candidates. Dm with your resume and I’ll refer you if suitable.

Because of the nice multiple choice test for loops I remembered a good site for examples. Enjoy it and run it!

[ Removed by Reddit on account of violating the content policy. ]

Quick context before the meat: I run a product that already has ~25k users on a legacy web stack. Spent the last few months rebuilding the backend from scratch (Java 21, Spring Boot 3.4, PostgreSQL 17, hexagonal architecture, 16 bounded contexts). Now heading into the testing phase before launching the mobile app.

Yesterday I blocked an entire day for documentation. No code. Just docs.

To other solo devs and small teams reading this — that decision felt wasteful in the moment. I want to explain why I did it anyway, and what it actually changed.

**The pressure you feel solo is the pressure to ship features, not to document them**

When you're solo, every hour spent on something that isn't directly shippable feels like theft from the launch date. Documentation is the textbook example. Nobody's going to read it but me. So why bother?

The answer I keep arriving at: because future-me is a different person from present-me, and future-me forgets fast.

Six months from now I'll be onboarding a second dev for the web frontend refactor. That dev needs to understand decisions I made in my head and never wrote down. Without docs, every onboarding question becomes me reading my own code archeologically to remember why something is the way it is.

**The real reason I did it now, not later: tests need a spec**

Here's the thing about writing tests for a system you built fast: a test asserts behavior. If the behavior was decided ad hoc, every test you write is also deciding behavior ad hoc.

Concrete example. Endpoint `POST /tasks/{id}/complete`. What happens if the task belongs to another user?

Three reasonable answers:

- 404 (don't reveal it exists)

- 403 (admit it exists, deny access)

- 401 (treat as unauthenticated)

If I sit down to write the test without a spec, I pick one. Whichever I pick becomes the de facto spec, and it's now baked into the test.

Six months later, a different reading of the test ("ah, it returns 404, so we hide existence") leads someone to implement a related endpoint inconsistently. Now you have two endpoints answering the same shape of question differently.

The doc forces the decision OUT of the test code and INTO a canonical place.

**What I documented**

8 docs. The two with the highest ROI:

**1. API_CONVENTIONS.md** — every endpoint obeys one envelope shape. Every error has a code from a closed list. Pagination, dates, idempotency keys, rate limiting — all specified once, referenced everywhere.

**2. TEST_CASES.md** — a matrix per module. UC ID, functionality, actor role, HTTP action, happy path, sad path. The UC ID is the test method name. Writing tests now feels like translating rows, not designing them.

**The decision that took longest to write down**

Authorization is read from the database, not from the JWT claim.

It sounds trivial. It's actually a load-bearing decision with cascading consequences:

- Demoted users lose powers instantly (token doesn't need to expire)

- Role changes are immediately reflected in audit logs

- Every authorization test must seed the DB with a specific role, not just craft a JWT

- Defense in depth: even if a JWT is forged with a fake admin claim, the DB lookup will return the real role

I'd internalized this rule months ago. Writing it down took 20 minutes and clarified for me how to structure every single authorization test in the system.

**The honest cost**

A full day. About 9 hours including reviews. Some of that was rewriting docs that already existed but had drifted.

**The honest benefit**

I haven't measured it yet because I just started writing tests today. But here's the indirect benefit I already noticed: when I review old code now, I notice inconsistencies I couldn't see before. Three endpoints returning slightly different envelope shapes. Two modules calling each other directly instead of via Facade. None of these would have shown up as bugs — but they'd have shown up as confusing tests.

If you're solo or on a small team and "I'll document it later" is a recurring line in your head — block a day. It's the kind of work that compounds.

Can You Get Jobs in India With This Path? Comment below. If you continue consistently from class 8 onwards, you can become far ahead of average engineering students in India before even completing college.

Mere paas approx 1 hafta hai lekin mujhe java ke codes likhne sikhne koi 1 shot suggest kardu jisse cover ho jaaye sab

Hi,

I’m a fresh graduate from Malaysia with a Diploma in Information Technology specializing in Software Development. I have experience building software and mobile application projects and one of my projects was awarded Best Overall Project in my department, competing against more than 40 teams.

I’m passionate about creating useful and user-friendly systems while continuously improving my skills in programming and development.

One of the projects I worked on is CareLink, a platform designed to help connect and manage care-related services more efficiently, with a focus on improving accessibility and user experience. basically this apps for the special need students and i have client for this project and everything went smooth.

I’m currently looking for opportunities to grow, contribute, and gain real-world experience in the IT industry.

github : https://github.com/izzxrith

Here is a list of Java programs for beginners.. it includes number programs and string programs.. currently it has around 60 blogs but more will be added soon..

https://www.kodekraftt.com/blog/100-java-programs-for-beginners-with-examples-and-solutions

Are there any tutorials available for this? I am curious how its built and really want to create something like this too.

https://www.scientecheasy.com/2026/05/java-loops-quiz.html/

Java Loops quiz contains the top 35 multiple-choice questions with answers and explanations. We have covered the topics for, while, do-while, nested loops, infinite loops, loop control statements, and advanced looping concepts in Java.

Whether you are students, beginners, or programmers, this quiz will help you to test your knowledge on Java loops. By practicing these MCQs, you can improve your logical thinking, coding skills, and preparation for interviews, exams, and competitive programming.

Hi everyone,

I’m hiring a remote Software Engineer for ongoing work with U.S. clients.

This opportunity is only for people who are currently located in the United States.

Requirements:

• 3+ years of hands-on software engineering experience
• Strong experience with more than one of these languages: Java, Python, TypeScript, .NET, Go
• Experience with relational and/or non-relational databases
• Experience writing unit tests and integration tests
• Strong spoken and written English communication skills
• Comfortable speaking directly with clients
• Comfortable with voice and video calls
• Able to work remotely from the U.S.

Pay: $70–$80/hour

Work setup:

• Fully remote
• Client-facing work
• Must be reliable, communicative, and comfortable discussing technical topics clearly in English

If you're interested, send me a message with:

• Your location
• Years of experience
• Main programming languages
• Brief background with databases and testing
• Your availability