From One Expert to Another: Steve Berczuk Steve Berczuk is a software developer, writer, and experienced practitioner of software configuration management (SCM) and agile software development. He is a co-author of the book Software Configuration Management Patterns: Effective Teamwork, Practical Integration, contributed to the book 97 Things Every Programmer Should Know. Last year, he interviewed Dan Wellman about test-driven development. In this installment of From One Expert to Another, it’s Dan’s turn to interview Steve about the ins and outs of SCM. |
||
Are Personality Issues Leading to Anxiety and Dysfunctional Ops? The root cause of bad service may have much to do with a personality trait known as anxiety and the often-dysfunctional defense mechanisms people resort to in an attempt to deal with its discomfort. If you want your IT operations group to be successful, then you need to consider the personality issues—at both the individual and group levels—that may impact their performance and your success. |
||
Eight Mistakes that Prevent DevOps Success DevOps is more than just a buzzword; it’s about delivering value to customers faster and more reliably. Jonathan Thorpe explains eight mistakes that can dramatically increase cycle time and slow the flow of releases to customers, which is counter to the goals of DevOps. |
||
Descrambling Parallel Build Logs One of GNU make's many features allows you to shorten build times by running more than one command at a time. If your dependencies are all correct, or nearly correct, this can give you a significant improvement, and since it's built into the tool you get it "for free." But GNU make's parallel build feature—often called "dash j mode," after the command-line option that is used to enable it—is not without drawbacks. The worst of these is that GNU make parallel builds can produce incorrect results if the build dependencies are not sufficiently correct. |
Eric Melski
March 28, 2013 |
|
In a Flat World There Are Many Potholes Imagine that you are the project manager of a software delivery program. Say someone on your team has been stumped by a problem for numerous hours and needs to resolve this "show stopper" to move to the next delivery phase of the project. You have called an emergency meeting and gathered a group of analysts, architects, software developers, and testers in a room for you all to work towards solving the issue. What do you do? David Lipien and Nicolas Concha explain how to handle this stressful situation as well as the lessons to be learned. |
||
Guidelines for Building a Monolithic Release Management System The release management system is an important component of the service-transition process. This article highlights the importance of building a monolithic release management system, which encompasses all of the functions and processes necessary to support application build, package, and deployment. The monolithic release management is holistic, comprehensive, and based upon industry best practices. These guidelines are applicable for any type of organization or projects of any size. |
||
How DevOps Drives InfoSec While DevOps is typically thought of as being the relationship and interaction between development and operations, the truth is that DevOps impacts QA, testing, and—most importantly—information security (InfoSec). DevOps is, above all else, a set of principles and practices tailored to improve communication between all stakeholders, of which InfoSec is a key part. This article will help you integrate your InfoSec into DevOps. |
||
Crossing The DevOps Divide of Complex Personalities IT organizations often face challenges ranging from complex technology to even more complex personalities. DevOps attempts to address the dynamics between IT operations and highly skilled software and systems delivery teams. Read on if you would like to improve your skills in dealing with these challenging dynamics. |
||
Agile ALM for Delivering Customer Value: Getting Started In this first part of a two-part series, Mario Moreira writes that a reasonable application lifecycle management (ALM) product will have a common user interface for utilizing the ALM functionality. It will also include a meta-model and process engine to parse and share information across and amongst the various functions within the ALM framework. These technical needs must be accompanied by a strong business case for delivering higher customer value and new approaches for seamless integration. |
||
Don't Forget Operations' Point of View in DevOps Much of what is written about DevOps—a set of principles that helps development and operations teams work more effectively together—is delivered from the perspective of developers. In my opinion, DevOps needs to also take an operations point of view in order to be effective and practical. This article is all about putting the “ops” back into DevOps, so to speak. |
Pages
Upcoming Events
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |
Jun 08 |
AI Con USA An Intelligence-Driven Future |
Sep 21 |
STARWEST Software Testing Conference in Anaheim & Online |