<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>....And the kitchen sink!</title><link>/technologies/businessofengineering/b/blog/posts/and-the-kitchen-sink</link><description>Early in my consultancy, I was eager to please. First clients aren&amp;#39;t easy to find! But this particular client was working on a new microcontroller implementation of an existing product. It started as a simple way to control the system, but as opportu</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: ....And the kitchen sink!</title><link>https://community.element14.com/technologies/businessofengineering/b/blog/posts/and-the-kitchen-sink</link><pubDate>Tue, 21 Oct 2014 10:51:18 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:2305e909-37c7-4588-854d-c703551bb698</guid><dc:creator>Workshopshed</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;There&amp;#39;s a principle of &amp;quot;Extreme Programming&amp;quot; called &lt;span class="st"&gt;YAGNI or &amp;quot;You arn&amp;#39;t going to need it&amp;quot;. The idea is that you should avoid adding functionality early as it will impede development and if it&amp;#39;s needed it can be added later.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span class="st"&gt;I wonder if this can be applied to hardware too or if the cost of change makes that approach equally unworkable.&lt;/span&gt;&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=18735&amp;AppID=96&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>