Tech Talk with Toni

  A missing tooth: that's not good (or is it?). Today's topic is inspired by a problem that one of my coworkers brought to my attention, and I think this is also something many people face on a day-to-day basis. As data professionals, we have all encountered datasets that contain fields with no data, which can be frustrating when building reports or machine learning models. Since we all know that a perfect dataset does not exist in the real world, the next best thing to do would be to have a game plan in place to tackle the inevitable. When posed with the question, "Toni, how should I go about solving this?" the first word that comes to mind is context. You see, just because something is missing doesn't mean it needs to be "fixed" for example, knowing why a tooth a missing is important before acting.  A 6-year old with a missing tooth doesn't require a filling.  With that being said, here is a strategy for dealing with the unknown: Why is the data no

  Price tags provide metadata about the product they are attached to. The "meta-" part of metadata means "beyond" or "transcending." So, metadata is like extra information that goes beyond the main data. For example, think about your name, personality type, height, and weight.  These are all things that help people know more about you. Here's an example some of my metadata: Name: Toni-Marie Noel Personality Type: ENTJ Height: 5 feet 6 inches (167.64 cm) Weight: 129 pounds (58.51 kg) Favorite Pastry: Currants Roll  I first heard about metadata at work, and it's becoming a really important aspect of my role. But why is metadata important in the first place? Searchability Imagine searching for George Orwell's 'Animal Farm' in a library filled with books lacking labels on their covers. A nightmare, I know! That's why I actually judge books by their cover. Search Engine Optimization  Utilizing the correct keywords can lead to a stagge

  When I think of Reporting, I think of the news.  Throughout my career in Technology, I have encountered two Microsoft products, Power BI and SQL Server Reporting Services (SSRS), both designed to serve the same purpose: Reporting.  Today, I decided to delve into their origins and explore their respective strengths and weaknesses. A Brief History on SSRS  If you were to ask me, "What is SSRS?" before my current job, I'd probably just stare blankly and shrug my shoulders. However, now I can confidently tell you that SSRS stands for SQL Server Reporting Services. Here's a fun fact: It started in 2004 as an add-on for SQL Server 2000. People really liked it because it could work with all sorts of data, such as tables from SQL Server databases, Excel, and XML files. And you know what's interesting? Even after all these years, people are still using it. SSRS Strengths SSRS is better suited for generating paginated reports, such as invoices and statements. Report subs

  "The best way to find yourself is to lose yourself in the service of others." - Mahatma Gandhi I began my career by engaging with external customers over the phone. It always started with introducing myself, stating my location, and the purpose of the call, all of which were recorded for quality assurance.  It would often go something like :  "Hi, my name is Toni-Marie and I am calling from Mars, I would like to speak to Mr. Salad Fingers"   I said that phrase so often that I would automatically say it, even when placing an order at Mario's: "Hi, my name is Toni-Marie and I would like to order a Chicken Picante Sandwich"  As part of the Technology Department, I now serve internal customers, and although these individuals work at the same place, I still believe that there needs to be a sense of urgency and respect when dealing with them.  Their perception of the Technology Department can impact the overall performance of the company.  If they do not t