RT @ceilfors: Many of the software engineers I talked to told me that they practice TDD out of guilt. That's not right, we need a differen….

RT @relizarov: I'm happy to see one more language adopting structured concurrency. Interesting design tradeoff, though. In Kotlin it is pur….

RT @tjaskula: No matter paradigm, to be successful hide the “how” and make “what” explicit. But each paradigm has it’s own ways to do it.

RT @kubukoz: Still hiring. Let me know if you're interested!

PSA: I'm happy to announce that, in a week, I'm changing jobs. After 7 years at LangMedia, I'm joining @OcadoTechnology as a #Java Software Engineer 😀. CC:.> @tdubikowski (my manager 👨‍💼).> @kubukoz, @meldmy, @_lsikora_ (people I follow who also work at Ocado in other teams 👋).

RT @aalmiray: Are you a long time Apache Maven user but have to deal with Gradle? Do you find Gradle to be confusing, irritating, or diffic….

RT @mariofusco: You can optimise for low latency. You can optimise for high throughput. You can optimise for memory occupation. However 90….

RT @OcadoTechnology: What can software developers learn from board game development? Maybe they aren't such different skills! https://t.co/….

RT @zsmb13: Here's a not-really-technical post for a change, where I ramble about imposter syndrome. Getting Only Positive Feedback.https:….

RT @konradkokosa: People quite often ask me how long it took me to write book and whether it was worth it. As almos….

That rich dependency management model looks very promising! 😍. I haven't used any of these features so far, but now that they're a cornerstone of Gradle, I'll definitely want to give them a try 😊.

RT @gradle: 📣 Gradle 6.0 is here! 🎉. Lots of great things:.📚 Substantial improvements in dependency management….

RT @OliverLibutzki: Being in 2019: Which part of #DomainDrivenDesign is more important and relevant? . You can use the comments to reason y….

RT @jodastephen: [blog] Java switch: 4 wrongs don't make a right! Sorry folks, but I don't like the extensions to switch in Java: https://t….

Summary cont'd (#JPMS module name = #Maven artifact ID = root package name). Pros:.5) root package names explicit through JAR names & directory names.

Thx @pucelius for pointing out con no. 4 👍.

Summary cont'd (#JPMS module name = #Maven artifact ID). Pros:.3) module names in JAR file names.4) module names in directory structure. Cons:.3) duplication (group ID = a prefix of artifact ID).4) JAR file & module directory names with dots (non-standard, cf. #Maven conventions).

Conclusions (#JPMS module name = #Maven artifact ID). For me, the pros outweighed the cons. I had to get used to long artifact IDs. Yet, I don't need to wonder which ID to use in which context (as there's only ever one)!. To sum up, I recommend @sormuras' convention! 👍. 4/4.

Summary (#JPMS module name = #Maven artifact ID). Pros:.1) module names finally become FIRST-CLASS citizens 🚀.2) for every project, there's only a SINGLE identifier across all source files 🔍. Cons:.1) long artifact IDs.2) same prefix in artifact IDs (only suffixes differ). 3/4.