Its a pain in da arse to support brotli decoding in Ruby (not sure about other languages) so when I send http requests, i just omit it in the request headers
1. How does it know how/when to reschedule that doctor's appointment that you need to call to reschedule? How do you know that receptionist won't hang up on your "AI agent" who tries to call them, b/c they think it's some sort of scam bot?
2. How does it know which contacts to contact? Does that acquaintance you talked to for some professional reason need to know your flight got rescheduled? What about that travel agency you talked to last night to confirm the flight?
I would say the problem there is the requirement to phone a human to change a record in their database.
If they had an app then an AI assistant should be able to tie things together. Where things seem to be going is apps provide an intent-based API wrapper plus UI widgets to interact with it. That way assistants can operate them too.
That, and when people ask me about my problems, i tell them about it. But then i realize they want to know about problems that have a scalable or easy solution they can build.
In other words, I gave them my damn problem but they arent interested in solving them.
So no, i aint talking to you about my problems anymore
Exactly, if you are waiting to make something that very very few ppl are doing, you will be waiting a lifetime. That or the market is extremely small to be profitable.
As my old business mentor often said: if nobody else is doing a thing, there's very likely a reason why. Learn what that reason is before you start doing it.
Throwing away old code and rewriting it in a sexy, new language also takes time away from projects that are actually meaningfully innovative: ie projects that help customers do more, or be more efficient