Painlessly Migrating to Java Jigsaw Modules - a Case Study
https://www.infoq.com/articles/Java-Jigsaw-Migration-Guide
https://www.infoq.com/articles/Java-Jigsaw-Migration-Guide
InfoQ
Painlessly Migrating to Java Jigsaw Modules - a Case Study
This article is a case study of changes required in an application to make use of the new Java Platform Module System. An understanding of the module system will become an important skill for Java developers, using Java 9 and beyond.
Basic Spring web application in Java, Kotlin and Scala - comparison ·
https://rskupnik.github.io/basic-spring-webapp-java-kotlin-scala
https://rskupnik.github.io/basic-spring-webapp-java-kotlin-scala
rskupnik.github.io
Basic Spring web application in Java, Kotlin and Scala - comparison ·
I’ve been wondering how hard would it be to implement a basic Spring Boot app in alternative JVM languages, such as S...
A Curious Java Language Feature and How it Produced a Subtle Bug – Java, SQL and jOOQ.
https://blog.jooq.org/2017/07/20/a-curious-java-language-feature-and-how-it-produced-a-subtle-bug/
https://blog.jooq.org/2017/07/20/a-curious-java-language-feature-and-how-it-produced-a-subtle-bug/
Java, SQL and jOOQ.
A Curious Java Language Feature and How it Produced a Subtle Bug
Java’s visibility rules are tricky at times. Do you know what this will print? package p; import static p.A.x; class A { static String x = "A.x"; } class B { String x = "B.x&qu…
Entities or DTOs - When should you use which projection? - Thoughts on Java
https://www.thoughts-on-java.org/entities-dtos-use-projection/
https://www.thoughts-on-java.org/entities-dtos-use-projection/
Thorben Janssen
Entities or DTOs - When should you use which projection? - Thorben Janssen
JPA and Hibernate allow you to use DTOs and entities as projections in your JPQL and Criteria queries. When I talk about Hibernate performance in my online training or at a workshop, I get often asked, if it matters which projection you use. The answer is:…
Richard Clayton - Speaking Intelligently about "Java vs Node" Performance
https://rclayton.silvrback.com/speaking-intelligently-about-java-vs-node-performance
https://rclayton.silvrback.com/speaking-intelligently-about-java-vs-node-performance
Silvrback
Richard Clayton - Speaking Intelligently about "Java vs Node" Performance
Speaking Intelligently about "Java vs Node" Performance - Please understand what's really important when it comes to the benefits of a platform.
Code Smells: Null | IntelliJ IDEA Blog
https://blog.jetbrains.com/idea/2017/08/code-smells-null/
https://blog.jetbrains.com/idea/2017/08/code-smells-null/
Node.js 8.3.0 is now available shipping with the Ignition + TurboFan execution pipeline
https://medium.com/the-node-js-collection/node-js-8-3-0-is-now-available-shipping-with-the-ignition-turbofan-execution-pipeline-aa5875ad3367
https://medium.com/the-node-js-collection/node-js-8-3-0-is-now-available-shipping-with-the-ignition-turbofan-execution-pipeline-aa5875ad3367
Medium
Node.js 8.3.0 is now available shipping with the Ignition + TurboFan execution pipeline
This post is brought to you by Myles Borins who is a @nodejs ctc member / developer advocate for Google Cloud.
NoBlogDefFound: flatMap() vs. concatMap() vs. concatMapEager() - RxJava FAQ
http://www.nurkiewicz.com/2017/08/flatmap-vs-concatmap-vs-concatmapeager.html?m=1
http://www.nurkiewicz.com/2017/08/flatmap-vs-concatmap-vs-concatmapeager.html?m=1
Nurkiewicz
flatMap() vs. concatMap() vs. concatMapEager() - RxJava FAQ
Frozen Stawy Cietrzewia There are three, seamlessly similar operators in RxJava 2.x: flatMap() , concatMap() and concatMapEager() . All...
From: Lean Enterprise - Jez Humble
Enormous initiatives, with roadmaps of months or even years, constantly pop up for these types of projects, with lip service paid to working incrementally to solve a real (internal) customer problem. In fact, teams building these systems are often dismissive of their customers’ needs and preferences — we often hear statements such as “we know what they need better than them.”
Projects run in this way, without regularly delivering incremental value to their customers in order to get feedback, are an appalling waste of time and resources and rarely achieve their intent, outcome, or objectives. But there are other serious negative consequences: internal systems that are painful to use make employees frustrated, impact morale and their ability to do their work effectively.
Enormous initiatives, with roadmaps of months or even years, constantly pop up for these types of projects, with lip service paid to working incrementally to solve a real (internal) customer problem. In fact, teams building these systems are often dismissive of their customers’ needs and preferences — we often hear statements such as “we know what they need better than them.”
Projects run in this way, without regularly delivering incremental value to their customers in order to get feedback, are an appalling waste of time and resources and rarely achieve their intent, outcome, or objectives. But there are other serious negative consequences: internal systems that are painful to use make employees frustrated, impact morale and their ability to do their work effectively.
