• submit to reddit
Giorgio Sironi11/07/12
0 replies

Scheduling is not the same for computers and people

Scheduling tasks for CPUs and for people has different requirements and assumptions.

Mark Needham11/06/12
0 replies

Configuration in DNS

Configuration in DNS is a valuable technique to reduce this complexity by using standard hostnames like ‘mail’ or ‘db’ and have DNS resolve to the correct host for that environment.

Mitch Pronschinske11/06/12
0 replies

Deployment: A Bottleneck No More

There's no magic tool that will completely solve organizational woes, but it would be crazy to deny that some tools make things a lot easier.

Roger Hughes11/06/12
0 replies

Implementing Continuous Delivery is Easy... Isn't It?

To my way of thinking, if you continually work weekends and late nights and suffer stress and cancelled holidays, so that you can painfully and manually push your app in to the production environment, then there’s something very wrong with your development process.

Giorgio Sironi11/05/12
0 replies

No one always needs a framework

Making a conscious decision for using an hammer is different from prescribing hammers as a panacea for all your problems.

Mitch Pronschinske11/05/12
1 replies

We Need a Programmer for President

Today, I'm going to present a new presidential candidate... A software developer candidate. This candidate is going to address the issues that the IT world cares about. Will you support them?

Michael Muller11/05/12
0 replies

Interview with Israel Gat on Technical Debt

Israel Gat, director of Cutter Consortium's Agile Product & Project Management practice, shares his thoughts on how technical debt can affect performance of development teams, the time when it is (or not) appropriate reducing it, and how it could be used as a tool for investment decision-making.

James Betteley11/04/12
4 replies

A Really $h!t Branching Policy

Branching is boring. Merging is also boring. None of this stuff is fun. But for some strange reason, I still see the occasional branching policy which involves using the largest number of branches you can possibly justify

Gil Zilberfeld11/04/12
13 replies

Technical Debt: I Do Not Think It Means What You Think It Means

The debt is an economic one, NOT technical. That’s no coincidence. Economics is a better way to persuade managers to listen to developers.

Sarah Goff-dupont11/01/12
0 replies

Story Branching and Continuous Integration: a swords-to-plowshares tale

Story branching, or "issue-driven development" is becoming an ever-more-popular development workflow, especially among agile teams. But how does one wrangle all those branches into a continuous integration scheme without adding a huge administrative burden?

Jurgen Appelo11/01/12
0 replies

I Don't Care About "Agile"

Of course, words like Agile and Lean were conceived to try and change the mindsets of managers and the cultures of businesses. But if these words don’t succeed, we shouldn’t mourn their defeat.

Giorgio Sironi10/31/12
0 replies

A CRC cards primer

A tool for doing design before and without writing code.

Rodrigo De Castro10/30/12
0 replies

What Makes a Great Operations Leader?

Read some of the great answers from John Allspaw to the question: "What are the attributes (other than technical ability/experience) that make a great VP of Technical Operations?"

Andrey Cheptsov10/29/12
0 replies

Top 20 Refactoring Features in IntelliJ IDEA

Following up on the previous article where we highlighted the top 20 features of Code Completion, I’d like to talk about the top Refactoring features that help make IntelliJ IDEA an extremely useful development tool.

Eric Minick10/25/12
1 replies

Standardizing Deployments? Start with Production and Work Backwards

Developers extend their continuous integration platforms towards continuous delivery organically, deploying to dev test environments for simple functional tests. And later to QA environments using similar approaches.