<?xml-stylesheet type="text/xsl" href="https://emersonexchange365.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>Tip #6: Change for the Sake of Change Is Not Always a Good Thing</title><link>/services/b/tips/posts/tip-6-change-for-the-sake-of-change-is-not-always-a-good-thing</link><description>I am a risk-averse engineer. My clients do NOT like surprises, and they pay me a decent salary to make sure that their automation projects go in as painlessly as possible. Therefore, I do not apply new technologies unless I know they work and I am content</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator></channel></rss>