G'day:
I've been really busy this week, and haven't been able to discover much interesting about either PHP or CFML or anything, hence being quite quiet. I'll admit this is very much a filler article, and a bit of a cheeky nod to something Andy said the other day:
Earlier I asked for people's opinions regarding TDD vs private methods: "The received wisdom of TDD and private methods".
I didn't get much feedback [scowl], but thanks to Dom and Gerry (there's a cat 'n' mouse joke in there somewhere) for offering up some thoughts.
I needed to provide a workflow for the team, and I thought I'd stick it up here as well, as a bit of closure on the previous article. And to give Andy a picture to look at.
What do you think of this approach (other than "unreadable at that size". Click here):
![]()
Forget the first two steps "Assign Ticket", etc, as that's just our Jira workflow and a bit of context for our peeps, but the rest of it after that. Also the associated process of how to maintain private methods whilst still adhering to TDD.
I think there's a reasonable mix of pragmatism and dogmatism in that?
Thoughts?
--
Adam
I've been really busy this week, and haven't been able to discover much interesting about either PHP or CFML or anything, hence being quite quiet. I'll admit this is very much a filler article, and a bit of a cheeky nod to something Andy said the other day:
@am2605 hahahahaha. Best I do some more charts soon then.Can't have my sole reader put off by all that weird writing shit.
— Adam Cameron (@DAC_dev) October 8, 2014Earlier I asked for people's opinions regarding TDD vs private methods: "The received wisdom of TDD and private methods".
I didn't get much feedback [scowl], but thanks to Dom and Gerry (there's a cat 'n' mouse joke in there somewhere) for offering up some thoughts.
I needed to provide a workflow for the team, and I thought I'd stick it up here as well, as a bit of closure on the previous article. And to give Andy a picture to look at.
What do you think of this approach (other than "unreadable at that size". Click here):
Forget the first two steps "Assign Ticket", etc, as that's just our Jira workflow and a bit of context for our peeps, but the rest of it after that. Also the associated process of how to maintain private methods whilst still adhering to TDD.
I think there's a reasonable mix of pragmatism and dogmatism in that?
Thoughts?
--
Adam