Continuous Delivery is a software development discipline where you build software in such a way that the software can be released to production at any time. You’re doing continuous delivery when...
As there is no “official” definition for DevOps, many individuals and organizations have their own definition. This morning at Innovate, IBM introduced its take.
The growing cost of most software development efforts can be traced back to one underlying cause – the lack of visibility into the software.
Writing a single application or installer that will work uniformly on 32-bit and
64-bit machines is complicated. Here's how.
Today: Arduino on the farm, Flask wants your help, and pure procedural programming with Fishbike. Plus: Intricate circuit-board beasties and wisdom from Joss Whedon in an unexpected place.
In this talk, Paul Gerrard discusses continuous delivery, particularly as it pertains to long-term requirements. Testing up front, he says, helps to deliver "front-door quality, not back-door quality."
One of the challenges of an automated build and test environment is you want your build to be fast, so that you can get fast feedback, but comprehensive tests take a long time to run.
I’ve already blogged about Deploying on Azure Web Site with Database Project in the past, but in that article I showed how to accomplish it with customization of the Build Template.
I've evaluated many open source projects and realized that APIs are often not documented well. It is important for the community to know what the reasons behind this.
Should we deploy a unique tool that is able to manage a wide variety of technologies and quality domains, or do we need a “pure player” tool dedicated to each technology’s specificities?
What is so cool about the possibility to access private class members from outside? Everyone keeps asking you during job interviews what are the basic rules of object oriented programming.
I would suggest going slowly toward automated modernization. I'm not easily convinced that any automated tool can preserve what's meaningful and ignore the parts which are quirks, bugs or legacy cruft that needs to be disposed of.
Integration testing sometimes involves writing complex codes. This book introduces you to the capabilities of Arquillian to enable you to write simple code with a broad range of integration tests for Java applications
Intro to “Asgard” -- an open source web interface for application deployments and cloud management.
To avoid having to build your own dialog box from scratch, the JOptionPane class provides methods to make a variety of dialog boxes by simply feeding them some parameters to determine the appearance of the dialog box.
We build our application and push it to Production after a lot of hassle and take a great sigh of relief...but this is not the end of the story.
Every team member has their specialty. Infielders have great reactions and throwing accuracy. Outfielders can cover distance quickly and throw long distances. Likewise, there are specialized positions on a development team.
What was once a beautiful idea that promised a future without (too many) passwords has now become completely useless feature.
Everyone now and then I want to check the contents of an archive without unpacking it, and I tend to use unzip to do so...
Insecurity can be very easy. What I mean by this is that sometimes it can be the smallest change to a website that blows the security wide open.
One of the goals of the QCon conferences is to act as “information Robin Hood” – finding ways to get out into public the secret sauce of high-performing organizations. So I set out to find talks that would answer the questions I frequently get asked.
Having each developer (development team) configure their continuous integration tool’s build jobs is extra work for the team, leads to inconsistencies/mistakes, and the overall build system becomes a pain to manage.
It's entirely possible to use BIND (or PowerDNS, for that matter) as a DNS server instead of the integrated MS DNS service that's bundled with Windows Server.
Did you ever imagine that someday it would be possible to code in the cloud? Create an app, test and debug it and deploy to a production PaaS, entirely in the cloud? Well, the good old desktop days are gone.
Success is directly influenced by the ability of your QA and Dev teams to work well together. Failing to understand the relationship between QA and Dev will take your product/team in the opposite direction. There is a delicate relationship between the two, and a certain tension that must be confronted and not overlooked.