More Evolution, More Complexity

Question

More Evolution, More Complexity

Steve Jones - SSC Editor

SSC Guru

Points: 736270
More actions
February 27, 2013 at 11:07 pm

#271726

Comments posted to this topic are about the item More Evolution, More Complexity

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

GRE (Gethyn Ellis) SSCrazy Eights Points: 9602 More actions · Answer 1

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.

Gethyn Elliswww.gethynellis.com

Gary Varga SSC Guru Points: 82166 More actions · Answer 2

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 😉

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!

batgirl SSCarpal Tunnel Points: 4979 More actions · Answer 3

Gary Varga (2/28/2013)
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 😉

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!

Steve Jones - SSC Editor SSC Guru Points: 736270 More actions · Answer 4

batgirl (2/28/2013)
This really speaks to me today.

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.

David Conn SSCertifiable Points: 6010 More actions · Answer 5

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 badly

David

Jeff Moden SSC Guru Points: 1004363 More actions · Answer 6

I think that a lot of people grossly confuse the words "change" and "improvement".

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Gary Varga SSC Guru Points: 82166 More actions · Answer 7

Jeff Moden (3/8/2013)
I think that a lot of people grossly confuse the words "change" and "improvement".

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.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!