Zach Dennis 4.18
For years developers have been looking for ways to improve how they write software. As a result we've gotten a plethora of methodologies, practices, and tools at our disposal. But how do you know when and what to use? And to what extent do you use them? No one wants to produce a mess of buggy and unreliable software. On the flip side, what good is NASA quality software that never gets used? This talk is a reflection on the presenter's experience practicing BDD and balancing the pendulum swinging from not enough to too much while producing reliable, working software.