In business there are many ways to gain a better perspective about a project Customer visits are a fantastic way to expose developers to actual and/or potential clients. Initiating a visit shows customers a personal level of attention that they rarely get from most companies they interact with.
Code review is a great software instrument and you should definitely use it to improve the quality of your code. But like any other tool, it may be misused sometimes. That’s why I came up with a list of best practices to guide you when reviewing your peers’ code.
Key management is defined as a group of operations such as generating, exchanging, storing and protecting security artifacts. Without effective management of such valuable resources, the system can be easily compromised by attackers.
There is hardly anything more infuriating that seeing a method @Deprecated without a proper documentation. I feel lost. Should I still use the method?
As an Enterprise Architect, I took an interest in this book as an opportunity to validate my understanding of security and ensure that ,in the design and guidance work that I do, I am providing good insights and directions so that the application architects and developers are both ensuring good security practices.
Canary Tests are minimal tests to quickly and automatically verify that the everything you depend on is ready.
Getting your arms around all those tools and frameworks needed to write solid, tested cookbooks gets you spinning. You need to install Food Critic, Chef Spec, Berkshelf – and the list goes on. This set up can easily take up to half a day or more.
This book is a must-read for all Git users. It’s usable on all levels, from absolute newbie to someone who feels fairly proficient with Git. I’ve been using Git daily for quite a while, and it really helped me understand what is going on. Everything is very accessible, with plenty of examples as small and practical as possible, as well as some images.
This installment of the DevOps Dudes series from Matthias Marshall looks at DevOps and mountain climbing.
Every week here and in our newsletter, we feature a new developer/blogger from the DZone community to catch up and find out what he or she is working on now and what's coming next. This week we're talking to Rafael Winterhalter, Java enthusiast and software engineer at Kantega in Oslo, Norway.
Open source is playing an increasingly important role in IT infrastructure generally. But is open source a natural evolutionary path for all IT disciplines, or are there certain characteristics that make some areas more ripe for open source than others?
Given an array of n rows numbered 0 to n-1, each of m seats 0 to m-1, where the cells have values True (meaning the seat is available) or False (meaning the seat is taken). A customer states that his favorite seat is at row x and seat y on that row.
Technical debt is not the only monster we have to fight – it has a hidden evil twin, as pointed out by Niklas Björnerstedt: Competence Debt. There is an often neglected tool at our fingertips that might help us fight competence debt. Its name is – behold – JavaDoc
One nice little feature of most debuggers that I have been exercising recently is the ability to log information on a breakpoint. This can be a really useful way to understand code without having to modify it or involve byte code modification, and in this article, you'll learn how to do it.
If you want to learn something about Apache Maven, why not try this new video tutorial? After watching the videos, the author thinks it looks like a good starting point. You may find other tutorials on YouTube, but in his opinion, it is worth checking out this course, because it handles all major topics.
Puppet, a popular configuration management tool, is used by many IT companies to help facilitate and automate the setup of environments. This is a hands on guide for how to quickly install Puppet a MySQL instance in just a couple of minutes.
Let's set the scene: The project has been humming along, and a new request comes in for a minor change. It's completed in quick order, QA signs off, but the customers are frustrated and confused. To find clarity, stop focusing on what did happen and dig a little deeper into what didn't happen.
Recently, one of my government clients decided to switch their public facing ASP.NET to Drupal (an open source solution), and they had an embarrassing hacking scenario. There are a number of disadvantages to open source systems that you should be aware of before making the switch.
The Boy Scouts have a rule: “Always leave the campground cleaner than you found it.” What if we followed a similar rule in our code: “Always check a module in cleaner than when you checked it out.”
In this post we are going to learn the benefits of Continuous Integration in Software Development. Let’s understand what continuous integration is first and then we will discuss the benefits we are having.
I frequently hear or read people suggesting using User Stories for relatively long-range planning. Sometimes they mean something as short as a release in a few months. Sometimes they’re talking about multiple releases over a year or two. What are the implications for doing this?
NuoDB 2.0 was recently released and it delivers some major new geo-distributed management features, along with database automation and SQL and Java stored procedures. The geo-distribution capabilities enable users to distribute a single logical database across multiple cloud regions or data centers.
I’ve been pushing this branching model for something like 14 years now. It’s nice to see Facebook say a little more about their Trunk Based Development. Of course they’re not doing it because they read anything I wrote, as the practice isn’t mine, it’s been hanging around in the industry for many years, but always as bridesmaid so to speak.
If you’re like me, you may have 30 branches at any given time. This can make viewing all the branches unwieldy. Once I week or so, I would go on a branch deletion spree by manually copying and pasting multiple branch names into a git branch -D statement.
How does your engineering organization build and deliver products to its customers? Similar to the well-known capability maturity model, the maturity level of a build automation system falls into one of the following: chaotic, repeatable, defined, managed, or optimized. Let’s take a look at the differences in these levels.