‘Technical Tidbits’ is a new addition to this blog comprised of mini-blogs on different technical topics. Not all of these topics will be on the introduction level; in fact, most will deal with new things I’m learning as I continue on my own technical journey. These little blogs will expose you to advanced topics. You will want to read them and tuck them away for later review. For example, you may not have a clue about parameter tables now; but when you begin your study of the DAX language, you will remember the ‘tidbit’ blog and have it to review. Think of ‘Technical Tidbits’ as little markers down the road; they’re showing you what lies ahead.
Our first ‘tidbit’ is a simple concept I wished I had employed at the beginning of my technical journey; it would have been of great help over the years. Don’t expect flashes of light and angel choirs in the background, it’s a simple little thing; it’s called a Knowledge Document.
A Knowledge document is a simple word document or spreadsheet where you record learning links and bits of code you find in your studies. In fact, I have several Knowledge Documents: one for keeping a list of training links on different topics, one for cool SQL Server Reporting Services (SSRS) expressions, another for T-SQL and Functions (Time Date, Cast/Convert, etc) for SQL Server 2012, and another one for DAX and PivotTables/Tabular with Excel 2013. There is just so much out there to know and learn; a Knowledge Document helps you to keep up with everything. There’s nothing worst that knowing there’s something you really need for your technical project, but you can’t find the link or the expression, or the function, or ……..
Creating a Knowledge Document is easy; just create a new word document or use a spreadsheet. You can insert a table or label topic areas; make the document easy for you to use, it’s for your use alone. The hard part is taking the time to record the nifty things you learn along the way. I didn’t find out about the concept of Knowledge Documents until two years into my learning; so I wasted lots of time looking for stuff over and over, because I didn’t save them in a file the first time!
Create a folder and keep all your Knowledge Documents in ONE location. It will make for an easy time when you need to locate something fast! See, I told you not to expect fireworks; this is simple common sense. I just wish I had thought about it sooner. Sigh!
Wanting to make your technical journey easier,
Susan Schneider lives in Jacksonville, Florida with her wonderful husband Steve. She enjoys sailing and is a ‘wanna be fisherman’, and loves all things BI. See more information under the ‘About Me’ section. Remember to sign up for new blog notifications: Go to Subscribe2 on the sidebar and sign up!