@PermitZIPhvac@mwmoedinger@MrLGroves@TopherNOW@RE_Deal_Junkie I partly disagree.
No question that a fine-tuned LLM deploys knowledge at scale unlike any piece of technology that came before it.
Disagree that people just needs to do their homework. User experience of the tool needs to cater to the task first. People will then follow.
@PermitZIPhvac@mwmoedinger@MrLGroves@TopherNOW@RE_Deal_Junkie My dude you misunderstand me. LLMs are a probabilistic code architecture. I'm on board that train as a way to deploy expertise through technology.
My critique is that LLMs powering chat bots are not the disruptor. It's the new technology experiences they make possible that are
@PermitZIPhvac@mwmoedinger@MrLGroves@TopherNOW@RE_Deal_Junkie I think you're a bit too focused on the technology approach here, and too little on the job and user experience a probabilistic code architecture could create.
At the end of the day though, it's humans and businesses that will stand behind estimates, so a chatbot ain't the story
Excited to announce that @Prologis has been our partner on product for @TestFitInc Industrial these past 18 months. A massive project to find market-fit in record time...the rest of the industrial ecosystem will benefit greatly!
https://t.co/qwF9t5hHMw
@Twiceroadsfool@MiketMatheny@TravisUsesRevit@autodesk There's a reason for that, although you may not agree with it -> the worksharing username needs to align with the Autodesk identity, so the change tracking in the construction cloud is always associated with a understandable name.
@TravisUsesRevit@autodesk Don't know what to tell you man. It's literally impossible to get this error state from any other reason. Chalk it up as a learning experience. Next time you get the prompt, don't throw out your unsynced work.
@dourevit@Twiceroadsfool@AutodeskRevit Yeah, I get that part. This is a just a bad error state. No way to sugar coat that. Thought you all had issues with the underlying dialog itself.