Code confusion and complexity is a problem in most software projects, and we can clearly see this in enterprise projects. The reason for this confusion might be fast and unplanned developing, poorly-designed structure and undefined architecture. But we have to know this. Code is inherently complex.
In my last blog, I started to talk about the need to figure out whether or not your application is misbehaving in it's production environment.
In the first post in this series, we took a quick look at Red Deer’s implementation of Requirements classes. In this post, we’ll take a more detailed look at Requirements, including how Red Deer supports your creating custom Requirements.
Even if last week, we promised an article on concurrency, there is one very important aspect of Java 8 lambdas and interoperability with “legacy” APIs that we need to talk about, first.
Strange that we still worry about duplication.
When I started programming some years ago, I would comment everything, and I mean everything.
My point here is not to put down the DevOps tools. Instead, I want to point out that how these tools are used is important. If you view tools like Chef or Ansible as a means of cutting out keystrokes (read: pushing config), then you are likely missing the point of automation. What these types of tools are really trying to do is much more profound.
A short "how-to" based on an issue one of my work mates recently faced when trying to automate the creation of an MSI package on Jenkins.
I spoke with my DBA friend today who runs an Oracle data-warehouse that’s about 2 terabytes big, at an international bank. I asked him: "What are some typical problems that users, data analysts, and DB developers have, that make you want to pull your hair out?" (to be fair, he doesn’t have much hair left, so if he’s willing to make that final sacrifice, these must be some big issues). In his experience, the vast majority of performance problems fall into these categories.
This post is my review of this training video on configuring, deploying, and administrating the JBoss Enterprise Application Platform.
Not long ago, in a blog post, I explained what Closure were in Groovy. This blog post will explain one good example of using them.
If the average programmer writes about 50 lines of production code a day. A 50,000 line program would take 1,000 man days to produce. The 50,000 line listing can be entered by a programmer at about 1,000 lines a day or about 50 man days. So what the heck are the developers doing for the other 950 days?
Do you need to make your Java library publicly accessible? Is your project hosted on GitHub? Do you like idea of "all-in-one deploy to Maven Central Repository" button? The author is going to show you how to set it up using the maven-release-plugin.
Are you using an IDE, or an editor? Are you a “hardcore” programmer, or you are one of those sissy modern developers that use IDEs?
I often need to have multiple versions of Java installed on my machine.
Mercurial is an awesome source control system! If you got a project in your PC and would like to share with your team. An easy and practical way is to put it in a common server (eg: linux) with ssh enabled.
The author was asked to put together examples of how to mock Java constructs well know for their testability issues. He calls these techniques unusual mocking. Developers practicing TDD or BDD should be aware of testability problems behind these constructs and avoid them when designing tests and modules.
Sometime it happens that when you configure a Maven mojo plugin, the given configuration doesn't apply or doesn't work as expected, but debugging Maven mojo plugin sources is now very easy with NetBeans 8. This short article shows you how.
Java EE in general and Context and Dependency Injection has been part of the Vaadin ecosystem since ages
I’ve come across this interesting article titled "Don’t Reinvent the Wheel! Use a Framework!" They All Say.
WebLogic is Oracle's strategic application server for the Java EE Platform
Successful, long-lasting movement have a clear manifesto outlining goals and principles. Many DevOps adopters may not be aware of the DevOps Manifesto (created by Jez Humble @jezhumble) nor how successful DevOps requires keeping a clear focus on principles, practices, and value (instead of infrastructure tooling).
Plumbr is all about detecting performance problems from within Java applications.
If you have to test methods handling complex objects or voluminous data, you easily end up with a bunch of unreadable assert statements. The visual approach featured by MagicTest allows you to write such tests very efficiently. To prove this, the author invites you to a testing challenge.
DZone would like to reveal the next topic in our new series of monthly Research Reports. We'd also like to show you how you can be a major part of them!