• submit to reddit
Mitch Pronschinske03/30/12
0 replies

Poll: How Do We Handle Our Application Environments?

I've created a poll that will give us all some interesting insights into the status of the developer community and how we're managing our application environments and deployments. We'll be sharing the poll results with the participants in the coming weeks. So answer the questions below to make sure that we get a full picture of how hard or easy our lives are in the areas of performance monitoring and deployment.

Giorgio Sironi03/29/12
0 replies

Lean Tools: Value Stream Mapping

Value Stream Mapping: a difficult name for a high-ROI activity that takes half an hour.

Mitch Pronschinske03/28/12
4 replies

NEW Refcardz Topics (Round 2): Awesome or Lame?

See a new menu of potential upcoming DZone Refcardz with some brief descriptions. Then simply vote on whether you think the topic idea is AWESOME, or lame.

Giorgio Sironi03/27/12
1 replies

Bullets for legacy code

No silver bullets, but we do have some weapons.

Tom O'connor03/24/12
1 replies

A Manifest for Agile DevOps

For software development teams, Agile is a pretty good, native fit. The concepts embodied by stories and sprints fit a development team very cleanly. When it comes to systems administration and engineering, or what I’ve come to refer to as DevOps, Agile can be a bit more awkward initially.

Jp Morgenthal03/24/12
0 replies

Concise Description of DevOps?

Get a clear overview of the differing perspectives on what DevOps is. Some talk about it as a organization-wide culture shift to having all groups more involved with one another. Others think it is a position where someone has the responsibilities of a developer and a sysadmin.

Roman Pichler03/22/12
0 replies

My Preferred Approach to Agile User Interface Design

This writer prefers a method that is user-centric, iterative, and collaborative. Start with high-level design, move towards detailed design, and then pay attention to user feedback.

Tony Siciliani03/22/12
0 replies

Agile Practice and Game Theory

Much of the Agile movement has been influenced by scientific theories, like Complexity Theory, Chaos Theory or Game Theory. Here's a look at how the latter can be applied to software development.

James Betteley03/22/12
0 replies

Test-Driven Infrastructure with Chef – A Book Review

A while ago I ordered a copy of “Test-Driven Infrastructure with Chef” from Amazon. It must have been sometime last summer in fact. It took months to arrive, because they simply didn’t have...

Giorgio Sironi03/21/12
0 replies

TravisCI Intro and PHP Example

Travis CI is a distributed build system that's heavily integrated with GitHub and supports a multitude of languages. Here is a quick intro with a PHP example.

Marion Eickmann03/20/12
0 replies

An Agile Management Framework and Tools for Managers

This article describes the possible areas of application of an agile approach, using examples applicable to all types of business and showing effective agile tools especially for management.

Venkatesh Kris...03/20/12
1 replies

Agile Testing Vs Traditional QA

Take a look at this nifty comparison between Agile Testing and Traditional QA testing!

Eric Genesky03/19/12
0 replies

Video: Exploiting the Cloud for Speedy Development and Continuous Delivery

This Agile Web Practices webinar follows the announcement of a partnership between CollabNet and CloudBees. It shows how to efficiently develop/deploy in the cloud and reduce overall cost.

Bob Hartman03/19/12
0 replies

New to agile? Learn how to fail well

Agile teams will have times when they “fail.” I know a lot of people dislike using the words “fail” and “failure” when talking about team results. I’m actually pretty tired of that argument because I don’t think it helps anyone

Jim Bird03/19/12
3 replies

Defensive Programming vs. Batshit Crazy Paranoid Programming

There’s healthy paranoia, then there’s over-the-top-error-checking, and then there’s bat shit crazy crippling paranoia – where defensive programming takes over and turns in on itself. Jim Bird shows us some tips for defensive (paranoid) programming that aren't over-the-top.