Mark Paluch πŸ‘¨β€πŸ’»,🎹&✈️

Mark Paluch πŸ‘¨β€πŸ’»,🎹&✈️

@mp911.de

Musician, producer, Spring Data, Database drivers. #Autist | #ADHD | INTJ-T | #Neurodiversity 🧠🌈 Ostfriesland 🌊🌬️🌞🌧️ https://paluch.biz/about-me/ | https://soundcloud.com/rflktd

965 followers211 following544 posts

Mark Paluch πŸ‘¨β€πŸ’»,🎹&✈️ reposted

Using Spring Modulith? There is a new validation that spots the classic Async + Transactional + TransactionalEventListener combination and includes a quick fix that turns it into a single ApplicationModuleListener annotation - less boilerplate, same behavior πŸ₯³ πŸš€

Mark Paluch πŸ‘¨β€πŸ’»,🎹&✈️ reposted

Mark Paluch πŸ‘¨β€πŸ’»,🎹&✈️ reposted

Hey Spring fam πŸƒ My early access book "Testing Spring Boot Applications" with @manning.com is Deal of The Day. Get 45% off the book, and a selection of other testing books, here: hubs.la/Q03-d27Y0 First 4 chapters online, the 5th is coming out soon, and putting finishing touches to chapter 6.

Mark Paluch πŸ‘¨β€πŸ’»,🎹&✈️ reposted

πŸš€ Datasource Micrometer v2.3.0 and v1.5.0 are out! Highlights: β€’ Customize when DataSource beans are instrumented β€’ Cache JdbcConnectionInfo per DataSource Release notes: github.com/jdbc-observa... #SpringBoot #Micrometer #Observability #JDBC

github.comv1.5 and v2.3 Release NotesMicrometer Observation API instrumentation and Spring Boot 3/4 Auto-Configuration for JDBC APIs - jdbc-observations/datasource-micrometer

Fable tried to convince me of broken hardware after a change insisting the problem is somewhere else. Sol follows a specification and creates more problems than functionality while all tests are green. Reminds me of assertTrue(true) and testing getters and setters to pretend test coverage.

I am convinced that AI will not take away developer jobs. Instead, it will require even more developers to clean up the mess.

Mark Paluch πŸ‘¨β€πŸ’»,🎹&✈️ reposted

Did you know? Spring Boot 4.1 brings Spring Data 4.1's type-safe property paths enabling devs to use method references instead of strings in data access code: Sort.by("lastname") ➑️ Sort.by(Person::getLastName)

The more AI I use for writing code, the more I come to the conclusion that this is doing the wrong thing faster. AI Coding for prototyping, learning, reviewing is great. For everything else, it leaves developers with complex indirections, hand-rolled duplications and an unmaintainable blob.

Mark Paluch πŸ‘¨β€πŸ’»,🎹&✈️ reposted