Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

What Counts for a DBA: Being Replaceable Expand / Collapse
Author
Message
Posted Saturday, December 8, 2012 12:18 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, November 26, 2014 9:29 AM
Points: 76, Visits: 93
Comments posted to this topic are about the item What Counts for a DBA: Being Replaceable


Post #1394305
Posted Saturday, December 8, 2012 7:53 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, December 23, 2014 7:08 AM
Points: 71, Visits: 678
This is a great viewpoint. Although none of us wants to be replaced unless it's by our own choice, we also typically have enough ego that we want to be remembered in a positive light. If someone else takes over for me and their job is terribly difficult because of the way I've done things, you can bet they will complain and let everyone know that I left a mess.

Hopefully most of you can agree to this - I absolutely love most of my customers, and I don't want to leave them in a bad situation if I leave my position. Therefore, my own "job security" aside, I do try to make sure that I am replaceable.
Post #1394336
Posted Saturday, December 8, 2012 10:20 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, December 22, 2014 6:18 AM
Points: 262, Visits: 920
Another good reason to be replaceable is that you should be able to "hand off" to a coworker so you can advance within the organization. If you've built yourself into a role so completely that it would be painful to your employer to move you up, then you'll be stuck there until you retire.
Post #1394343
Posted Saturday, December 8, 2012 4:13 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 6:05 PM
Points: 35,832, Visits: 32,505
What an incredible article. I wish more people had that attitude. I've often told people that if you're indespensable in your current position, you can't get a promotion, can't get a decent night's sleep, and can't take a vacation without your laptop and phone.

And I agree with what "Dizzy" said above. It's a small world and news travels fast. If you leave someone in bad shape even just once, good luck trying to find another job in the local area.

I also don't want to leave any co-workers hanging. In one of the shops I recently worked in, I was teaching the SQL Developers and the resident DBA everything I could on every project. One of the Developers asked me why I was making myself so replaceable by teaching them so much and so many "SQL tricks and secrets". My answer was "I'm not making myself more replaceable. They can replace me at the drop of a hat... any hat. No... You're a good person and a good developer and if something happens to me, I want you to succeed whether you stay here or not. Besides, if you were to say 'I worked with Jeff Moden', I'd want you to be able to live up to that claim."

Sounds kind of corny to most but I've always said it and I live by it. "Pass it forward". The totally unexpected side effect of doing that is that it has come back a hundred fold.


--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."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1394363
Posted Saturday, December 8, 2012 7:57 PM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Tuesday, December 23, 2014 12:21 PM
Points: 755, Visits: 5,539
I agree that one should try to be "replaceable." As Jeff M pointed out, being replaceable means taking a vacation in peace, enjoying time with your friends and family in peace. The people who try to be "irreplaceable" are only hurting themselves, both in their personal and professional lives.

One of the ways to work towards being replaceable is to document *everything*, document thoroughly, and make sure others know where to find this documentation (in the filing cabinet in the basement bathroom with the "beware of tiger" sign on the wall )

Jason
Post #1394371
Posted Sunday, December 9, 2012 9:27 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, November 7, 2014 11:28 AM
Points: 1, Visits: 31
I have a couple of different thoughts:

I try to become valuable to a dept/company- not invaluable. Being invaluable means I created a position with no room to advance. Valuable means the right folks know what I do without me needing to stuff an ego with chest pounding (we all know that type :) )- that's where reviews, bonuses & raises acknowledge my work. Knowing most people last 2 years or so in a position on average, a job just preps me for the next career challenge. Keeping things in order, documented, making time to cross train keeps me replaceable. It also makes me valuable as an asset. I don't work in a silo (when an issue is resolved, "try it now" isn't good enough of an explanation). I've seen a former enterprise drop 2,500 pink slips on colleagues desks 1 week before Christmas and it stuck: We are all rereplaceable so I use a job to make me more hireable the very next day- every day and that is my focus. As my skills get better, so does my level of proficiency at the current job. Make my skills more dedesirable than the next guys.

It's a competitive thing with me: Yes, I'm replaceable but I'll make sure 1 person alone can't replace me. The last couple jobs replaced me with 2 to 2 1/4 new full timers, (2 as new hires) and that's a form of flattery especially when I cross trained my replacement and it's been established "things are in good order", "best practices are being followed"- and it still takes 2 people to replace me because of skills and proficiencies that are unique to me. That's flattery in my mind.
Post #1394400
Posted Monday, December 10, 2012 1:18 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 11:15 AM
Points: 2,926, Visits: 1,881
Mike Dougherty-384281 (12/8/2012)
Another good reason to be replaceable is that you should be able to "hand off" to a coworker so you can advance within the organization. If you've built yourself into a role so completely that it would be painful to your employer to move you up, then you'll be stuck there until you retire.


Excellent point. Not much fun watching your colleagues get all the interesting projects and training courses while you are shovelling albatross turds simply because you've gained the knowledge to stop it pecking.


LinkedIn Profile
Newbie on www.simple-talk.com
Post #1394473
Posted Monday, December 10, 2012 10:24 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, December 10, 2014 9:48 AM
Points: 199, Visits: 300
Mike Dougherty-384281 (12/8/2012)
Another good reason to be replaceable [snip]


I agree too and well said. I would point out that the Internet paradigm requires free exchange of information. If you silo your information, you are using an outmoded business model and you are on your way out. I will go so far as to say that making yourself irreplaceable by obscuring a system is unethical. Professionalism demands the opposite.
Post #1394706
Posted Monday, December 10, 2012 10:39 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 2:03 PM
Points: 1,334, Visits: 3,069
The only DBA's, or even developers for that matter, in the companies I have had experience with in the past that have become "irreplaceable' is because the company let them become that way. By allowing them constantly to not share information, to not document things they are doing, or allow them to assume the "guru' status by letting them handle everything.. If company policy, or managers, allow for this sort of thing to happen in their departments then who do they have to blame? No one person just becomes irreplaceable unless they are allowed to ascend to that position IMHO. Knowledge sharing, resource delegation, and thorough documentation practices must be enforced at a company/department policy level. Otherwise, people with will by nature try to protect their own job security.

"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ..."
Post #1394709
Posted Monday, December 10, 2012 11:08 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, December 23, 2014 1:27 PM
Points: 309, Visits: 868
As usual, Steve got me to think about an old thing in a new way.

We are all unique and irreplacable beings, and that's a good thing--except when you're responsible for someone else's data (ie, their business). In that situation, I can see that it's a lot more appropriate to consider myself a module, a replaceable unit. Might get hit by a bus, might get downsized, but it's a certainty I won't be here forever.

And in that context as a data handling professional, and whatever I build or implement, I need to ask myself "what can I do to make it easier for the next person to understand and manage this when I'm gone?"

I also agree 100% with Jeff Moden's Pay It Forward philosophy--I like to share what I know.

Knowledge is power only when you share it. If you don't share it, it's a bottleneck.


Sigerson

"No pressure, no diamonds." - Thomas Carlyle
Post #1394717
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse