@rsoesemann@SalesforceDevs@partnerforce Haha true. It’s only been a month since the zoomin acquisition. Probably reworking their approach to unstructured data integrating tech from zoomin ?
@WadeWegner@Ubiquiti For the exact same reasons I ditched my Unifi and moved to Netgear Orbi.
For a wireless kit, they are pretty awesome (albeit pricey)
I believe that Intelligence becoming commodity is true but it will still need intelligent humans interacting with intelligent systems to make the world work. Humans with low IQ will still struggle because they will simply not understand what’s the AI is doing!
#ArtificialIntelligence#AGI
It’s all well and good to have AGI but how accessible will it be. Today there are cars capable of going over 250mph but not many people have the skills to use them or afford them!
and to continue with the cars analogy, we put speed limits on roads so as to not harm fellow humans and ourselves. Will there be an intelligence limit lol
IQ, EQ and their correlation to success is well documented.
The ability to communicate with machines and get the best out of them lies somewhere in-between IQ and EQ. We should perhaps call it AIQ ?
@AidanHarding@bt_uk@BTSopenreach Never heard anyone say anything nice about BT. Congratulations!
Generally speaking I think you have better odds of winning the lottery compared to experiencing great service from BT.
#Salesforce#summer23 release breaking change
If you find that your new scratch orgs are messed up after Summer23, note that our friends have made yet another breaking change to the scratch defn file. You need this change:
@rsoesemann@RobSalesforce@karenfidelak@AndrewDavis_io At the heart of the problem is a monolith target production org that actually masters metadata and code in a stateful relational database.
We can all pretend that Git is the source of truth but in reality the stateful production org is the real master.
@rsoesemann It simply boils down to the quality of resources probably. The people who take on lower paid support roles are probably the ones who don’t want to (or not able to) do delivery roles.
@michaelforce @dhoechst @sfdcjames@leesto You’d have to do it in the in-memory Quote model before you save and delegate to the calculator API. No DML involved.
Note that dates are hierarchical so you typically set it at a Quote level but can override any individual lines .
@michaelforce yeah it is still dangerous with POT pricing, parent child relationships, pricing that has dependencies to things on that particular quote etc etc
@michaelforce Having said that, the API itself is terribly designed. It is stateful and not idempotent. If you aren’t careful your leave the data in an absolute mess.
@michaelforce It is asking for trouble. It is akin to writing to the database when there is a whole business logic layer built to write it in a consistent and compliant manner.