4 ms·
TDD starts with failure. I don’t really subscribe to TDD, but they have a valid point: Start with something that doesn’t work, and work on it, until it works.
by ChrisMarshallNY 5y ago
TDD starts with failure.
I don’t really subscribe to TDD, but they have a valid point: Start with something that doesn’t work, and work on it, until it works.
I tend to develop my software in a similar way, but I also start with a “fuzzy” design, which would give TDD people fits.
I fail every day. Repeatedly. It’s how I end up with some damn good software, at the end of the day.
- agumonkey 5y agofailure + exploring solution space + minimizing said space <= I need a book about that :)
- ChrisMarshallNY 5y agoI could probably write one, but writing books is hard. I am still smarting from the time I wrote a 400-page book, that was out of date before it could be published. I do have a blurb that discusses my design philosophy here: https://littlegreenviper.com/miscellany/evolutionary-design-specification/ https://littlegreenviper.com/miscellany/evolutionary-design-...
- agumonkey 5y ago"Vague" systemic exploration is interesting, having live prototypes to modify and refine gradually, to gain knowledge and maybe readjust the substructures.
- ChrisMarshallNY 5y agoHere’s an object example: I’m developing a fairly ambitious iOS app. It’s a social media-like app, based on aggregate servers. I wrote the servers, myself, years ago. One is currently a world standard, and heavily in use. The other, was a server I wrote a few years ago as a “practice” project. The app, itself, has been under development for over a year. A big reason for that, is the team had only a vague idea of what it would do. It wasn’t really feasible to get them to hash out a more detailed plan, so I set up a “breadboard” system, based on Apple’s TestFlight beta-test system [0]. TestFlight is usually only engaged towards the very end of a project, but we’ve been using it since one month after my initial checkin. TestFlight requires a fairly “complete” app, that runs without tripping any alarms (like crashing). Apple vets each release. I can produce a fairly full-featured app, quite rapidly, so I was able to meet Apple’s quality bar, pretty quickly. Because we are using TestFlight, we have some significant advantages: 1. The app is constantly at “beta” quality. Even with incomplete functionality, what’s there, works well. I cannot overstate the importance of this. 2. We can have non-technical stakeholders constantly “test driving” the UI, and providing relevant, useful feedback, on a continuous basis. They are also highly motivated and engaged. 3. Because Apple is constantly vetting the app, we know that we probably won’t have any nasty surprises, when we finally release. During this year, we have explored a number of avenues that have resulted in “dead ends.” I’ve tossed out months’ worth of work. That’s great. The best code I write, is the code I don’t write. I’m happy to tear out huge chunks of code. The result is that we now have a clear, robust, ultra-high-quality app that is in the final stages of development. I still have a couple of areas of functionality to add, but we’re done prevaricating. We know where we’re going, and everyone is on board and psyched. The quality of the app is also, quite frankly, jaw-dropping. We’re all thrilled to death. Using TestFlight has allowed us to work through a lot of stuff that is often encountered during early MVP stages; without the brand damage and public humiliation. [0] https://developer.apple.com/testflight/ https://developer.apple.com/testflight/
- peterburkimsher 5y agoTDD has some excellent philosophy behind it, but I struggle to implement it because I get discouraged by failure, and move on to other topics. If the TDD approach said "thank you" for the good parts (code structure, not breaking 500 other test cases), that would make the 13 errors less scary. One of the things I like about software is that it's "soft" - it should be possible to make changes without the fear of getting it wrong, and be able to fix them now while I see the problem, rather than procrastinating until later when I've forgotten about it. The same "thank you" system applies when working with external contractors (e.g. language translations). We can assume they tried their best, and therefore might not know what else to say. Reporting 19 problems will get us a reputation for being nitpicky, hostile, even toxic. Rather, we should thank them for the 730 that they got right, and suggest improvements for the 19 that we think might be better. With thankfulness and encouragement, TDD could really change the industry for the better.
- ChrisMarshallNY 5y agoI like your attitude. I've always preferred carrots over sticks.