March 25, 2015 at 12:00 am
Comments posted to this topic are about the item Mastery – Repetition, Variations, and Depth
March 25, 2015 at 3:06 am
I totally agree with this editorial. My blog (don't rush it is not exciting at all ;-)) is comprised of one vendor issue and a handful, at most, of solutions to issues for which I could not find another source of information.
As for mastery, one can only consider themselves to be a master if they have a deep comprehension of the tools, techniques and materials used. My opinion is that the materials of the knowledge worker (read DBAs and programmers) are data and code. Deep comprehension is only achieved through study and the repetition of practice.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
March 25, 2015 at 3:16 am
I agree and last year started a SharePoint Wiki where we can put such nuggets of information about the tools of our trade (SQLServer including SSIS, SSAS and SSRS , Visual Studio, Team Foundation Server, Windows 7 etc.) This has proved invaluable especially when I have to sort out TFS when a user changes to a new pc.
March 25, 2015 at 6:30 am
I agree too. Maybe it's a few notes somewhere, or perhaps saving some sql code you used. I save all the sql I write every day in a file titled with the date YYMMDD.sql so if I have to repeat something I know I did six months ago I can find it.
March 25, 2015 at 6:35 am
P Jones (3/25/2015)
I agree and last year started a SharePoint Wiki where we can put such nuggets of information about the tools of our trade (SQLServer including SSIS, SSAS and SSRS , Visual Studio, Team Foundation Server, Windows 7 etc.) This has proved invaluable especially when I have to sort out TFS when a user changes to a new pc.
We keep talking about starting a Wiki here at work in IT but never seem to get around to it.
March 25, 2015 at 6:51 am
As someone who has mastered GIS (Geographic Information Systems) and can do all facets blindfolded, BUT has only just begun my deep journey into the SQL Server world 2 years ago I found this article comforting. The SQL world is deep and complex and in the GIS world we have people called SDE Admins (Spatial Data Admins) who's job is to be SQL gurus as well as GIS Data gurus and make them sing and dance together. Not an easy task.
I started as a cartographer just reading the data and making maps. I have now worked my way "backwards" towards enterprise solutions with GIS as my strong point. I took notes on all those rare GIS things for installation and how I had to configure that on top of SQL Server 2012.
I now am moving towards ArcServer 10.3 & Spotfire Server 7.0 all built on a SQL Server 2014 R2 & Windows Server 2012 R2. I am hoping my notes from 2 years ago doing ArcServer 10.1, SQL 2012, and Windows 2008 R2 serve me well, but I am sure there will be new hurdles and software changes that will just stump me and make me feel all alone as I get these software's to talk properly. I'll keep this article in mind that even well versed SQL gurus have the same hurdles that "newbies" like me have when setting up systems every once in a blue moon.
March 25, 2015 at 6:57 am
Gary - added your blog to my list, had missed it. Maybe add it to your signature?
March 25, 2015 at 7:02 am
Wikis are tough. Several years ago I found a group of volunteers to do the initial build of http://wiki.sqlsaturday.com/. Over a weekend we tried to write up all the basic topics and in the process figure out how to use it, how to organize it, etc. Getting the granularity right takes practice. Making it easy to navigate requires some effort. I think making the initial investment is something you can get a team to do. The hardest part is ingraining it into the culture so that it's used as a reference AND it gets updated. The SQLSat wiki still lives and that's good. I learned a lot from the effort.
March 25, 2015 at 7:02 am
Bornready - those are blog posts just waiting to be posted!
March 25, 2015 at 7:03 am
Andy Warren (3/25/2015)
Gary - added your blog to my list, had missed it. Maybe add it to your signature?
Thanks Andy. As for my signature, I thought that adding a link to my blog would just be a duplicate of the "Blog" button under each of my posts. I guess it is easy to miss though.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
March 25, 2015 at 7:04 am
Obviously I did miss it! So much for mastering the details on a Wed morning!
March 25, 2015 at 7:06 am
dkennard - Thanks for the comments, I'm glad it helped. It took me a while to learn, but most of us have the same challenges and the same fears. Fewer of us figure out the patterns that move us up a notch. I like to think a lot of what happens here at SSC is about sharing the ideas and the patterns.
March 25, 2015 at 7:09 am
SharePoint has a Wiki feature, if you want to create something that visible within your team or organization.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 25, 2015 at 9:15 am
I totally agree with that last idea about the blog. I started one about four months ago as a way to learn more, inform potential employers about my knowledge level, post interesting solutions, and most importantly, find a way to link my passion for database administration with my passion for fishing :-D. It's been a fun experience and I hope I continue to have time to do it as my career progressing and my skill level improves.
March 25, 2015 at 9:18 am
When you do something new or solve an interesting problem, write it down. Blog if you have one, but if not just write the steps in Word or Evernote or whatever it is you use.
In my world, they're usually in the form of comments in the body of, or reposed with, the relevant application code. GitHub[/url] particularly offers extensive commenting capabilities.
Viewing 15 posts - 1 through 15 (of 27 total)
You must be logged in to reply to this topic. Login to reply