We're halfway through 2016 and gender gap in the tech field remains to be an issue. But how much has improved? Realistically, we're a long way from achieving equality but that doesn't mean solutions do not exist.
In this tutorial we will discuss about the introduction to Apache Flink, What is Flink, Why and where to use Flink. This Flink tutorial will answer the question why Apache Flink is called 4G of Big Data? The tutorial also briefs about Flink APIs and features.
This article is a unification of my blog posts reviewing the possibility of creating fat JARs (Java Archive file) in Java without using any additional plugin, IDE, or any other tool — just pure command line and Java.
In the world of build tools (Ant, Maven, or Gradle) it might not even seem useful to think about the command line. The most famous IDEs (IntelliJ, Eclipse, or NetBeans) offer building tools and implementation immediately. But let's say you only have the command line and no Internet access.
To begin, I’d like to highlight what a copy in Java is. First, let’s differentiate between a reference copy and an object copy. A reference copy, as the name implies, creates a copy of a reference variable pointing to an object. If we have a Car object, with a myCar variable pointing to it and we make a reference copy, we will now have two myCar variables, but still one object.
A while back, I got the oppurtunity to work with the Cognos SDK and Java. After some exercises, I was able to write some modular code for my project. IBM Cognos SDK has plenty of examples of interacting with the Cognos environment and executing the report, but here, I am providing some better modular code to execute the Cognos report and save the XLS format to your machine.
Using instanceof is a code smell. I think we may agree on that. Whenever I see a construction like that, I’m sure that something went awry. Maybe someone just didn’t notice a problem when making a change? Maybe there was an idea, but it was so complex that it required so much effort or time that a developer made a decision not to do it? Maybe it was just laziness? Who knows. The fact remains that the code evolved into such state and we have to work with it.
Or maybe there is something that we can do about it? Something that will open our code for extensions?
Java continues to evolve despite having been around for 20 years. If you're looking for the bleeding edge, Java might not be your best bet. However, if you're an existing Java developer, no need to worry about your marketability.