2 ms·
(we assume) that everyone knows distributed/federated systems are a good design goal Do they? Are they? Maybe you need to check if anyone else in this industry
by egypturnash 5y ago
(we assume) that everyone knows distributed/federated systems are a good design goal
Do they? Are they? Maybe you need to check if anyone else in this industry thinks this. If they don’t then you have to convince them that it’s a good idea, AND that your product is the solution to it.
You say “many of the vendors have APIs”; will switching to your product solve the problem of interfacing with them? Is this a problem anyone is having? Perhaps you can push adoption of your own API by making a product that talks to all these different closed APIs on the back end, and only requires its users to learn your API to talk with all of them.
Perhaps you should read the history of email. Wikipedia’s article on it starts by noting that it took fifty years for the current suite of smtp/pop/imap to become the standard. https://en.wikipedia.org/wiki/History_of_email https://en.wikipedia.org/wiki/History_of_email
- openthc 5y ago> took fifty years oh shit. edit: we also made this: https://github.com/openthc/bong https://github.com/openthc/bong - Basic Object Normalization Gateway -- but it's like "draft" quality.
- egypturnash 5y agoYeah, sorry. Really looking at your other answers: the industry does seem to be realizing it needs your unified API, and you’re in there getting hired to implement it. You are doing the work, and the only real problem is that you think it should take a lot less than fifty years. If you take email as a model, your future career path probably includes forming a weed standards organization, issuing a lot of weed standards RFCs, and helping people implement them.
- sgammon 5y agosomething like this? https://github.com/CookiesCo/OpenCannabis/blob/dev/rfc/7/README.md https://github.com/CookiesCo/OpenCannabis/blob/dev/rfc/7/REA... lol