The 145th airhacks.tv is out 📺 This time we covered a lot of ground - from a 1992 pattern that LLMs understand better than most developers, to running agents locally on Apple Metal. Here are the highlights: **BCE is older than Java** Ivar Jacobson coined Boundary-Control-Entity in 1992. Three packages. Clear responsibilities. No magic. And because it's been in books and specs for decades, LLMs generate BCE-structured code remarkably well. Standards age better than frameworks. **@Transactional belongs on the Boundary. Period.** One use case, one transaction. Moving @Transactional down to the Control layer is how you end up with inconsistent data and debugging sessions you didn't plan for. **Agent Smith: a zero-dependency Java 25 agent framework.** ~130KB JAR. We did a live demo: a transcriber agent with multi-agent delegation, episodic memory, and tool permissions. I currently run 20-30 agents for my own business processes. Just Java SE. **GPU Llama + TornadoVM - local LLM execution on Apple Metal.** The goal: run Agent Smith without any cloud dependency. We're getting close. **The Z ecosystem keeps growing.** ZUnit - a single-file test runner in ~300 lines. ZB - a build tool. ZDate, ZJDocFind. All zero-dependency, all Java 25. Small tools that do one thing well. **A community member from France built a zero-dependency MCP server** using BCE principles. This is exactly what happens when you keep things simple - people can actually build on top of it. **LLMs understand standards better than frameworks.** This keeps coming up. The leaner your stack, the better AI-assisted development works. Fewer dependencies = fewer hallucinations. And: upcoming airhacks Live workshops on spec-driven Java development and building front-ends without dependencies. Watch the full episode here: https://lnkd.in/d8he8iTf #java #airhacks #zerodependency #agentsmith #bce #java25 #ai #llm #softwarearchitecture

Weekend learning mode: ON. 🎧💻 I’ve spent the last two days heavily focused on advancing my backend architecture skills with Java. Moving into enterprise development means understanding the tools, but also mastering the web fundamentals that hold it all together. Here’s what I’ve been tackling: 🌐 Web Basics: Solidifying the foundations—HTTP/HTTPS lifecycle, REST API design principles, and configuring CORS securely. ⚙️ Spring Core: Getting hands-on with Dependency Injection (IoC) and understanding how the container handles Bean scopes and lifecycles. 🛡️ Spring AOP: Learning how to cleanly modularize cross-cutting concerns (like logging and security) without cluttering up the core business logic. Transitioning to Java has been challenging, but realizing how powerful these frameworks are for building scalable systems makes it completely worth it. What is one topic you think every backend developer needs to master early on? Let me know! #Java #Backend #API #SpringFramework #DeveloperJourney #LearnInPublic

After one month in the Web Development + AI Bootcamp at @TuwaiqAcademy, we moved from Java basics into Spring Boot — and one thing became clear: Validation is not optional. It’s fundamental. At first, I was writing manual checks like: if(name.isEmpty()) { ... } That works… but it doesn’t scale and quickly turns messy. Now using annotation-based validation in Spring Boot: - @NotNull - @Size(max = 100) - @Min / @Max The difference is obvious: Cleaner code, better structure, and proper separation of concerns. Instead of mixing validation with business logic, everything becomes more maintainable. Next step: Handling validation errors properly and returning meaningful API responses instead of generic 400 errors. This is where backend development starts to feel real. #TuwaiqAcademy #Java #SpringBoot #BackendDevelopment #SoftwareEngineering

🚀 Exciting Update: Solving the Latest Spring Boot Bugs with Scenario-Based AI Contexts! If you are building AI-driven applications in Java, managing runtime contexts effectively is crucial. I’ve just pushed a significant update to my open-source project: Scenario-Based Runtime Context for AI. In our latest update, I’ve added detailed descriptions and concrete evidence demonstrating how this framework successfully resolves some tricky bugs encountered in the latest Spring Boot releases. 🐛🔨 By utilizing a scenario-based approach, we can handle dynamic AI runtime contexts much more smoothly without clashing with Spring Boot's latest lifecycle or dependency injection changes. Curious to see how it works? Check out the updated repository and the new use cases here: 🔗 https://lnkd.in/gUnnVG5y I'd love to hear your thoughts! If you find it helpful, a ⭐️ on GitHub is always appreciated. Feedback and PRs are welcome! #SpringBoot #Java #AI #OpenSource #GitHub #SoftwareEngineering #DeveloperTools

Day 1/60 – Backend Development Journey (Java OOP Foundations) Today I worked on implementing two core OOP concepts: Encapsulation and Inheritance. Instead of just learning theory, I built a small user system with different roles. What I built: - A base User class with private attributes - Two derived classes: - Admin (with admin-level access) - Customer (with wallet functionality) Key Concepts Applied 1. Encapsulation I restricted direct access to variables using private fields and controlled them through getters and setters. 2. Inheritance Created Admin and Customer classes extending User to reuse common properties. GitHub repo: https://lnkd.in/gYQVDmnk #Java #Backend #OOP #ChatGPT

Most developers call APIs every day but very few understand what actually happens behind the scenes Swipe through this This is how I started looking at backend systems more clearly In the beginning it felt simple request goes in response comes out but there is a lot happening in between how requests are routed how controllers handle them how services process logic how databases are queried and how responses are built and sent back Once I understood this flow debugging became easier design decisions started making more sense The more I learn the more I realise backend is not just endpoints it is a complete flow Still learning and improving What part of request flow feels confusing to you #Java #SpringBoot #BackendDevelopment #SystemDesign #SoftwareEngineering

🚨 90% of developers use HTTP methods incorrectly… If you work on APIs or backend, these basics MUST be clear 👇 GET = fetch data POST = create data PUT = full update PATCH = partial update DELETE = remove data ⚡ Sounds simple… but these mistakes are what create bugs. 💬 Comment “API” if this is clear 🔔 Follow @DevelopersStreet for daily dev content 🌐 www.developersstreet.com 📞 +91 94128 92908 #HTTP #API #RESTAPI #WebDevelopment #Coding #Programming #DeveloperLife #BackendDeveloper #FrontendDeveloper #FullStackDeveloper #LearnToCode #CodingTips #DevTips #SoftwareDevelopment #TechCommunity #LinkedInLearning

Day 103 - LeetCode Journey Solved LeetCode 232: Implement Queue using Stacks ✅ Classic problem where you reverse the thinking. Queue is FIFO, but stacks are LIFO… So the trick is to use two stacks to simulate queue behavior. Approach used: Push → reverse elements using second stack Pop/Peek → operate directly from main stack Key learnings: • Understanding stack vs queue behavior • Using two stacks to reverse order • Designing data structures from scratch • Thinking in terms of operations, not just code ✅ All test cases passed ⚡ Efficient and clean implementation This is one of those problems that builds strong fundamentals 💪 #LeetCode #DSA #Stack #Queue #Java #CodingJourney #ProblemSolving #InterviewPrep

🚨 Today wasn’t about solving problems… it was about fixing what was broken. Day 37 of my Backend Developer Journey — and honestly, 👉 this felt more like a real developer day 🧠 LeetCode Breakthrough Solved today’s Daily Challenge using Median + Math Optimization 💡 What clicked: → Flatten the grid into a single array → Check if all elements follow same modulo → Use median to minimize operations ⚡ The Real Trick 👉 If modulo condition fails → impossible ❌ 👉 If valid → median gives minimum operations ✅ 🔍 Key Insight 👉 Median minimizes absolute differences 👉 Math-based optimization beats brute force 🔗 My Submission: https://lnkd.in/gf43YBkq ☕ Spring Boot Learning 🐛 Debugging Day (Real Dev Life) Today was not smooth… and that’s okay 👇 👉 Faced issues with Lombok + Java 24 👉 Switched back to Java 21 👉 Bugs reduced, but still debugging ⚡ What I learned 👉 New versions ≠ always stable 👉 Compatibility matters more than hype 👉 Debugging is a core developer skill 🔌 Database Progress 👉 Successfully connected PostgreSQL to my server 👉 Backend is now interacting with real data 🧠 The Shift 👉 Not every day is productive — but every day teaches 👉 Debugging builds deeper understanding than coding 👉 Real growth happens when things don’t work 🔗 GitHub Repo (Lovable Clone): https://lnkd.in/gwHmAZaK 📈 Day 37 Progress: ✅ Learned median optimization technique ✅ Handled real-world debugging issues ✅ Connected DB to backend successfully 💬 What’s one bug that taught you more than any tutorial? 👇 #100DaysOfCode #BackendDevelopment #SpringBoot #Java #LeetCode #Debugging #CodingJourney

Yesterday: “It’s working perfectly 😌” Today: Application failed to start. Same code. Same logic. Different story. Welcome to Spring Boot reality 👇 → One missing bean = full system collapse → One wrong config = hours gone → One hidden null = chaos unleashed → One DB hiccup = everything breaks And suddenly… you’re not coding anymore, you’re investigating. Logs become clues. Stack traces become stories. Debugging isn’t pain — it’s where real backend thinking begins. Because great developers don’t fear crashes… they understand them. ⚡ #SpringBoot #Java #BackendDevelopment #Debugging #BuildInPublic