4 ms·
Selling a magical pill without providing pharmacology is no different than selling snakeoil. Share your solution please, unless that part in your question is ju
by ziikutv 9y ago
Selling a magical pill without providing pharmacology is no different than selling snakeoil. Share your solution please, unless that part in your question is just a digression; (addendum) does not seem to be the case from the last paragraph.
To answer your question, it depends. Anecdotally, we created custom solution for analytics for our Robot, and then moved it in as a solution. You can think of it like 'internal-pivot'.
Additionally, in-house tools, if designed correctly, are usually small pieces of software that do just what a company needs. Tailored solutions, if effectively created, are sometimes better than something out of the box. It also lets the developers stay stimulated when there is not 'actual work' to be done and adds potential for features to be implemented for their product; if not providing with something they can pivot and sell separately.
- Sreyanth 9y ago> Selling a magical pill without providing pharmacology is no different than selling snakeoil. Agreed. I was just not sure if it was a good idea to share my solution as the answers would be mostly anlayzing the solution. I wanted to know more about the problem - and see if such a problem really exists. But briefly, here is how it works. 1. You give the schema of your DB to the tool. 2. The tool analyzes and build backend flows. 3. The user can now select which fields indicate the username, card or payment amount etc., and the flows will be adjusted for the same. 4. User can add access control to tables and fields. 5. Preview and publish, and the tool is ready to be used. Since a single tool like this cannot build tools for specific usecase, there is an option to define own actions and layouts.
- ziikutv 9y agoThat kind of sounds like an ORM no?