Thanks for a great fourth session Wednesday. Our team commented how curious everyone was to discuss documentation and how we as individuals can improve on our day to day documentation. Below is a light digest of Call 4, including a reminder for your (TWO) Seaside Chats and additional (TWO) Co-Working times before our Call 5 on Wednesday, October 19th. Looking forward to seeing you then!
Goals: We discussed documentation, documentation, and more documentation!! Plus touched base with our teams on where our Pathway is and where it may go….
Task for next time:
Have TWO Seaside Chats and work on your pathway
Have TWO Seaside Chat with your team (recommend one each week)
Prepare to present your Pathway on Call 5 (Oct 19)
Each group has 10 minutes to share their pathway: (5 min present + 5 min Qs)
If you are unable to upload to Google Drive, please email Anna or Corey your Pathway and they will drop it in the folder for you.
Co-working: (optional). This is a time to come work on your own data science things, but also be able to talk things through and screenshare to get help from others. Note that we have TWO co-working sessions scheduled:
It [documentation] always seems like a good idea but it’s kind of boring. And then there is of course the problem that I think there is no way I could ever forget what I’m going through right now. Why do I need to spend so long describing it when I’ll know it tomorrow and the next day and the next day. But then it seems I always come back to it the day after that and know nothing about what I was doing. +1+1
I really like all of these ideas and I feel like I can get started on them right away. One thing that I need to work on is to actually set the time aside to outline everything as I’m working so that I’m not starting from scratch as I start to formalize the documentation. To break it up into chunks, do it little by little… I think that would make the whole task a lot easier. I really like the examples, they are helpful.+1000
Documentation takes WORK and motivation - and it can be not-so-fun to do if/when I develop things alone. I like to combat the boredom and incentivise myself to do the activity by listening to music, co-working (i.e. don’t document alone!) and rewarding myself with something after I finish a daunting task. +1
Music Recommendation: Monterey Bay Aquarium Lofi Hip Hop Recordings | Monterey Bay Aquarium Krill Waves Radio
I like the emphasis on tracking progress. It sometimes gets tricky when progress is discussed through emails because it may get lost in other discussions. In the past we made spreadsheets to track tasks but was never actually used consistently. If this can be done consistently as common practice, then that would also be better. +1
Hi @Openscapes2022-swrcb-cohort,
Thanks for a great fourth session Wednesday. Our team commented how curious everyone was to discuss documentation and how we as individuals can improve on our day to day documentation. Below is a light digest of Call 4, including a reminder for your (TWO) Seaside Chats and additional (TWO) Co-Working times before our Call 5 on Wednesday, October 19th. Looking forward to seeing you then!
Have a good week, Devan, Tina, Corey, and Anna
Digest: Cohort Call 4 [ 2022-SWRCB ] CohortCall Google folder - contains video recordings and completed agendas openscapes.github.io/2022-swrcb - Cohort webpage MS Team Channel - Water Boards Teams Channel
Goals: We discussed documentation, documentation, and more documentation!! Plus touched base with our teams on where our Pathway is and where it may go….
Task for next time:
Slide Decks: Week 4: Documentation & the Pathway
A few lines from shared notes in the Agenda doc:
It [documentation] always seems like a good idea but it’s kind of boring. And then there is of course the problem that I think there is no way I could ever forget what I’m going through right now. Why do I need to spend so long describing it when I’ll know it tomorrow and the next day and the next day. But then it seems I always come back to it the day after that and know nothing about what I was doing. +1+1
I really like all of these ideas and I feel like I can get started on them right away. One thing that I need to work on is to actually set the time aside to outline everything as I’m working so that I’m not starting from scratch as I start to formalize the documentation. To break it up into chunks, do it little by little… I think that would make the whole task a lot easier. I really like the examples, they are helpful.+1000
Documentation takes WORK and motivation - and it can be not-so-fun to do if/when I develop things alone. I like to combat the boredom and incentivise myself to do the activity by listening to music, co-working (i.e. don’t document alone!) and rewarding myself with something after I finish a daunting task. +1
I like the emphasis on tracking progress. It sometimes gets tricky when progress is discussed through emails because it may get lost in other discussions. In the past we made spreadsheets to track tasks but was never actually used consistently. If this can be done consistently as common practice, then that would also be better. +1