RE: Building Culture – SQLServerCentral

SSC Guru

Points: 1003863

February 20, 2018 at 7:04 am

#1980448

xsevensinzx - Monday, February 19, 2018 8:59 PM
On my team, I am certainly trying to build a culture centered around being open, honest, and always on the quest for more knowledge to not only improve themselves, but also help the team be smarter through knowledge sharing/transfer. I take this approach because I noticed a trend among a lot of young professionals in that if they find they are the smartest people in the room, then they should quit. I actually dislike this approach because it emphasizes that if you think that you are the smartest, then screw the team and move on. This is often a bad approach because although someone may not know something, if you take the time to show them, they often may help you discover something you did not see.
Therefore, I am focused on building a culture around the opposite as well a more open and casual environment where we can all help ourselves while also pushing the business forward together. No man or woman left behind.

Totally agree and having done it when I first started working for my current company (and previous companies), I can tell you that it works very, very well. That's a good part of why I sit with the Developers (being the old dude in the group, I also protect them from "drive by shootings" by users and managers and they seem to appreciate that, as well). We do peer reviews with a strong emphasis on mentoring and knowledge sharing during the reviews (and, yeah, I also learn), we have a WIKI of some tips and tricks as well as standards, and we occasionally have "Lunch'n'Learns". Anyone can ask anyone, including the infrastructure folks, for help or ideas. Although there are certainly centers of particular expertise (no one can know everything), there are no silos.

--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)