I love sitting down to review a new codebase. Depending on the age of the codebase, it can be a little like archaeology. There are often distinct sections that have not been touched in many, many years. Sometimes you can almost see rings around the codebase similar to the rings on a tree. One section might be written in one framework, but another section is implemented in a different, newer framework. The following describes how I spend the first hour with some new code.
Vendor lock-in can be a pain. Imagine you've written an application to work against one cloud provider and now you'd like to migrate to another one.
Creating that initial environment for your application to run in is a solved problem. Or is it? On the market today, there are a seemingly ever-increasing number of tools to facilitate that process: CFEngine, Puppet, Chef, Vagrant, Packer, Ansible, Salt Stack, Rundeck… the list goes on.
Last week, I took some days off to attend Devoxx France 2014 3rd edition. As for oysters, the largest talks do not necessarily contain the prettiest pearls.
Like any new development methodology, implementing Continuous Delivery has a number of pitfalls that can trip up even the most mature organizations. In this article, you'll find four of the most common pitfalls to avoid when implementing Continuous Delivery.
Once you've downloaded DZone's 2014 Guide to Continuous Delivery, you may be looking for some additional resources to help with your implementation of CD. We dug into the DZone archives and pulled out a handful of DZone's most popular Continuous Delivery resources over the last couple of years.
Of course after OS X Mountain Lion it was the time to update my Java on OS X Mavericks. Let’s see how to use multiple versions of Java on OS X Mavericks.
41% of developers believe they are achieving Continuous Delivery while only 8% actually are. Use the Continuous Delivery Maturity Checklist from DZone's 2014 Guide to Continuous Delivery to determine how close you are to achieving true Continuous Delivery
So why release regularly? I would argue that releasing regularly makes you code in a certain style. When you know you have a release deadline coming up, it helps to focus the mind on which issues really need fixing. It also means that you code to a minimum, and, I find, helps keeps my code lean and mean.
I have seen lots developers are not seeing benefits of Test Driven development. When you do Test Driven development there are lots of benefits. So I thought it will be good idea to write a blog post about it. t will definitely make you more productive and it’s your friend.
The traditional gap impedes system integration, user acceptance testing, visibility into project progress, and corporate governance. ALM PaaS bridges the development gap between corporate IT and distributed outsourced development activities.
A vigorous area of debate in the development and architecture community exists around the value of Continuous Integration.
Attention to new features in JDK 8 has rightfully been largely focused on new language features and syntax. However, there are some nice additions to the libraries and APIs
This episode takes a look at a core component of continuous delivery: the application update mechanism. We talk a bit about our collective experiences supporting update paths, and whether or not that’s actually good for customers, or it’s just a myth we hear parroted constantly.
I’ve been playing with Vagrant over the last few days, using Ansible to provision it. These are some notes to remind myself for next time and are very disjointed! Configuring Vagrant to provision using Ansible is easy enough.
The author has been "busy" this weekend doing several things. But nothing more important than playing the addictive game 2048. In this article, you'll find a JavaFX version called 2048FX, so you can learn how to code a game like this and also several new features of Java SE 8 and JavaFX!
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 Steve Smith, Agile consultant and Continuous Delivery specialist at Always Agile Consulting Ltd.
Usually, a project has a minimum Java version requirement and that applies to all of its modules. But every rule has its exceptions, as recently I stumbled on the following issue.
This week's link roundup includes Chef's new Microsoft Azure integrations, Cassandra hits one million writes per second, Hadoop has a new search engine, utilizing continuous delivery, the 30 best tools for data visualization, and an answer to why Unreal Engine 4 uses C++.
For DZone's 2014 Guide to Continuous Delivery we created this detailed infographic to illustrate the creation of deployment pipelines. The Guide includes in-depth articles written by industry experts, survey results from 500+ developers, and profiles on 38 popular Continuous Delivery solutions.
Chris also discusses how tech companies, specifically, can up their skills by learning improvisation basics, and how this all fits in with companies on their own DevOps transformation journey, plus illuminates some surprising facts about what the basics of improvisation are about!
I am a recent convert to thymeleaf for view templating in Spring based web applications, preferring it over jsp's.
Small debt to the quality may speed the development process, but it should be paid back, sometimes by means of complete revision of the technical solutions. In case, the debt is not paid back: product development is blocked by technical problems of the project.
Debates about the usefulness of ORM (Object-Relational Mapping) have been going on for the last decade.
In this article, I’m going to outline the importance or addressing your company’s source-control use before diving too far into CD. Specifically, I’m suggesting that you should decide whether your enterprise should do Trunk Based Development (TBD) in one big trunk or not.