fuck c and cpp fans. and java. NullPointerExceptions.

🔗 Kotlin treats null-safety as a first-class feature: types are non-nullable by default, so you catch potential `NullPointerExceptions` at compile time, without the verbosity of `Optional`. See how this works in a Spring Boot backend 👇 kotl.in/b74l38

If we properly use Spring's awesome features, we might be able to say goodbye to NullPointerExceptions -The “billion-dollar mistake” is finally getting a real fix in the Spring ecosystem Spring Boot 4 Spring Framework 7 take a huge leap toward compile-time null-safety with JSpecify. @NullMarked and @Nullable, two annotations by Spring finally giving Java developers what we’ve needed for years: - Catch NPEs at compile time (with tools like NullAway) - Cleaner, explicit APIs - Smarter IDE guidance from the first line of code - More reliable production systems

A proposed enhancement, targeted for @ApacheGroovy version 6, adds an optional compile-time null checking mechanism. 𝑪𝒂𝒕𝒄𝒉𝒊𝒏𝒈 𝑵𝒖𝒍𝒍𝑷𝒐𝒊𝒏𝒕𝒆𝒓𝑬𝒙𝒄𝒆𝒑𝒕𝒊𝒐𝒏𝒔 𝒂𝒕 𝒄𝒐𝒎𝒑𝒊𝒍𝒆 𝒕𝒊𝒎𝒆. Read more about it and provide your feedback: groovy.apache.org/blog/groov…

The jSpecify specification helps you to avoid NullPointerExceptions. You can easily configure jSpecify support in Java projects using the freshly brewed jSpecify Agent Skill ♨️ github.com/sivaprasadreddy/s…

Backend lead is wrong. It should return 400 Bad Request with detail. The server shouldn't expose exceptions to the front end. NullpointerExceptions shouldn't happen in prod.

70 % aller Fehler in Java-Produktionscode sind #NullPointerExceptions. Mit #NullAway & #JSpecify lassen sie sich statisch verhindern – ohne große Umbauten. Richard Gross zeigt, wie Teams sicher & schrittweise migrieren. Details: javapro.io/de/wie-man-den-mi… @SpringCentral @UberEng

Did You Know! 💡 The most expensive error in coding history is the "Null Reference". In 1965, computer scientist Tony Hoare introduced null into the ALGOL language. His reason? "It was just so easy to implement." He later apologized, calling it his "Billion Dollar Mistake." Why? Because NullPointerExceptions (and undefined errors) have caused countless system crashes, security vulnerabilities, and billions of dollars in lost time over the last 60 years. The Lesson: A crash happens not when code is complex, but when data is missing. • In Java: Use Optional<T> instead of returning null. • In JS: Use Optional Chaining (user?.name). Defensive coding saves weekends. 🛡️ #Java #Programming #HistoryOfTech #SoftwareEngineering #DidYouKnow

🚨 Say Goodbye to NullPointerExceptions 🚨 New video on what is jSpecify and how it helps to avoid NullPointerExceptions. youtube.com/watch?v=p3v8wJG3… 👉 How @intellijidea Dataflow analysis catch some NPE issues 👉 How IntelliJ IDEA show jSpecify Nullability issues as warnings 👉 How to configure Maven to fail the build if there are Nullability Issues 👉 How to customize IntelliJ IDEA settings to show Nullability issues as errors 👉 How jSpecify helps in Spring Boot applications #Java #SpringBoot #IntelliJIDEA

"that has NullPointerExceptions" ...and?

well it is because it did not deliver on any of it's initial promises. There is literally better solutions for any field it operates in. Jack of all trades, master of none. As I said: Who builds in the overhead of a virtual machine and garbage collector and then has NullPointerExceptions. This is so braindead I cannot even...

A bloated memory managed language that has NullPointerExceptions. The greatest fail in programming history, except for JavaScript. That's even worse.

NullPointerExceptions are still the #1 reason Java apps crash in production. Here’s a better way: catch them at compile time using #JSpecify and #NullAway in Quarkus. Simple setup, zero runtime cost. Read the full tutorial → buff.ly/GtIsnAT #Java #Quarkus

I'm never leaving this app, says @__Piyushrathore People with sticks look like students not devs & one of them is likely rowdy, says @PachhaVenkatesh As a fellow dev Those 'Java devs' are just interns stress-testing their NullPointerExceptions IRL. Python stays chill. 🐍😂🤣

yeah yeah exception handled next time try not to throw nullpointerexceptions at me

🧟‍♂️ Night of the Undying NullPointerExceptions: A Scary Story from Kodee It was a quiet October evening like any other when Alex sat down to deploy an update. But what began as a simple deployment was quickly met with blood-curdling screams from the logs... One NullPointerException thrown after another, with no end in sight. The app crashed, users vanished, and darkness consumed the server room. AAAAHHH! Luckily, @kotlin's null safety provides the counter-curse needed to fend off these NullPointerException spirits. The compiler catches them before they can ever begin haunting you in production. ☠️ NullPointer nightmares, begone!

Spring Boot 4 tip: Collections with nullable elements (List<Nullable String>) help catch NullPointerExceptions at compile-time instead of runtime. No more surprises when processing API responses that might contain null values! 🛡️ #SpringBoot #javabh

Java Interview Scenario based question: You're using @Autowired for field injection in your Spring project. It's simple and it works. @Component public class UserService { @Autowired private UserRepository userRepository; } Your team lead asks you to refactor this as field is injection often discouraged. Think of below drawbacks of field injection: →Visibility: Hides a class's required dependencies. →Testability: Makes unit testing harder, often requiring reflection. →Runtime Issues: Can lead to NullPointerExceptions if a dependency is missing. →Design: Encourages classes with too many responsibilities (violating SRP). So what's the recommended alternative? → Constructor Injection. Dependencies are passed explicitly when the object is created, making them non-negotiable requirements. @Component public class UserService { private final UserRepository userRepo; // Final! public UserService(UserRepository userRepo) { this.userRepo = userRepo; } Why is Constructor Injection better? → Explicit: Clearly defines what a class needs to function. → Guaranteed: The application won't start if a dependency is missing. → Immutable: final fields are safer and thread-friendly. → Testable: Easily mock and pass dependencies in tests. Leads to more robust and maintainable code

How do you avoid NullPointerExceptions in Java without endless if (x != null) checks? Let’s find out 👇

Calling all Java devs! Head to the Discovery Theater in one hour to catch @dashaun 's session: "Null Safety in Spring with JSpecify and NullAway." Discover how to make NullPointerExceptions a thing of the past! #SpringOne #VMwareExplore brcm.tech/45TjWvo