Overview
Last week, I met with Prof. Guinn and other members of the class in CU's CSPB 3112 Professional Development course to discuss our prospective projects. I discussed the history and intention of decx.press as well as work done thus far. One of the main takeaways from the meeting is that given what the goals of decx.press are, it may be difficult to isolate the scope of what I can get done in the next 14 weeks. Prof. Guinn mentioned that this is a project that could worked on for years, so making sure I set clear milestones in the project proposal for myself will be important.
Last Week
- Met with Prof. Guinn and other members of the class to discuss our projects
- Diagrammed a Merkle Tree reduction algorithm for storing content
Next Week
- 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
Blockers
As decx.press is a team project, the main challenge I'm facing is getting everyone to contribute to the project, even in minor ways like reviewing PRs or showing up to meetings consistently. But these are minor issues, and I know that this is an issue that can be solved with my own communication and organization skills. I think a way to solve this is to show the team what I hope to accomplish once I've created my project proposal and be clear about what they can do to help me.
Reflections on Process
It's too early for me to have a good sense of how to speak to this. I think once I've created a map for the semester in the project proposal, I'll easier be able to find a way to both reflect and improve my process. A big question mark I hope to solve is how to fold the decx.press team into my process. I'm optimistic that I'll be able to do this.