semyonsh
Joined 7 years ago
Joined 7 years ago
Advising to homebrew everything with an LLM just sounds insane to me. Cognitive overhead of what? Using well thought out and standardized libraries that have proper documentation? Creating a new engine with an LLM is only going to achieve the opposite of fully understanding your codebase.
The real challenge of a Cloud exit is undoing the years of gradually getting vendor locked-in. Not only do you use the services it provides, the software you might have written also uses the SDK's, is tightly coupled etc. I'm not even taking IAM into account, which is vertically integrated everywhere, in the equation.
And this isn't only on a technical level but also organizational. So i'm out of the cloud, my staff still doesn't know anything about managing dedicated servers and other solutions. I'm now fully dependent on a firm which main focus is doing migrations? How would that work?
What kind of business is your target audience here?
It had one feature that's maybe essential and that I'm missing here, and that is being able to share the app and data with your partner so both are in control of monitoring, maybe I'm overlooking it but I can imagine that's hard to integrate with a PWA that does not use accounts.
One last thing: "no accounts", but filling in the email field is mandatory, i'd skip that.
Nice job!
Does it use some client, what do I need to install on my devices (if supported) and what permissions does it need etc? Instead I'm greeted by a login page.
It's not transparent enough for me how the product is used before signing up and that's a huge turn off.
[1] - http://www-cs-students.stanford.edu/~amitp/Articles/SRE-Docu...