馃煠 Source Code Performance Round Table: Catch-all discussions
What is this?
This is an issue created to catch all generic discussions about Performance before they crystallise into specific issues.
Agenda
Find the agendas for our weekly meetings here (internal company link): Agenda
What are the active topics being discussed?
The issues in column workflowrefinement are actively being discussed and still haven't forked into specific tasks being scheduled, yet.
What do I need to do?
-
Do you have a formal proposal for a topic to be discussed? Open an issue with ~"Performance Round Tables::Source Code" + workflowrefinement
-
If you don't have a formal proposal but would like to have a quick discussion or ask a question, drop it in the comments of this issue, please.
Goal
This issue and sessions are targeted at everyone in the Source Code group: Backend engineers, Frontend engineers, Product Manager, Designers.
We look to identify potential performance work that will bring performance improvements through these discussions.
Some ideas:
- incremental innovations: small steps we can take to improve performance of our apps/pages.
- radical innovations: large projects that bring technological innovations to improve performance of our apps/pages.
- open questions: have we tried X or Y? Maybe you heard someone mention this new approach and you think it might apply to making our apps faster
- problems that need solving: it's important that we keep our eyes on the users' perspective and what problems need solving. identifying them properly is half the victory.
Questions?
Feel free to ask in #g_create_source-code