Testing expert and author Colin Vipurs tells us why you should never name your test “Test1”.
Dagger aficionado Sven Ruppert demonstrates dependency injection in a simple example aimed at declaring dependencies, specifying how to satisfy them, as well as allowing you to focus on the interesting classes.
A look at the pros and cons of the big data processing framework that took the industry by storm.
We’re determined to investigate the claim that developer knowledge has a half life of approximately five years. That means in order to stay technically current, we need to adopt a lifelong learning philosophy.
How do you prepare to fully understand the impact of new code on your system? Alex Zhitnitsky takes us through the gear Java developers should have in their proverbial tool box.
For all the wonders of digital media, let’s not forget the importance of speaking in person, writes frequent conference-goer Stefan Priebsch.
Releasing software is like taking out a mortgage. You have a constant debt to keep, repaid in testing, maintenance and lines of code. If you fail to keep up payments, you can lose it all.
An easy guide through the three-step process of consuming REST services for Java applications.
FIRST_VALUE(), LAST_VALUE(), LEAD(), and LAG() – you’ll soon be asking yourself how you’ve survived SQL this long without these window functions.
What are the most common testing mistakes? How much testing is enough? And what should you name your tests? Find all the answers in this latest issue of JAX Magazine.
Imagine a builder that has never heard of windows. Now imagine the joys of a SQL programmer that discovers window functions.
Alex Zhitnitsky takes us behind the scenes of Java 9 and shows us how new features come to life.
At the EclipseCon Europe 2014, head of Eclipse Mike Milinkovich told JAX Editors Diana Kupfer and Hartmut Schlosser about the new Eclipse Cloud Initiative.
jOOQ’s Lukas Eder takes a look at the wealth of creative class names in Spring and the naming policy in Java.