Luke Lee

🚀 Spring 4.0.1 Released! On the 18th, Spring 4.0.1 was officially released. This update brings important fixes and incremental improvements that help keep Spring applications stable, secure, and easier to maintain. If you’re working with Spring-based systems, it’s worth taking a look at the release notes and planning your upgrade. Small updates can make a big difference in production reliability. #Java #SpringFramework #SoftwareDevelopment #Backend #TechUpdates https://lnkd.in/eg4TSMcq

24

1 Comment

Ever debugged TypeScript code and found line numbers don't match your source? 🤔 This happens because traditional TypeScript compilers transform syntax like enums and parameter properties into JavaScript equivalents, shifting line numbers and making debugging frustrating. The solution is here! TypeScript's new erasable syntax feature lets you write cleaner code that compiles directly to native JavaScript without line shifts. → Use the --erasableSyntaxOnly flag in TS 5.8+ → Your enums and parameter properties compile cleanly → Debug with accurate line numbers → Better developer experience What's your biggest debugging pain point with TypeScript? #TypeScript #TypeScript2026 #DeveloperTools #Debugging #JavaScript

3

Spring Boot developers use @Autowired everywhere. Senior developers stopped using it years ago. Here's why - and what to use instead. 🔴 THE PROBLEM WITH FIELD INJECTION @Service public class PaymentService { @Autowired private PaymentRepository repo; // ❌ field injection @Autowired private FraudService fraudService; } ❌ You cannot write a unit test without starting Spring context ❌ Dependencies are invisible - no way to see them from the constructor ❌ Allows circular dependencies to compile - blow up at runtime ❌ final fields not possible - object state can change after construction ❌ Spring owns your class. Not you. ✅ CONSTRUCTOR INJECTION - THE RIGHT WAY @Service public class PaymentService { private final PaymentRepository repo; private final FraudService fraudService; public PaymentService(PaymentRepository repo, FraudService fraudService) { this.repo = repo; this.fraudService = fraudService; } } ✅ Dependencies explicit - visible at a glance ✅ final fields - immutable after construction ✅ Unit testable without Spring context: new PaymentService(mockRepo, mockFraud); // done ✅ Circular dependency? Fails at startup - not in production ✅ Works without @Autowired - Spring auto-detects single constructor 💡 With Lombok - zero boilerplate: @Service @RequiredArgsConstructor // generates constructor for all final fields public class PaymentService { private final PaymentRepository repo; private final FraudService fraudService; } 🔴 WHEN SETTER INJECTION MAKES SENSE Optional dependencies that can change after construction. Almost never in BFSI & Telecom production code. If you're using setter injection - ask why that dependency is optional. 💡 The rule: Field injection = Spring owns your object. Constructor injection = you own your object. In 10 years of BFSI & Telecom Java codebases - every class I've seen with 5+ @Autowired fields was a class doing too many things. Constructor injection makes that visible. Field injection hides it. 📌 If you can't construct it in a test - you can't trust it in production. 💬 Is your team still using field injection? What's stopping the switch? 👇 #Java #SpringBoot #CleanCode #BackendEngineering #BFSI #Telecom #JavaDeveloper #SeniorDeveloper #SoftwareEngineering #TDD

10

3 Comments