It's finally happening: the screws will be tightened on illegal access to JDK internals through openjdk.java.net/jeps/396. Something we warned about already in 2017 in the @javamodularity book.
“The cost of modularity is explicit complexity” — @mfeathers in @oredev keynote.
Nicely put, though I’d replace cost with benefit. Implicit dependencies are ticking timebombs in code. Whether through #microservices or other modular approaches (cf. @javamodularity), surface them!
So that’s how @__N_M_E surprised me this evening with a gift out of the blues. A signed copy of @javamodularity book 😱🙌🏻🙌🏻
Finally a solid incentive to delve into Java 9 that I have been shying away from all this while 🤦♂️🤦♂️
My new post: 5 Refactoring Principles by Example (➡️@javamodularity plugin)
1. Hide "how" with "what" (➡️#CleanCode)
2. Aim for consistency (➡️@TheDonRaab's symmetry)
3. Avoid deep nesting
4. Separate concerns (= SRP)
5. Avoid duplication wisely (= DRY)
blog.tlinkowski.pl/2019/5-re…
Thanks @devoxx for attending Java Modularity: the Year After! You can find the slides here slideshare.net/SanderMak/jav…
Don't forget to swing by the @OReillyUK booth at 13:30 to get a signed copy of the @javamodularity book. There's a limited number, first come, first serve.
Great start to @devoxx with @mreinhold explaining the state of the #java platform: modularization, trimming down & increasing the pace of innovation.
When migrating to JDK 11 and later, the @javamodularity book provides invaluable help & context: javamodularity.com#devoxx
Come and join me for 'Java Modularity: the Year After' at 12:30 in room 2018. There will even be some free @javamodularity books for a few lucky attendees! #CodeOne
For the second year in a row our @javamodularity book is mentioned in the keynote. With #jdk11 just released the book is now more relevant than ever. javamodularity.com