IOTA Development Patterns

[muellae]

Goal Title

Priority: () There are already quite a lot use case description of what can be done with IOTA. What's missing is the intermediate description and patterns on how to actually solve more complex problems. The basic course about how to send/receive funds and data is very low level. It would be great to have a set of patterns on how to tackle different task.

Key results

1. • Set of basic development patterns
2. • How can these pattern be combined to get to the next level
3. • Best practices, tipps an tricks, cheat sheet

Team

IOTA Experience Team ?

Contributors

X-Team members

@githubusername - Name Surname - thisis@myema.il

IOTA Foundation member

@githubusername - Name Surname - thisis@iota.org

Additional Information

• link to project
• link to documentation
• link to repository
• link

Governance

Please use the following emoji reactions in this post to indicate: :+1: - Participating :heavy_plus_sign: - Add my vote

[jlvandenhout]

I really like this idea. Like in development you have different kinds of testing, like unit tests, component tests and integration tests, you could have different kinds of examples. For example you could have:

• Usage examples: These examples answer user questions like: "How would I do ...?" or "What does ... do?" You could forward users to these examples to get a feeling of what the community thinks to be best practices using a specific library.
• Integration examples: These examples answer user questions like: "Is it possible to do ...?" or "Could you give an example how to use ... together with ...?" You could forward users to these examples to get a feeling of where the library fits in the bigger picture or provide a starting point that is similar to the use case the user has in mind.