#refactorings — Public Fediverse posts

And btw, I am decidedly NOT a fan of Lombok. While Records are not a replacement for what Lombok does, the way Lombok is designed can cause problems, especially when doing automated #Refactorings.

For DTOs, I let IntelliJ IDEA (or Cody @sourcegraphcody) do the grunt work of generating getter/setters as necessary.

In fact, you might not need getter/setters at all, if they're DTOs, maybe it's OK to make the fields public? (Obviously check for compatibility with your framework.)

I’ll be part of the #Bucharest #Techweek in Romania as part of their #Java summit https://www.techweek.ro/java-summit and I’ll discuss an old topic: #database #refactorings and #migrations and why these things make a lot of sense for a #Graph database like #neo4j that is not so schemaless like you would think.