<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Best of the Week on Dhaval Shah</title><link>https://www.dhaval-shah.com/categories/best-of-the-week/</link><description>Recent content in Best of the Week on Dhaval Shah</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Thu, 05 Jan 2017 19:48:47 +0000</lastBuildDate><atom:link href="https://www.dhaval-shah.com/categories/best-of-the-week/index.xml" rel="self" type="application/rss+xml"/><item><title>Anatomy of Test Driven Development – Part 1</title><link>https://www.dhaval-shah.com/anatomy-of-test-driven-development-part-1/</link><pubDate>Thu, 05 Jan 2017 19:48:47 +0000</pubDate><guid>https://www.dhaval-shah.com/anatomy-of-test-driven-development-part-1/</guid><description>Since we being one of the most intellectual and so called logical species on this earth, we need proper rationale behind each and every action that we do in our personal and professional life. Hence I thought to pen down a two post series highlighting rationale behind following one off the most important and underrated XP practice of software devlopment i.e. Test Driven Development
What is TDD Lets try to understand definition of TDD and the primary motive behind TDD; this was outlined by none other than one of the protagonist of TDD i.</description></item></channel></rss>