Overview
I've spent a considerable amount of time this week ensuring that I can relate to the team members on the project and ensure I'm setting them up for success when they want to work on the project. I was able to finally put fingers to code and pair with Noah and Carlos to refactor the Character2Hash and HashRegistry contracts. I've also set up a few recurring events to help the team find an optimal flow despite all of our busy schedules.
Last Week
What I Said I'd Do
- Refactor Solidity contracts for handling character-to-hash contracts and hashes-to-hash contracts (hashes-to-hash contract refactoring is not yet implemented)
- Integrate a Hash Registry to handle deduplication across units
- Add a Technical Architecture section to the wiki, with a basic "Glossary of Terms" and "Technical Decisions" sub-sections
- Attend the Slambox talk
Additional Accomplishments
- Added a Working on decx.press section to the wiki
- Added a Git Flow Guidelines section to the wiki
- Paired with team members (Noah & Carlos) to refactor the Character2Hash and HashRegistry contracts #17
- Better incorporated team members into the project (Carlos), allowing him to take specific refactoring task for hashes-to-hash contracts #18
-
Set up a few recurring terminal events over the next month to help the team have more opportunities to work together and review each other's code:
- PR Mondays: Every Monday, team members will commit to reviewing any open PRs (Feb 10th, Feb 17th, Feb 24th, Mar 3rd)
- Open Hours: Every Friday, we will have an open Zoom call to chat about the project, pair program, or have unstructured conversations (Feb 7th, Feb 14th, Feb 21st, Feb 28th)
- First Sunday Retrospective: In place of our usual Sunday team call, we will have a retrospective on the first Sunday of the month to reflect on the process of the past month and keep things that are working and drop things that are not. (March 2nd)
Next Week
- Ensure hashes-to-hash contract refactoring is complete #18
- Merge any outstanding PRs
- Build out the DecxDAG logic to handle the process of converting a string into a single representative hash #21
- Deploy the built contracts to a testnet
- Plan how the API will work, what endpoints and methods it will have, and which tools I should use to implement it
Blockers
I'm happy Carlos took on the hashes-to-hash contract refactoring and trusting him to accomplish the task. Getting more members involved in the project is great, but I anticipate it will cause some initial slowdowns. In the long run, I know it will pay off.
Reflections on Process
I'm curious to see how the events I set up will go. I think they will help the team get more comfortable with the project and each other. But I'm also aware that I need to be careful not to overwhelm the team with too many events. This is why I'm only committing a trial phase of 4 events and then automatically ending them by default, that way they can die quietly versus needing a conversation.