I really enjoy reading empirical studies that challenge how I think about building software. The studies about TDD still make me squirm as my career started with pretty strict TDD, but the findings about benefits being rooted in shorter cycles does make sense to me.
I find it useful for young programmers to spend at least some time doing TDD, even if they never do it again, for the experience of imposing discipline on how they program and because it often kicks them into a different mental view of the act.
I would be interested in a summary post on “results of software engineering research”. I looked at the slides of this talk, but the results cited look more like “we don’t actually have much empirical evidence about software engineering processes”. This is interesting, but not actionable.
Nice one, thank you! By the way, it was shared at the time with some comments (well, one comment).
I really enjoy reading empirical studies that challenge how I think about building software. The studies about TDD still make me squirm as my career started with pretty strict TDD, but the findings about benefits being rooted in shorter cycles does make sense to me.
I find it useful for young programmers to spend at least some time doing TDD, even if they never do it again, for the experience of imposing discipline on how they program and because it often kicks them into a different mental view of the act.
I would be interested in a summary post on “results of software engineering research”. I looked at the slides of this talk, but the results cited look more like “we don’t actually have much empirical evidence about software engineering processes”. This is interesting, but not actionable.