527 karma · joined May 8, 2011
If I take the example: ""what is the probability that a nurse is {GENDER}", I could argue that saying that, let's say, a nurse is 80% likely to be a woman, is a bias that just reflects the reality.
Therefore, in some scenarios, this could be fine. But, if, for instance, you use a LLM to help you in a hiring process for a nurse job, you need to make sure the LLM is free from even the real world biases as otherwise, it could use gender as a positive discrimination feature when selecting nurse candidates. And this is just illegal
- Some more details on the building (and challenges) of the leaderboard https://livablesoftware.com/biases-llm-leaderboard/
- The tests used in the backend: https://github.com/SOM-Research/LangBiTe
Or for a graphical online UML editor (https://modeling-languages.com/web-based-modeling-tools-uml-...)?
If the former, then plantUML is my favourite. If the latter, there quite a few options but one that's easy and fast is http://www.umletino.com/
I'm not sure this is also the case when we're talking about business/non-tech users
But in a "brilliant marketing twist" (that we should learn from) they focus on the message on something developers will 1 - better understand and 2 - feel more familiar to them.
It's much easier to understand the concept of low-code (I still code if I want but less) than something more abstract as "model-driven development"
Clearly, in the above example, you didn't provide what the bot was expecting and since the bot is a research prototype, it had not enough training to identify that you were not providing an API file but asking a clarification question.
No, the bot owner should the dashboard to realize that a user (you) asked this question that made the bot failed and should prepare a new version of the bot that can answer it
Then Xatkit aims to be a very flexible platform that helps you create chatbots on top of any platform you need, more than a concrete solution for a specific set of technologies. For instance, most current solutions are tied to a specific NLU Engine (being DialogFlow, IBM Watson or whatever). Xatkit tries to abstract from the concrete engine and let you define the bot in a more abstract way and deploy the bot on any of them based on your deployment preferences.
(this doesn't mean Xatkit provides right now all the connectors you may want, it just means that the architecture of Xatkit was especially designed with this goal in mind, it's open source so it's possible for you to create whatever you need)
It's true the one in our home page is a bot to illustrate a simple scenario with some of the features that Xatkit includes (if you ask the bot for a demo)
Also, for small companies, it may be the only option as they cannot be available 24/7.
Mostly, right now (IMHO) you can only get some success translating very short pieces of code.
We used LSTMs for that (which seems to be the more usual approach in this domain)
But the key to benefiting from UML is to first decide what subset of the whole language you need and focus only on that. Very few companies will find a use for the 13 types of UML diagrams.
We could have elections and let elected experts to act unsupervised for a period of time, use liquid democracy (where you delegate your vote when you're not involved in a certain decision),...