Ever wondered what the difference is between server-side and client-side containers? John Whiley, CTO of Moka5, explains their core functions and why you need both.
It’s never easy to know quite when you’ve finished testing. That’s why a group of researchers have developed an Eclipse plug-in that evaluates your testing habits.
Apache Hadoop, Apache Spark, Akka, Java 8 streams and Quasar: A look at the classic use cases to the newest concurrency approaches for Java developers.
Atlassian talks about DevOps, gifs, corporate communication and the latest HipChat innovation: HipChat server, which allows companies to use their chat tool behind a firewall.
Many commentators are weighing in on Pivotal’s recent decision to withdraw support for Groovy, and a number of open source advocates have come out in defence of the JVM language. Lukas Eder argues it was “doomed to fail”.
NASA has produced its own set of coding standards to ensure code quality and safety among all NASA applications. These standards have evolved from their own guidelines and are set to be applicable to the greater software development industry.
In this new series of articles on testing, Daniel Witkowski identifies common mistakes made during performance testing and demonstrates how to use widely available free open source tools to find response time problems before they reach production.
Ask any programmer and they’ll be able to tell you what time of the day (or night) they’re most productive. As tech employers grow more and more tolerant to alternative work routines, studies are showing that ‘night owl’ developers are often like nocturnal predators.
Does open source need to be profitable? Lukas Eder weighs in on the open source funding debate, following Pivotal’s surprise decision to cut support for Groovy and Grails.
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.