User Input using Scanner

import java.util.Scanner;
Scanner sc = new Scanner(System.in);

import java.util.Scanner;

public class Main {

  public static void main(String[] args) {

    Scanner sc = new Scanner(System.in);

    System.out.print("Enter your name: ");
    String name = sc.nextLine();

    System.out.print("Enter your age: ");
    int age = sc.nextInt();

    System.out.print("Enter your salary: ");
    double salary = sc.nextDouble();

    System.out.println("Name: " + name);
    System.out.println("Age: " + age);
    System.out.println("Salary: " + salary);

    sc.close();

  }
}

• 1 Scanner is a class in java.util package.
• 2 Used to read input from user.
• 3 Works with System.in input stream.
• 4 Supports multiple data types.

• 1 nextLine() → reads string input.
• 2 nextInt() → reads integer input.
• 3 nextDouble() → reads decimal input.
• 4 nextBoolean() → reads true/false.

• 1 Scanner reads input from keyboard.
• 2 Stores input in variables.
• 3 Processes data during runtime.
• 4 Closes connection after use.

• 1 Used for interactive programs.
• 2 Allows dynamic input from users.
• 3 Essential for real-world applications.
• 4 Makes programs user-friendly.

• 1 Used in login and registration forms.
• 2 Used in console-based applications.
• 3 Used in banking and billing systems.
• 4 Used in student management systems.
• 5 SaaS products use User Input Using Scanner in Java in services, dashboards, background jobs, and API workflows.
• 6 ERP and banking systems apply User Input Using Scanner in Java with validation, logging, review, and rollback plans.
• 7 E-commerce and healthcare platforms use User Input Using Scanner in Java carefully because reliability and data correctness matter.

• 1 A Java program first evaluates the surrounding context, then applies the User Input Using Scanner in Java 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 Not importing Scanner class.
• 2 Forgetting to close Scanner object.
• 3 Mixing nextLine() with nextInt() incorrectly.
• 4 Using wrong input method for data type.
• 5 Skipping the small working example before adding framework code.
• 6 Ignoring null, empty, duplicate, and boundary inputs.
• 7 Mixing business logic, input handling, and output formatting in one place.
• 8 Using broad error handling that hides the real failure.
• 9 Forgetting to test the behavior after refactoring.
• 10 Adding clever code that future maintainers will struggle to read.

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

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

• 1 Build a small Java console feature that demonstrates User Input Using Scanner in Java.
• 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 User Input Using Scanner in Java 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.