### Burger Conclusion { #burger-conclusion }

In this scenario of "fast food burgers with your crush", as there is a lot of waiting 🕙, it makes a lot more sense to have a concurrent system ⏸🔀⏯.

This is the case for most of the web applications.

Many, many users, but your server is waiting 🕙 for their not-so-good connection to send their requests.

And then waiting 🕙 again for the responses to come back.

The same way, there are many compatible tools. Including code generation tools for many languages.

## Pydantic { #pydantic }

All the data validation is performed under the hood by [Pydantic](https://docs.pydantic.dev/), so you get all the benefits from it. And you know you are in good hands.

You can use the same type declarations with `str`, `float`, `bool` and many other complex data types.

    tester.forAllPublicStaticMethods(GoodSerializableFactory.class).testSerializable();
  }

  public static final class GoodSerializableFactory {
    public static Object good(Runnable r) {
      return r;
    }

    public static Object good(AnInterface i) {
      return i;
    }

    private GoodSerializableFactory() {}
  }

  public void testSerializableOnReturnValues_bad() throws Exception {

        new Object() {
          @Subscribe
          public void eat(Object food) {
            objectEvents.add(food);
          }
        };

    List<Comparable<?>> compEvents = new ArrayList<>();
    Object compCatcher =
        new Object() {
          @Subscribe
          public void eat(Comparable<?> food) {
            compEvents.add(food);
          }
        };
    bus.register(stringCatcher);

        new Object() {
          @Subscribe
          public void eat(Object food) {
            objectEvents.add(food);
          }
        };

    List<Comparable<?>> compEvents = new ArrayList<>();
    Object compCatcher =
        new Object() {
          @Subscribe
          public void eat(Comparable<?> food) {
            compEvents.add(food);
          }
        };
    bus.register(stringCatcher);

There is a `#contributing` channel on the community Slack which you can use
to ask any questions.

## Finding issues to work on

If you are looking for good first issues, take a look at the list of [good first issues](https://github.com/gradle/gradle/labels/good%20first%20issue) that should be actionable and ready for a contribution.

To **deploy** an application means to perform the necessary steps to make it **available to the users**.

For a **web API**, it normally involves putting it in a **remote machine**, with a **server program** that provides good performance, stability, etc, so that your **users** can **access** the application efficiently and without interruptions or problems.

* Then manually fix the remaining issues in the translation, so that it is a good translation.

        "EqualsGetClass", // Let's agree if we want to adopt Error Prone's idea of valid equals()
        "JdkObsolete", // Most of the checks are good, but we do not want to replace all LinkedLists without a good reason

        // NEVER
        "AssignmentExpression", // Not using it is more a matter of taste.

        suggester.indexer().addBadWord("bad", false);

        SuggestItem[] items = new SuggestItem[3];

        // Good item
        String[][] readings1 = new String[1][];
        readings1[0] = new String[] { "good" };
        items[0] = new SuggestItem(new String[] { "good" }, readings1, new String[] { "content" }, 1, 0, -1, new String[] { "tag1" },