Consulting Lines

[theDirector]

I don't currently consult, but when I did along with "I'm not going to write this down, " if I'm getting friction from the local DBAs who are frequently very good, I ask to speak to them in a private call and say, "I'm not here to take your job. I already have one." I frequently came across DBAs who were infuriated that a fresh set of eyes was brought in to look at an issue. I try to let folks know that I have a dozen peers on speed dial to give a second look. None of us are infallible.

[error.]

The first bit is also kinda about the xy problem, client wants to solve problem x, but is asking about how to do solution y which they've determined is the way to solve x, but they didn't bring up x to you. And it's possible that to solve x you want to consider z, etc. But you can't dig in to that until you get past looking at solution y and get to the root problem x. One way to get this uncovered is, when they first introduce their problem, determine if it's a predetermined solution to some root problem by asking, "why do you want to do this?" Or in the more consulting style, "how will solving this problem best help the company? let's make sure we're on the best path." or other suggestions would be great.

[grhodes]

Are you open to discussing alternative solutions? If not, sounds like you have this problem all figured out and I'm just slowing you down. I propose we move on to the next problem where I might be able to help.

[trud]

Great advice. Do you often implement the PROD changes by yourself, or do you want someone from the client side to do so? If it is someone from the client side, how do you control that they implement it properly?

[mortezasafaee]

Brent is on the darling data road with adidas tshirt😂 like erik sign the contract with adidas🎉