[Clubhouse #] Feature Name Tech Design RFC - Githubissues

tienyuan / trust-the-process

0 stars 0 forks source link

[Clubhouse #] Feature Name Tech Design RFC #2

Open tienyuan opened 4 years ago

tienyuan commented 4 years ago

Proposed Solution

Outline in enough detail for a team member to understand how you'll implement.

Please consider adding:

context, concerns that need product/design/dev clarification
examples for specific use cases, edge cases
FE: logic, states, scenes, VIP, workers, ui, libraries, tools
BE: logic, states, services, database changes, migrations, libraries, tools
performance choices
maintenance choices
flowcharts, pictures, links 🙂
what is in scope

Alternatives/Considerations

What other options have been considered? There are tradeoffs to choosing any path. Attempt to identify them here.

Please consider:

implementation cost, both in term of code size, complexity and time
the impact on maintenance, code readability
integration of this feature with other existing and planned features
cost of migrating existing codebase (is it a breaking change?)
what is not in scope

tienyuan commented 4 years ago

beans

tienyuan commented 4 years ago

beans

omg what about bananas?