<aside> <img src="/icons/info-alternate_purple.svg" alt="/icons/info-alternate_purple.svg" width="40px" /> This page has the objective of collecting all the lessons learned of the recent Nu<>Keep collaboration for the Threshold FE in the form of a retrospective

</aside>

What went well

• Required functionality was added! 🎉
• Only one small hotfix was required - it was non-breaking, just an issue in some dynamically generated info
• Release cycle went well, no major blockers

What didn’t go so well

• Development took too long due to unfamiliarity with codebase and lack of experience with tech stack
• Whilst minimal viable functionality was shipped, several pieces (required for future) where skipped due to time
• Issues with setting up a dev environment, although this has improved greatly
• Changes on main or external libraries would cause previously working code to error, without explanation

Things to improve for the next time

• Get Keep involved from the very beginning 😀
  • an introduction to the codebase, architecture, tech stack, deploy/release etc - we should probably document some of this too
  • Nucypher provide an outline of required features, and an implementation plan is developed with Keep team - they will know which bits will be tricky and which areas of the codebase are brittle
• Shorter development and review cycle. The overall task should’ve been broken into smaller pieces to make testing and reviewing easier for everyone. This links to the above plan. Testing needs to come from both teams to ensure we don’t break each others stuff.
• Dedicated time booked in advance with the Keep team. Michal was amazing, and when he got involved development leapt forward because he was able to fix issues much faster than Nucypher team.
• Better communication when changes made to external dependencies or underlying main branch might have knock-on effects for in-progress dev work