Java Right Shift Operator Precedence and Evaluation

This confused me when I started working with exceptions public void test() throws Exception { throw new Exception("Error"); } Now see this: public static void main(String[] args) { test(); ❌ } 👉 This won’t compile! 💥 Error: Unhandled exception: Exception 👉 Why? Because test() is throwing a checked exception So Java forces you to handle it. ✅ Option 1: try { test(); } catch (Exception e) { e.printStackTrace(); } ✅ Option 2: public static void main(String[] args) throws Exception { test(); } 💡 Lesson: Checked exceptions must be handled either where they occur or where they are called. Did this confuse you earlier? 👇 #Java #CoreJava #ExceptionHandling #Programming #BackendDeveloper #Coding

Checked vs Unchecked Exceptions - Know the Difference ⚠️ 🔹 Checked Exceptions ▸ Checked at compile time ▸ Must be handled (try-catch or throws) ▸ Not handled → code won’t compile ▸ Examples: IOException, SQLException, FileNotFoundException 🔹 Unchecked Exceptions ▸ Occur at runtime ▸ No need to handle (but recommended) ▸ Extend RuntimeException ▸ Examples: NullPointerException, ArrayIndexOutOfBoundsException 💡 Simple Way to Remember → Checked = Compiler forces handling → Unchecked = Runtime errors 🚀 Best Practice ▸ Use Checked → for recoverable scenarios (e.g., file not found → retry) ▸ Use Unchecked → for programming bugs (e.g., null → fix the code) #Java #SpringBoot #ExceptionHandling #JavaDeveloper #BackendDeveloper

Hi everyone, happy weekend 🤗 Today I want to discuss Constructor Injection in Spring  Framework. 👉 Constructor injection is a way in Spring where all required properties are provided at the time the object is created. This ensures the object is fully initialized and ready to use immediately. 👉 We mainly use this when properties are mandatory for the class to function and when we want complete initialization at the time of object creation. 👉 The main benefits of this are: ✔ Ensures all required values are available from the start ✔ Avoids null values and incomplete objects ✔ Improves code safety and reliability ✔ Makes testing easier ✔ Supports immutability (with final fields) #SpringBoot #Java #BackendDevelopment #WeekendLearning

Still confused about how Java actually runs your code? 🤔 Here’s a simple breakdown of how the JVM works 👇 👉 1. Build Phase ✔️ Java code (.java) is compiled using javac ✔️ Converted into bytecode (.class files) 👉 2. Class Loading ✔️ JVM loads classes using: Bootstrap Class Loader Platform Class Loader System Class Loader 👉 3. Linking ✔️ Verify → Prepare → Resolve ✔️ Ensures code is safe and ready to run 👉 4. Initialization ✔️ Static variables & blocks are initialized 👉 5. Runtime Data Areas ✔️ Method Area & Heap (shared) ✔️ Stack, PC Register, Native Stack (per thread) 👉 6. Execution Engine ✔️ Interpreter executes bytecode line by line ✔️ JIT Compiler converts hot code into machine code for speed 👉 7. Native Interface (JNI) ✔️ Interacts with native libraries when needed 💡 JVM is the reason behind Java’s “Write Once, Run Anywhere” power. 📌 Save this post 🔁 Repost to help others 👨💻 Follow Abhishek Sharma for more such content #Java #JVM #SystemDesign #BackendDevelopment #SoftwareEngineer #Developers #TechJobs #Programming #LearnJava

Day 89 - LeetCode Journey Solved LeetCode 1290: Convert Binary Number in a Linked List to Integer in Java ✅ A simple yet insightful problem combining linked lists + binary concepts. Instead of storing values, I directly built the number while traversing the list. At each step, I multiplied the current result by 2 and added the current node’s value. This mimics how binary numbers are converted to decimal. Clean logic, no extra space, and efficient traversal. Key takeaways: • Combining binary logic with linked list traversal • Building result on the go without extra storage • Strengthening fundamentals of number systems • Writing simple and efficient code ✅ All test cases passed ⚡ O(n) time and O(1) space Sometimes the simplest problems reinforce the strongest concepts 💯 #LeetCode #DSA #Java #LinkedList #Binary #ProblemSolving #CodingJourney #InterviewPrep #Consistency #100DaysOfCode

Day-4 Spring Without XML. Today I explored how Spring works completely using annotations (no XML). - Started container using AnnotationConfigApplicationContext -Used @Configuration, @ComponentScan, @PropertySource -Created beans with @Component -Injected values using @Value -Managed dependencies using @Autowired ➡️ Final result: Fully initialized object with zero manual wiring. Clean. Simple. Powerful. git - https://lnkd.in/gwbUxRiK Frontlines EduTech (FLM) #SpringFramework #Java #BackendDevelopment #LearningInPublic #100DaysOfCode

While working on backend systems, I revisited some features from Java 17… and honestly, they make code much cleaner. One feature I find really useful is Records. 👉 Earlier: We used to write a lot of boilerplate just to create a simple data class. Getters Constructors toString(), equals(), hashCode() ✅ With Java 17 — Records: You can define a data class in one line: public record User(String name, int age) {} That’s it. Java automatically provides: ✔️ Constructor ✔️ Getters ✔️ equals() & hashCode() ✔️ toString() 💡 Practical usage: User user = new User("Dipesh", 25); System.out.println(user.name()); // Dipesh System.out.println(user.age()); // 25 🧠 Where this helps: DTOs in APIs Response objects Immutable data models What I like most is how it reduces boilerplate and keeps the code focused. Would love to know — are you using records in your projects? #Java #Java17 #Backend #SoftwareEngineering #Programming #Microservices #LearningInPublic

“No implementation. Still powerful.” Sounds weird? A thing that does nothing… yet controls everything. 👉 That’s a Java Interface. Think of it like this: An interface is a contract. It doesn’t tell how to do something. It tells what must be done. And once you agree to that contract… 'You must follow it.' What makes Interface special? You cannot create objects of an interface It contains: Variables → public static final Methods → public abstract (by default) A class uses implements → to accept the contract What happens when a class implements an interface? No shortcuts. If a class signs the contract: 👉 It MUST implement all methods 👉 Otherwise → it becomes abstract 🧠 The real power (most people miss this) One class → can implement multiple interfaces That means: ✔ Multiple behaviors ✔ Flexible design ✔ Loose coupling This is something classes alone can’t achieve. 🔥 Real-world thinking Interface = Rules Class = Player Rules don’t play the game… but without rules, the game collapses. Final Insight- Abstract class gives partial abstraction Interface gives pure abstraction 👉 If abstraction is hiding complexity then interface is designing clarity #Java #OOP #Interface #Abstraction #JavaProgramming #SoftwareDesign #CodingJourney #DeveloperMindset #LearnJava #TechSkills

I was debugging a backend issue recently in a Java service. At first nothing looked wrong. No errors, no obvious problems. But something was off. After checking a bit more, it turned out to be a small mismatch between the data model and the repository. The code worked fine in most cases, but not with certain data. Fixing it was simple. Finding it was not. Sometimes the problem is not complex. It’s just hidden in small details. #Java #BackendEngineering #Debugging #SpringBoot

🚀 **Day 5/30 – LeetCode Java Challenge** Today’s problem was a step up — not in complexity, but in **how carefully the logic had to be applied**. Worked on constructing a valid string based on given conditions. The tricky part wasn’t writing code — it was **handling overlaps and conflicts correctly** without breaking earlier decisions. 📊 **Result:** ✔️ Accepted (739/739 test cases) ⚡ Runtime: 11 ms (Beats 77.08%) 💾 Memory: Moderate efficiency 💡 **What actually mattered today:** * Greedy thinking can fail if you don’t track constraints properly * Managing “state” (like locked positions) is critical in construction problems * Edge cases are where most solutions break — not the main logic Let’s be honest: This isn’t an optimal solution yet. There’s still room to improve both performance and clarity. But the bigger win is understanding **why conflicts happen and how to control them**. Day 5 done. Less guesswork, more control over logic. Archana J E Bavani k Hari priya B Deepika Kannan Divya Suresh Devipriya R Bhavya B Harini B Kezia H Vaishnavi Janaki #LeetCode #Java #DSA #ProblemSolving #Consistency #30DaysOfCode