@DevinKunysz One major problem with CRM implementations is that they rarely have value for the individual who has to use it. The implementation is focused on a tool to manage a process. So, IC’s input as little data as required, and or low value data
The #TartanArmy has a few new marching members!
🦆🏴
If you know about the ducks in Boston then you get it.
Complete with mini traffic cones and all 😂
Little dude asking the hotel staff where he can buy dinosaur bones to the embarrassment of his sister was the highlight of my morning.
Keep asking. Be 'cringe'. Never be embarrassed. You will not get what you want otherwise.
The future of analytics engineering is...
Building the agentic context for your company's data — whether that's a semantic layer or a more sophisticated ontology
Evals — analytics teams have the agency and depth on their data models to know what “ground truth” looks like
Automation — reports are no longer the end state. The next step is systems that explain what changed, recommend what to do, and eventually take action
Please understand this will be the single biggest driver of job security for data teams since they now will have infinity tickets titled “Why doesn’t revenue align between these two dashboards?”
@DevinKunysz@matt_slotnick@james406 Actually, each penguin might have their own CRM & you may have to integrate multiple CRMs because they mate for life
@matt_slotnick@theinformation DBRX uses OAI as part of Agent Bricks. OAI is a DBRX customer. DBRX provided access to OAI to their customers. One advantage of using DBRX to serve OAI is that it counted against discounts & commit agreements. For customers, it’s cheaper
@matt_slotnick One thing, RBC has an agent based on Databricks for earnings release calls. The agent captures details & writes a summary with a 15 minute lag after the call
@McCainJack Use a fresh turkey if you have freezer space, take some of the cooked turkey , cryovac it & freeze for later. I also do the same with smoked pulled chicken