I almost didn't the article because wth can NYT tell us about agile software? Some thrice-washed-down generalization for the masses, full of holes? Turns out i

I almost didn't the article because wth can NYT tell us about agile software? Some thrice-washed-down generalization for the masses, full of holes? Turns out it's from their dev blog and it's an interesting read.