Recently NotebookLM started to pop up at work as part of our Google Enterprise subscription. We have a SaaS committee that reviews tools, tries to consolidate licensing, etc – and so this was brought up more as a curiosity I guess. I saw a demo, didn’t really think much of it – maybe the demo […]
To be clear, I am not complaining about someone else’s API or IP here. I just found the Calendly APIs to be odd, and wanted to write about what I learned. I am thankful for having had the time to dig into this, getting all into Postman making this work – and having had a
This category is kind of a catch all. As I work through my Projects, Experiments and Learning I’ll be running across great articles, books, YouTube videos, or even the random interesting fact. That stuff will go here. Stay tuned!
We home schooled our children. Part of the registration is to give your home school a name – and we picked “The Mobius Academy” because it seemed cool, and a tag line like “Where learning never stops!” was even cooler. Since mobius loops never stop… Just like this comment. 🙂 So in the spirit of
I like to think I am a lifelong learner – sometimes a casual dabbler, but as I get more books, watch more videos, and learn new things at work or in my free time – well, getting hands on is the best way to learn for me. I can read something and think I get
Ok, so why was I overcomplicating things? It stemmed from three things… 1 – We weren’t sure if the app that needed to communicate with the CRM had the abilty to securely store variables. (I now know that it can). 2 – The app that needed to make the the API call had to do
Recently I needed to solve what seemed like a tiny problem, and after I was done experimenting and over complicating it – it was small. (More on the over complication in part 2). We needed an outside application to get data from our CRM, a simple lookup/return as quick as possible. That kind of ruled
