You have a really cool and impactful project, but as soon as your codebase gets bigger, and more and more contributors come into play, things can become challenging in regards to aspects like: code consistency, technical debt, refactoring, application architecture and team organization. Let's jump onboard on this journey and walk through different techniques that can help us keep our code sane and healthy for better scalability.
Disclaimer: This talk is going to be focused from a mobile standpoint but most of the practices included can also be applied to any software project under development.
MEMORIES OR TO FOLLOW UP AFTER THE TALK:
**Engineering Design Patterns:**
- There are a bunch here: https://www.tutorialspoint.com/design_pattern/design_pattern_overview.htm
- Martin Fowler -> https://martinfowler.com/ (Such a valuable source of information: browse the topics)
- Robert C. Martin
- Clean Code
- The Pragmatic Programmer
- The Gang of Four
And then any specific programming language ones. I personally do not marry to any programming language, there is no better or worse programming Language, they have all been design with a purpose in mind.
- "Use the best tool for the right job"
- "Do not do over-engineering"
- "Share and share and let other people participate. "