PVB Refactor Communication Protocols | Voters

PVB Refactor Communication Protocols

Michael Reeves

The Idea behind this technical debt is that, we (dev team) would want to make the way we communicate between different processes in the PV10 code less cumbersome to update and easier to understand from newer developers we have in the near future.

July 18, 2023

Mairin Jerse

marked this post as

open

Mairin Jerse

marked this post as

planned

Mairin Jerse

marked this post as

revisit 2024

Planned for 2024

Mairin Jerse

marked this post as

revisit q4

Mairin Jerse

Thanks Mike - I can mark this one as something we revisit in Q4. 
Do you have an idea of effort we're looking at? Would this involve one developer / all devs, multiple sprints? 
If you can estimate, do you have an idea of the impact of refactoring PV10? Time saved, bugs reduced, etc.
Thank you!  🚀

Michael Reeves

Mairin Jerse: Mairin, Im thinking this is easily 5+ points and I think 1 sprint is required. 
Id have to investigate a little more how the work can be split up, but I guess we can revisit that in Q4.
The main impact this change will have is the increased expandability of the PV10 platform, time saved, and hopefully it can help reduce bugs but not counting on it.

Mairin Jerse

Michael Reeves: That's helpful - thanks Mike! Given that it seems low effort / high impact, I'm down to refine this in Q4 and then get it slotted for a sprint

Todd Price

This is one I'd like to see us get in during Q4. We had a much more ambitious refactor of PV10 planned which we had been calling "PV10+", but this would be the single best incremental change that will help future developers be more productive while developing on PV10.