When I’m writing a presentation or blog post, I often start here:
It’s a photo of me in my office in Dallas, Texas in 2004. When I look at that picture, I remember everything like it was yesterday. I can talk at length about everything on the bookshelf, on my desk, in my drawers (the desk drawers, that is).
I can tell you what technology problems I was struggling with, plus what problems my manager was concerned about. I remember what I knew, and what I didn’t know yet. I can recite the web sites I frequented.
Next, I can turn the mental camera around and see exactly what’s outside my office door: my developers and my support team. I can tell you what they rocked at and what they wanted training on. I can remember how we decorated their cubes for their birthdays – covering Julian’s stuff in aluminum foil, building a princess’ castle for Hima.
The funniest thing, though, is that I didn’t remember any of this until I rediscovered this photo several years ago. All of a sudden, everything was clear to me.
And I realized who I was writing for.
Now, it’s really easy for me to scope my presentations and blog posts because I’m writing for 2004 Brent. 2004 Brent hadn’t studied databases and tried to turn them inside out – he just needed to store data and get it back out quickly. He wasn’t on a first name basis with book authors and MVPs – he didn’t even know what an MVP was.
You need to take this picture today.
Set up your camera with a self-timer or get a colleague to shoot a few pictures of yourself sitting in your work environment. Get pictures of the books on your shelf, the stuff on your desk, and maybe take a screenshot of your task list. Write yourself a one-page note covering:
- The stuff you’re comfortable with
- The stuff you’re uncomfortable with
- The things you want to learn this year
- The things you learned recently that surprised you
Stash these pictures and words away in a time capsule folder somewhere. A few years from now, when you’re writing a presentation covering something you’ve learned, get these back out. Think about what you knew and didn’t know, and that’s your target audience. Before you use a term or acronym, think back and ask, “Did 2013 Me know that? If not, lemme introduce the topic.”
When you’re writing, remember that you’re never writing for your current self. You’re writing for the past version of you. Having these pictures and words will help you define your audience.
That’s a great idea! I’ve got an old photo of me from 1999 that I run across often. I’ll have to try to write up what that me knew and didn’t know as well as doing that for today. I’ve got about 300 tech books in my basement that date to 1994. I go scan those titles every once in a while just to remember. 🙂
Good stuff as always.
Brent just a quick note. It is really frustrating when you are tying to follow best practice for sql and your boss thinks that he is right. Examples: he’s doing (shrinking all database after a rebuilt and index. he’s rebuilt all the indexes every day on a maintenance plan. Give users access directly to tables not views or functions. Anyone can create a table without knowing the deal. I have a table that has 500 columns and not a single clustered on it. System Db on the C drive. and many, many more.
Thanks for listening.
How do you deal with this.????????????????
Alejandro – well, that’s an interesting question. Our job as database administrators is to solve pain points. I can’t make everyone code everything perfectly, so I try to only focus on the areas that are causing people pain. When they complain about slow performance, we solve that together, and I show them why a certain technique can’t perform.
Otherwise, if you try to just make people change for “Best Practices”, they’ll think you’re crying wolf – because it does seem to work even when they don’t follow best practices. Hope that helps!
Brent with the ideas… I linked in to this from SQLBrit’s blog and immediately took a snapshot of me. As an official full time Junior DBA for the past 3 months I’m really looking forward to this annual snapshot. I find that as much as I try to impose Best Practices I am often overruled just as Alejandro describes. For me it’s trying to prevent the same information being in 17 tables, but “it’s how we’ve always done it…” so for now I follow the status quo. My goal is to use the status quo on existing tables, but use better planning and standards going forward. We’ll see.
My pleasure! Glad I could help inspire you, sir. Good luck on your journey!