This article represents top 5 coding practices related with Java exception handling that you may want to watch out for or better say, avoid, while doing coding for exception handling.
Though I love learning new programming techniques and technologies, I often struggle to make them a part of my normal development processes
Disclaimer: this is not a TDD vs. BDD post – now that we’ve got that out of the way let’s discuss the thing I hate most about BDD…
I’m going to try to explain the alternatives for Trunk Based Development (TBD) in terms of branch layout. There’s few different styles, that different types of development organization might try to implement.
Today, DZone released its latest Refcard: Getting Started with Scala. If you're interested in learning more about Scala or sharpening your skills, we decided to dig into the DZone archives and find some of the most popular posts we've had on the topic.
When we talk about testability we usually mean "hard to test". That is a whole discussion by itself, because "hard to test" is also subjective. If we follow the theme of testing as an investment to minimize future maintenance costs, then "hard to test" translates to "Costly to test" or "risky to test".
Understanding a software design proposal is so much easier once you can actually visualize it.
Crowdsourcing has had a pretty big impact upon most industries, but perhaps software development has seen a bigger impact than most. The rise of social coding sites such as BitBucket and GitHub have transformed the way software projects are undertaken.
One of the most poorly understood concepts in product/software development is incremental delivery.
The developer survey from DZone's 2014 Guide to Continuous Delivery gave us a few more insights than we were able to include in the guide. For a bit more detail on tool usage in Continuous Delivery, we've created this new infographic.
If you understand the definition of“average” you shouldn’t be offended by me calling a large number of programmers average or below.
The traditional Ops toolkit often involves a range of tools that help monitor trends in KPIs as well as tools that perform different periodic health checks on key components of your systems.
I recently put together an end-to-end demo showing step-by-step how to set up a Continuous Delivery pipeline to help automate your deployments and shorten your cycle times for getting code from development to production.
No one loves Null Pointer Exceptions ! Is there a way we can get rid of them ? Maybe . . .
Here is a quick solution for those encountering the “Failure to Transfer” error in Maven.
Influence debugging is an efficient active debugging method by which you can ignore a large part of your code during bug hunting. You can go backward along influences exclusively until you catch the bug. Tricky missing code errors can also be detected by this new method.
Often developers writing code that they think is useful and relevant while they are not listening to their target audience, in this case not the end users of the systems but the people that are maintaining the platforms. The people that work on a daily base with these tools.
The Javadoc for the ChoiceFormat class states that ChoiceFormat "allows you to attach a format to a range of numbers" and is "generally used in a MessageFormat for handling plurals."
It’s been 10 years since I wrote my first unit test. Since then, I can’t remember how many thousands of unit tests I’ve written.
The selection of a more modular architecture tends to result in an organization with more (smaller) teams.
How you can use the Graph analysis and visualization Tool Gephi to have a look into the Package Dependency structure of your Java Project with a "graph perspective."
One of the most frequently voiced criticisms of the Java programming language is the amount of Boilerplate Code it requires.
While Spock can be used for some property-based testing, ScalaCheck and ScalaTest may be your best option.
At JavaZone I attended many great talks by brilliant speakers, but one was really head and shoulders above the lot: “Software Design, Why, When and How” by Kent Beck.