Reflections - Githubissues

What went well in building the project? What lessons will you take away from the experience?
- There was not too many huge blockers that were caused from broken code. They were mostly from lack of understanding of the python and django tango. Once figured out the progress was slow but steady. A take way for me is to spend more time going over django documentation to get a better understanding of whats allowed and how to utilize it
Is there anything about your efforts/workflow you want to reproduce in future projects?
- Compared to previous projects I would like to reproduce the steady pace I was able to maintain. More hours were used on actually coding functionality or design than figuring out a solution to a problem. Its a huge confidence booster which helped balance out some frustration during development
What did not go so well? Which events/obstacles blocked you or impeded your / team’s progress?
- Creating my own views, paths and templates were very challenging if they deviated from the notions examples. The deadline and planning itself was a huge obstacle. My turtle pace made for some stressful planning. Also using materialize posed an issue because some classes were preset and changing them seemed more of an issue than it should've been. There was a lot of dropping server and running server to test the css I wrote as opposed to just reloading the page and the most time in design was spent trying to see what would work with what materialize preemptively used.
What will you do to prevent that from occurring in a future project/collaboration?
- BETTER PLANNING! I got too far into the deadline to completely get rid of materialize and opt for all custom css. With better planning and my experience dealing with materialize future projects will either use a different css library or (more than likely) have custom styling

ant07hony / Green_Thumb

Reflections #3