Java Programs for Practice

// Basic Java Structure
public class Main {
    public static void main(String[] args) {
        System.out.println("Practice Java Programs");
    }
}

// 1. Print Hello World
class HelloWorld {
  public static void main(String[] args) {
    System.out.println("Hello World");
  }
}


// 2. Swap two numbers
class SwapNumbers {
  public static void main(String[] args) {
    int a = 10, b = 20;

    int temp = a;
    a = b;
    b = temp;

    System.out.println("a=" + a + " b=" + b);
  }
}


// 3. Check Even or Odd
class EvenOdd {
  public static void main(String[] args) {
    int num = 7;

    if (num % 2 == 0) {
      System.out.println("Even");
    } else {
      System.out.println("Odd");
    }
  }
}


// 4. Print Multiplication Table
class MultiplicationTable {
  public static void main(String[] args) {
    int num = 5;

    for (int i = 1; i <= 10; i++) {
      System.out.println(num + " x " + i + " = " + (num * i));
    }
  }
}


// 5. Sum of Digits
class SumOfDigits {
  public static void main(String[] args) {
    int num = 1234;
    int sum = 0;

    while (num > 0) {
      sum += num % 10;
      num /= 10;
    }

    System.out.println(sum);
  }
}


// 6. Reverse Number
class ReverseNumber {
  public static void main(String[] args) {
    int num = 1234;
    int rev = 0;

    while (num > 0) {
      rev = rev * 10 + (num % 10);
      num /= 10;
    }

    System.out.println(rev);
  }
}


// 7. Print Star Pattern
class StarPattern {
  public static void main(String[] args) {
    for (int i = 1; i <= 5; i++) {
      for (int j = 1; j <= i; j++) {
        System.out.print("*");
      }
      System.out.println();
    }
  }
}

• 1 Improve logic building
• 2 Prepare for interviews
• 3 Understand syntax
• 4 Build confidence in coding

• 1 Basic programs
• 2 Loop programs
• 3 Array programs
• 4 Pattern programs

• 1 Loops and conditions
• 2 Strings and arrays
• 3 Math problems
• 4 Patterns

• 1 Start with basics
• 2 Repeat daily practice
• 3 Solve interview questions
• 4 Increase difficulty gradually

• 1 Used for beginner programming practice.
• 2 Used in coding interviews preparation.
• 3 Used in college lab assignments.
• 4 Used to build logical thinking.
• 5 SaaS products use Java Programs for Practice in services, dashboards, background jobs, and API workflows.
• 6 ERP and banking systems apply Java Programs for Practice with validation, logging, review, and rollback plans.
• 7 E-commerce and healthcare platforms use Java Programs for Practice carefully because reliability and data correctness matter.

• 1 A Java program first evaluates the surrounding context, then applies the Java Programs for Practice rules to the current data.
• 2 The important mental model is input, transformation, result, and failure path.
• 3 In production, the same flow usually sits inside a larger layer such as a controller, service, repository, job, or UI component.

• 1 Choose the simplest implementation first, then measure real workloads.
• 2 Watch for repeated work inside loops, unnecessary allocations, and slow I/O in hot paths.
• 3 Prefer clear data structures and stable APIs before micro-optimizing syntax.

• 1 Treat external input as untrusted until it is validated.
• 2 Avoid hardcoded secrets and never print sensitive values in examples or logs.
• 3 Use established libraries for authentication, encryption, parsing, and database access.

• 1 Writing conditions that overlap or miss boundary values.
• 2 Creating loops that never terminate.
• 3 Nesting control flow until it becomes hard to read.
• 4 Skipping the small working example before adding framework code.
• 5 Ignoring null, empty, duplicate, and boundary inputs.
• 6 Mixing business logic, input handling, and output formatting in one place.
• 7 Using broad error handling that hides the real failure.
• 8 Forgetting to test the behavior after refactoring.
• 9 Adding clever code that future maintainers will struggle to read.
• 10 Not checking performance on realistic input sizes.

• 1 Test boundary and empty cases.
• 2 Keep each condition focused.
• 3 Extract complex branches into named functions.
• 4 Start with clear requirements and one minimal working example.
• 5 Use meaningful names that explain business intent.
• 6 Keep examples small enough to debug line by line.
• 7 Validate input at every trust boundary.
• 8 Handle errors explicitly and preserve useful context.
• 9 Prefer simple control flow over deeply nested logic.
• 10 Separate domain logic from I/O and framework code.
• 11 Write tests for normal, boundary, and failure cases.
• 12 Review security assumptions before production use.
• 13 Measure performance before optimizing.
• 14 Document non-obvious decisions close to the code or in project notes.
• 15 Use official documentation when behavior is version-specific.
• 16 Keep dependencies current and remove unused code.
• 17 Avoid hardcoded secrets, credentials, and environment-specific paths.
• 18 Log operational events without exposing sensitive data.
• 19 Design examples so learners can safely modify and rerun them.
• 20 Prefer maintainability over short-term cleverness.

• 1 Beginner: rewrite the example with different names and values.
• 2 Intermediate: add validation and handle one expected failure case.
• 3 Advanced: place Java Programs for Practice inside a small service-style design with tests.

• 1 Build a small Java console feature that demonstrates Java Programs for Practice.
• 2 Accept input, process it with the concept, print a clear result, and handle invalid input.
• 3 Add a README note explaining the design choice and two edge cases you tested.

• 1 If the program does not compile, check spelling, imports, braces, and file/class names first.
• 2 If output is unexpected, print intermediate values and verify each branch of the logic.
• 3 If the design feels complex, reduce it to the smallest working example and add pieces back one at a time.

• 1 Practice Java Programs for Practice with a second example from a business domain such as inventory, payroll, banking, or e-commerce.
• 2 Review related Java topics that cover data flow, error handling, testing, and clean design.
• 3 Compare your solution with official documentation and simplify anything you cannot explain clearly.