﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Editorials / SQLServerCentral.com  / More Evolution, More Complexity / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Mon, 20 May 2013 15:21:10 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: More Evolution, More Complexity</title><link>http://www.sqlservercentral.com/Forums/Topic1424912-263-1.aspx</link><description>[quote][b]Jeff Moden (3/8/2013)[/b][hr]I think that a lot of people grossly confuse the words "change" and "improvement".[/quote]So true.Recently, I have seen a re-write which a months into the engagement I was in a meeting when a senior management asked the attendees whether the re-write was "rubbish". Then I was glad that I wasn't asked directly as from the little I saw I wouldn't have been confident enough to say "no". As it stands, if asked directly today my answer would be "yes". All change, little improvement (if any) in performance, reliability and maintainability.</description><pubDate>Mon, 11 Mar 2013 04:07:33 GMT</pubDate><dc:creator>Gary Varga</dc:creator></item><item><title>RE: More Evolution, More Complexity</title><link>http://www.sqlservercentral.com/Forums/Topic1424912-263-1.aspx</link><description>I think that a lot of people grossly confuse the words "change" and "improvement".</description><pubDate>Fri, 08 Mar 2013 21:58:44 GMT</pubDate><dc:creator>Jeff Moden</dc:creator></item><item><title>RE: More Evolution, More Complexity</title><link>http://www.sqlservercentral.com/Forums/Topic1424912-263-1.aspx</link><description>I'm hoping that the SQL Server evolution will lead to less Performance Tuning by the DBA. Surely everything that a DBA can determine about the performance of a Database Engine could also be determined by the Engine itself and corrected ?I would like to see the day when a SQL Server DBA's Job is more about the Architecture of the Databases than why is the Engine performing badlyDavid</description><pubDate>Fri, 08 Mar 2013 20:40:19 GMT</pubDate><dc:creator>David Conn</dc:creator></item><item><title>RE: More Evolution, More Complexity</title><link>http://www.sqlservercentral.com/Forums/Topic1424912-263-1.aspx</link><description>[quote][b]batgirl (2/28/2013)[/b][hr]This really speaks to me today.  [/quote]Glad to hear it, and glad things are going well.Love to see a card trick if we end up at the same event sometime.</description><pubDate>Thu, 28 Feb 2013 10:11:55 GMT</pubDate><dc:creator>Steve Jones - SSC Editor</dc:creator></item><item><title>RE: More Evolution, More Complexity</title><link>http://www.sqlservercentral.com/Forums/Topic1424912-263-1.aspx</link><description>[quote][b]Gary Varga (2/28/2013)[/b][hr]I've suffered a serious burnout once and a close call one other time. As with many things, recovering from going too far is harder than not going too far in the first place. Having said that, there are far too many people in IT who are "knowledge static" (my term). They either learnt somethings and decided that was enough or just muddle through never intentionally improving themselves.This editorial highlights that continuous improvement is an essential, albeit slow, never ending task.Of course, the sheer fact that we are here on SQLServerCentral.com probably means that we all have already accepted this ;-)[/quote]This really speaks to me today.  I reached a full burnout point about 18 months ago - mostly due to an overwhelming workload that did not allow for learning anything new.  I really jumped off the deep end - left my job to pursue a totally new career as a blackjack dealer.  It didn't go very well for me and I felt "trapped" into having to come back to IT.  Fortunately I found a great new spot that has put me back into learning mode.  I'm really lucky to have landed softly.  And as a bonus, I have a new set of card tricks!</description><pubDate>Thu, 28 Feb 2013 06:16:52 GMT</pubDate><dc:creator>batgirl</dc:creator></item><item><title>RE: More Evolution, More Complexity</title><link>http://www.sqlservercentral.com/Forums/Topic1424912-263-1.aspx</link><description>I've suffered a serious burnout once and a close call one other time. As with many things, recovering from going too far is harder than not going too far in the first place. Having said that, there are far too many people in IT who are "knowledge static" (my term). They either learnt somethings and decided that was enough or just muddle through never intentionally improving themselves.This editorial highlights that continuous improvement is an essential, albeit slow, never ending task.Of course, the sheer fact that we are here on SQLServerCentral.com probably means that we all have already accepted this ;-)</description><pubDate>Thu, 28 Feb 2013 06:02:56 GMT</pubDate><dc:creator>Gary Varga</dc:creator></item><item><title>RE: More Evolution, More Complexity</title><link>http://www.sqlservercentral.com/Forums/Topic1424912-263-1.aspx</link><description>Technology does evolve and in some cases it evolves quickly. As an IT/Data professional keeping abreast and up to date  of the changes that impact your job is vital to your career success. If you standstill as an IT professional you will get left behind.I fully agree that you can't learn everything at once and pacing your learning over say the next five years  is great idea. Always remembering what you learn today may not be as relevant in five years time.</description><pubDate>Thu, 28 Feb 2013 03:22:40 GMT</pubDate><dc:creator>GRE (Gethyn Ellis)</dc:creator></item><item><title>More Evolution, More Complexity</title><link>http://www.sqlservercentral.com/Forums/Topic1424912-263-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/articles/Editorial/97294/"&gt;More Evolution, More Complexity&lt;/A&gt;[/B]</description><pubDate>Wed, 27 Feb 2013 23:07:09 GMT</pubDate><dc:creator>Steve Jones - SSC Editor</dc:creator></item></channel></rss>