Oracle switched from Waterfall development model to sprint years ago. They also switched from yearly to quarterly releases (for their Apps) which means they deliver a lot of features in a year.

They acquired the leaders in HCM (PeopleSoft) and CRM (Siebel) domains and combined them all (SCM, HCM, CRM) into a single (new) product called Fusion.

Their pitch also was - PeopleSoft and Siebel required people with different skill sets (PeopleCode for PeopleSoft, Siebel eScript for Siebel); but with Fusion, customization would not require any programming language knowledge and in the rare cases that it did, you just needed Java. This meant it was cheaper for enterprises. This was a big selling point for a lot of enterprises and helped them reduce their IT cost.

Oracle's plugin allows you access Fusion REST Endpoints (your business data) from within an Excel workbook but it only works on Windows machines and has some other limitations.

Also added a plugin for inspecting punchout payloads for RSSP [2]

[1] https://vbcs-alt.com/

[2] https://vbcs-alt.com/inspect_punchout/

Self plug here - If you aren't technical and still want to run models locally, you can try our App [1]

1] https://ai.nocommandline.com

That's actually what we've done for our own App [1]. It checks if Ollama and other dependencies are installed. No model is bundled with it. We prompt user to install a model (you pick a model, click a button and we download the model; similar if you wish to remove a model). The aim is to make it quite simple for non-technical folks to use.

1) https://ai.nocommandline.com/

I recently released an Electron App for Ollama [1] and it's nowhere close to 1GB (between 300 - 350MB). A 1GB App would be really big

1) https://ai.nocommandline.com/

1) Answering questions on Stackoverflow.

    - A few users clicked on the profile and went to our home page

    - A few of my responses involved a link to post on our blog (only did this where it was absolutely necessary)

I recently added support for Cloud Run and am now building it out. Support for Cloud Function is also on the road map.

I’m also still maintaining the patch [2] I created which allows you run App Engine Python 3 Apps with dev_appserver.py on Windows. To test App Engine bundled API/services, you need dev_appserver.py

[2] https://github.com/NoCommandLine/dev_appserver-python3-windo...

Oracle's plugin allows you access Fusion REST Endpoints (your business data) from within an Excel workbook but it only works on Windows machines and has some other limitations

[1] https://vbcs-alt.com/

E.g. I use/used Google App Engine (GAE)[1] a lot. When Google deprecated the GUI, I found it inconveniencing using the CLI. Secondly, there was no GUI for the Datastore Emulator. So, I set out to build something for both of them [2] and then decided to put it out there for others.

Along the line, it turned out that Google didn't support using one of their tools "dev_appserver.py" for building Python 3 Apps on Windows and so I also built a patch for it [3]

1) https://cloud.google.com/appengine/docs/standard

2) https://nocommandline.com

3) https://github.com/NoCommandLine/dev_appserver-python3-windo...

1) Google App Engine Standard. Datastore for DB.

2) For anything that won’t work with the above, then it’s Google Cloud Run

1) You can customize it and add your company logo/image. Can also limitedly change colors to match your branding.

2) It can be set to notify you of new submissions (ie each time someone fills it and submits it, you get an email)

3) It’s free and easy to set up.

4) You get a link which you place behind a ‘Contact Us’ text on your website. When users click it, it opens up the form.

- If you strictly made it to make money, then release it as a paid product but assume it might not make any money at all or that it will take time to make money. I believe that there's a general advice to shut down a project that doesn't make money in a very short time but some projects take awhile to gain traction. You can also use this as a learning experience in marketing/sales. Play around with the pricing over time (starting with much lower rates than you'd planned for) and see what works. You'll learn from it.

- Another option is to shut down the project entirely. You still have your code and they might come in handy when you work on other projects in the future (this has happened to me with multiple side projects)

How exactly do you go about making a chatbot a legal entity?

Comments URL: https://news.ycombinator.com/item?id=39426107

Points: 34

# Comments: 21