if there are any gaps in our usage of of AI right now, it's application gap
This is how I feel too. Everything I haven't automated yet is because I haven't developed the framework for automating it yet. Most often because I just haven't gotten to it and there are many cases where it's not rewarding enough versus what else is open: there is lower hanging fruit. [1]
the very end of that is that they can build their own features and build their own visualizations on top of our capabilities through our interfaces.
API-first. This is what I personally love to hear, because it shows what I've seen, and not some Huang LARP bullcrap where AI is using your browser and other GUI apps[2]. That's just inefficiency to work around the software industry largely not thinking in standalone programmatic interfaces to deliver functionality previously. And in banking it's particularly bad if you're looking for easy integrations, even after a decade of mandatory PSD2 APIs in Europe, it's very hard to find good APIs that are easy to onboard. So from a tech p.o.v., I think this is the right move.
Instead of our customers coming to our intelligence systems and knowing what question to ask and what to prompt the AI, we can actually prompt our customers and we can do it in the right time so that they can have an experience where they have an intelligent system that is looking to protect their business and to protect their individual finances and help them along whatever goals they might have.
This feels somewhat dangerous in the face of Third Party Doctrine. Having a conversation with a third party about your finances while we see police states expanding rapidly - without any respect for the individual and their privacy - while maximizing their intelligence towards political goals, is a self-own. So this may become (or perhaps already is) a massive honeypot. This worries me, but not the most.
I don't think we're early to this realization. I think most companies are late. Within the next year, I believe the majority of companies will reach the same conclusion and make similar structural changes.
Structurally, this would mean a massive unemployment problem if it really all happens within a year. I'm having trouble this morning to apply Let no good crisis go to waste towards this. But that's what's most needed now: How can we avoid UBI?
PS:
What gives you guys the right to win here?
This is such a sad fucking question that it made me laugh
Funnily though, automated money management carries the least priority for me, which is the entire functional area that Jack is serving, but this is also because I largely operate outside of compliance regimes (which I suspect is going to bite me hard when you're all on UBI and I'm out there not getting any work either, and no UBI, but I guess I just have to work harder now and conquer my part of the world before retiring. tick tock.) ↩
Post-2005, every (huge) commercial system I've designed has been API-first and API-foremost, and focused on simplicity of integration and extendability. This has hurt some stakeholder confidence in the past because they wanted to see slick apps and websites first, which were of lesser concern during foundational systems development, but those that accepted the vision of doing API really well to prepare for the future are now up to 2 decades ahead over the laggards. ↩
This is how I feel too. Everything I haven't automated yet is because I haven't developed the framework for automating it yet. Most often because I just haven't gotten to it and there are many cases where it's not rewarding enough versus what else is open: there is lower hanging fruit. [1]
API-first. This is what I personally love to hear, because it shows what I've seen, and not some Huang LARP bullcrap where AI is using your browser and other GUI apps[2]. That's just inefficiency to work around the software industry largely not thinking in standalone programmatic interfaces to deliver functionality previously. And in banking it's particularly bad if you're looking for easy integrations, even after a decade of mandatory PSD2 APIs in Europe, it's very hard to find good APIs that are easy to onboard. So from a tech p.o.v., I think this is the right move.
This feels somewhat dangerous in the face of Third Party Doctrine. Having a conversation with a third party about your finances while we see police states expanding rapidly - without any respect for the individual and their privacy - while maximizing their intelligence towards political goals, is a self-own. So this may become (or perhaps already is) a massive honeypot. This worries me, but not the most.
Structurally, this would mean a massive unemployment problem if it really all happens within a year. I'm having trouble this morning to apply
Let no good crisis go to wastetowards this. But that's what's most needed now: How can we avoid UBI?PS:
This is such a sad fucking question that it made me laugh
Funnily though, automated money management carries the least priority for me, which is the entire functional area that Jack is serving, but this is also because I largely operate outside of compliance regimes (which I suspect is going to bite me hard when you're all on UBI and I'm out there not getting any work either, and no UBI, but I guess I just have to work harder now and conquer my part of the world before retiring. tick tock.) ↩
Post-2005, every (huge) commercial system I've designed has been API-first and API-foremost, and focused on simplicity of integration and extendability. This has hurt some stakeholder confidence in the past because they wanted to see slick apps and websites first, which were of lesser concern during foundational systems development, but those that accepted the vision of doing API really well to prepare for the future are now up to 2 decades ahead over the laggards. ↩