3 ms·
I think gfodor means that this: I know this might sound goofy, but BDD really does work. Didnt really get explained - why does it work? (I have to confess on
by ErrantX 17y ago
I think gfodor means that this:
I know this might sound goofy, but BDD really does work.
Didnt really get explained - why does it work?
(I have to confess one of my teams tried BDD for a while and it didnt really work out too well. Too much time making or meeting specs :))
- joshowens 17y agoErrantX, I added a third paragraph that might help with some insight as to why I feel this way. Going the BDD (or TDD) route first can help you in many ways... They include: finding unintended bugs, ensuring code works the way you want always, helps convey code intentions to other devs, etc, etc. If you found it was taking too much time, I would suggest you slow down a bit and really focus on BDD for a few weeks, you only get faster by practicing.
- tome 17y agoUnintended bugs?
- ErrantX 17y agoNah agile evangalism isn't our cup of tea. We do enterprise software without the enterprise bureaucracy - so adding in agile just takes it back that way. Ultimately I dont recommend anyone forces themselves into agile/TDD/BDD methodologies. They are systems designed by people to fit their working practices and preferred approach - its impossible to force yourself efficiently into the exact same mindset as someone else... The best approach is to pick and choose techniques and practices that fit your flow and develop your own way of working. You'll find it's vastly more efficient. (we have a couple of teams who finish contract work for other companies who's agile techniques just screwed the timetables/delivery :) so I've seen the difference in action)