← Back to Blog

Weekly Project Update #2

The one where I write my project proposal

2 min read • BD Tinsley

Overview

The project proposal for decx.press was a big step towards creating a plan for the semester. It was a way to set clear goals for myself and to communicate with the decx.press team about what I need from them. They were very helpful in reviewing my proposal and providing feedback. We also discussed that it would be helpful to have a knowledge repository for the project. It's something I won't let creep the scope of the project, but it will be important as a first pass of documentation, motivation and best practices for the project.

Last Week

What I Said I'd Do

  • Create and post my project proposal
  • Review at least 2 classmates' project proposals
  • Share my project proposal with the decx.press team and articulate what I need from them

Additional Accomplishments

Next Week

  • Refactor Solidity contracts for handling character-to-hash contracts and hashes-to-hash contracts
  • 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

Blockers

None! Let's get going.

Reflections on Process

This week I added a What I Said I'd Do subsection to my Last Week section as a way to remind myself if I'm accomplishing the things I said I'd do. I'd like to continue this practice for the rest of the semester. Otherwise, this week was still a lot of planning and not a lot of actual working. Next week, I'll have a better idea if the plan I set for myself is realistic and if there are changes to the process I need to make.