You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are officially 80 percent of the way through the cohort session. Before you start blocking out dates for next spring or panicking about how to complete your current pathway, let's reflect on another great cohort call. Thank you, @AHolder1, for teaching us how to manage project work in GitHub (perhaps particularly useful during this final push to the finish). Another big thank you to this week's guest speaker, Alena Reynolds, who helped us consider our data cleanliness expectations and how important it is to set them.
Speaking of communicating information and setting expectations, please take a look at the following text for light digest of Call 4 and some reminders for upcoming intermediate sessions.
Cheers,
TJ & the rest of the Mentor + Instructor Team
We discussed how to use GitHub for project management & data strategies for future us. We started by practicing creating and submitting issues (e.g., the classic fall dilemma of #8 when to don the pumpkin beanie). We followed up by reflecting on how and whether GitHub or other software can help us streamline projects. Finally, our guest speaker guided us through what it means to have tidy data.
Discussion Highlights
GitHub for Project Management
How do these topics resonate with you?
Use the project management software that works for your team.
Buy-in and compatibility with existing processes are crucial.
Tag your team.
GitHub has some of the best cross-platform functionality.
Project Management Ideas
Our options include MS Project, Trello, and GitHub
Move task management from email to project management software
Make a second brain to organize projects
Data Strategies for Future Us
Tackle these strategies one a time; don’t bite off more than you can chew
If anyone wants to deep-dive into the theory of data architecture, you can read up on Medallion Architecture. The raw data lives in the bronze layer in that model.
How do you protect raw data?
Label “do not touch” in filename
Limit # of people that have access, if possible
Write an SOP if this isn’t possible
Backup at least 1 additional place (e.g., external hard drive)
Tasks for next time
Seaside Chat 1: Fill in the “next steps” column of your Pathway
Focus on the steps you will need to take to achieve your “Future You” goals.
Use the “Next Steps” column and write down the immediate next step(s) you can take to start working towards “Future You”. Try to be as specific as possible.
Write down what you think you need to do instead of focusing on priorities. Hint: writing down “we need to figure out how to …” or “we need to set time aside to think about … more” totally counts! It’s not about knowing/having all the answers/solutions - it’s about documenting the immediate next step you need to take to find them! Resources:Pathways details & examples
Seaside Chat 2: Prepare to present your Pathway work-in-progress on our final call
Each group has 15 minutes to share their pathway: (10 min present + 5 min Qs)
You’ve been practicing this through the reflections breakout groups on earlier Calls
Presentations can be formal or informal - share whatever you have with us in a way that feels right for you!
Team leads/supervisors are encouraged not to present!
Share Pathway Doc in our Pathway
Share folder, if you want
Cohort Co-working Sessions (optional)
Friday (2024-09-20) and Wednesday (2024-09-25)
These are a time to come work on your own things, but also be able to talk things through and screenshare to get help from others.
The text was updated successfully, but these errors were encountered:
@Openscapes/2024-swrcb-fall-cohort sorry for the original partial digest. I tagged everyone a little early in the process! Please take another look at 04 Cohort Call Digest 2024-SWRCB-Fall if you have not gotten an updated notification.
Hi everyone @Openscapes/2024-swrcb-fall-cohort
We are officially 80 percent of the way through the cohort session. Before you start blocking out dates for next spring or panicking about how to complete your current pathway, let's reflect on another great cohort call. Thank you, @AHolder1, for teaching us how to manage project work in GitHub (perhaps particularly useful during this final push to the finish). Another big thank you to this week's guest speaker, Alena Reynolds, who helped us consider our data cleanliness expectations and how important it is to set them.
Speaking of communicating information and setting expectations, please take a look at the following text for light digest of Call 4 and some reminders for upcoming intermediate sessions.
Cheers,
TJ & the rest of the Mentor + Instructor Team
Digest: Cohort Call 4 [ 2024F-SWRCB ]
Resources
General
Slide Decks
Data Management
Goals
We discussed how to use GitHub for project management & data strategies for future us. We started by practicing creating and submitting issues (e.g., the classic fall dilemma of #8 when to don the pumpkin beanie). We followed up by reflecting on how and whether GitHub or other software can help us streamline projects. Finally, our guest speaker guided us through what it means to have tidy data.
Discussion Highlights
GitHub for Project Management
How do these topics resonate with you?
Project Management Ideas
Data Strategies for Future Us
Tasks for next time
Hint: writing down “we need to figure out how to …” or “we need to set time aside to think about … more” totally counts! It’s not about knowing/having all the answers/solutions - it’s about documenting the immediate next step you need to take to find them!
Resources: Pathways details & examples
The text was updated successfully, but these errors were encountered: