• submit to reddit
Giorgio Sironi02/21/12
0 replies

The 7 habits of highly effective developers

The 7 habits of Stephen Covey can be applied to software development too. Let's start with the failure of an Internet connection.

Esther Derby 02/20/12
1 replies

How Do You Decide on Methodology? Look to the Needs of the Team

The point of any agile role is to help a team learn new skills, improve, and transition to new ways of working. There are many elements of a role to consider before choosing an effective methodology, including qualities, preferences, and style for the role.

Cody Powell02/20/12
0 replies

Understanding-Driven Development

I have a weird idea. What if, with every change we made to our codebase, we tried to increase our understanding of it a little bit? This is challenging because codebases always go in the opposite direction. How do you increase understanding on a large scale, then? Let's go through a few approaches, none of which are earth shattering.

Geoffrey Papilion02/19/12
7 replies

Sometimes It’s Okay to Incur Technical Debt

Your avoidance of Technical Debt shouldn't block all other tasks because of one issue. It's better to have a partially automated solution, than none at all.

Jessica Thornsby02/18/12
1 replies

Polling Subversion with Jenkins

There are many advantages Jenkins can offer Apache Subversion users, one of which is the option of automatically polling Subversion repositories for changes, and creating a new build whenever changes are detected. Implementing this functionality is made easy in this tutorial.

Steve Rogalsky02/17/12
0 replies

Simple, But Not Easy: Agile Advice for Beginners

Some of the common problems illuminated by this post include an "out of control scope" and "never ending projects." The author also includes some links to useful articles, books, and podcasts.

Dror Helper02/16/12
0 replies

The Evolution of a Taskboard: Sticky Notes, Excel, and Beyond

This post covers the blogger's experience with managing tasks in his team of developers. He discusses how a sticky-note-oriented task table can be converted into a useful excel sheet, and then takes it a step further.

Jim Bird02/15/12
2 replies

Technical Debt: How Much is it Really Costing You?

According to one report, “applications carry on average $3.61 of technical debt per line of code”. The figure seems a bit arbitrary and absolute in a context where there can be so many variables. This review will give you a better idea of technical debt by looking at different kinds of technical debt, and how much they might cost you.

Giorgio Sironi02/15/12
0 replies

Practical PHP Refactoring: Extract Hierarchy

God classes contain many conditionals and switches: extracting a hierarchy is a possible step to make the design manageable.

John Esposito02/15/12
52 replies

Ask DZ: What Features Would an Ideal IDE Have?

You may love your IDE, but even the best IDE can get better. Or you may be chugging along with a free, open-source, but less-than-perfect IDE, plugging the functionality gaps with plugins that may or may not integrate perfectly. So, DZonistas: what features would an ideal IDE have?

Mitch Pronschinske02/14/12
0 replies

Is DevOps a Power Grab?

One blogger has made his opinion known about DevOps recently, calling it a power grab for devs and cloud vendors who envision a "NoOps" world. I have a few opinions about what he says, but let's hear what you think.

Giorgio Sironi02/13/12
0 replies

Practical PHP Refactoring: Separate Domain from Presentation

SQL and HTML are not friends. Separating concerns is the most basic step for building a maintainable web application instead of a big ball of mud.

Jp Morgenthal02/13/12
0 replies

Dependency Creep on Cloud Migration: A Potential Solution

This article suggests a common solution to the common problem of users trying to access information within a company using applications that have not been developed as part of a cohesive strategy. Morgenthal looks to DevOps to foster communication between engineering and operations.

Ayende Rahien02/13/12
1 replies

The Economics of Continuous Deployment

Selling software is hard. Ayende Rahien knows because he has his own product that he sells. One of the big difficulties is how to keep improving the product so that there are continual 'major' new releases with new features that are enticing enough for people to buy the next version. Join in Ayende's discussion on the best ways to monetize our software with concepts like continuous deployment.

Aaron Nichols02/11/12
0 replies

The Never Shrinking Result of Consistent Review

The problem with turning over rocks is that there’s usually ugly stuff hiding underneath. You retro every 2 weeks and you list out all the stuff that isn’t working. You diligently collect all the deltas and turn those into actions. You collect all the actions from your retro’s and your post-mortems and you track them in a tool where they sit… forever.