Skip to content

Releases: codebuddies/v3

September 18th, 2019 Project Updates

19 Sep 04:00
@lpatmo lpatmo
0.0.2
8c3a9c9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
September 18th, 2019 Project Updates Latest
Latest

✅Announcements

🎯Short-term Goals

  • Start work on some proof-of-concept prototypes to help decide the tech to use for CBV3 (IN PROGRESS)
  • Re-launch our community newsletter, with the eventual goal of reaching out to sponsors who can support our Open Collective (IN PROGRESS)
  • Work on open source publicly / launch a Twitch channel so we can show off what a CodeBuddies hangout is like, and also have memories we can look back on years later (LAUNCHED: https://twitch.tv/codebuddies)
  • Identify key problems and solutions we want to solve for CBV3, and start sketching out some user stories

🎯Long-term Goals

  • Remote-first platform for people to find study and pair programming partners on any programming-related thing they want to learn
  • Friendly place for beginners to get un-stuck and not feel stupid asking questions
  • Help lift each other up side-project-wise, career-wise, and learning-wise
  • Sustainable open source project and revolving community of contributors
  • Exploratory sandbox where people can experiment, and the goal is learning

🔗Progress on the proof-of-concepts in the new repositories

Reminder: if you are interested in contributing to an issue, please comment on the issue thread that you are working on it! That helps minimize potential future PR conflicts/people stepping on each others' toes.

Node concept

  • Angelo started work on this! Not sure which issues need the most help (yet)

Go Concept

  • @cbelsole worked on this, and will be doing a code walkthrough that will be livestreamed on twitch.tv/codebuddies on Monday at 5:30pm PST / 8:30pm EST (check codebuddies.org/hangouts for the Zoom link)

Serverless concept

  • @d3vild06 worked on this! And walked through serverless/graphQL in a hangout you can watch here: https://www.youtube.com/watch?v=ea2nlNX2xas
  • Is looking for contributors! Especially someone who could lead on the React side and get resources displaying
  • Other TODOs:
  • Cost estimate of using netlify
  • Explore Apollo Client: https://www.apollographql.com/docs/react/
  • Explore using Auth0 vs. Netlify vs. an alternative for user management / authentication

Django concept

Vue concept

  • No work on this yet

✅Helpful links

📢❓Help wanted!

🎏Coming soon

  • More work on each of the prototypes
  • We should come to a stopping point with each of the prototypes and evaluate each side by side
  • Twitch streams ft. AMAs with other members of the community (BOTH prototype-related and non-CBV3-related)
  • Study groups twitch streamed to the CB Twitch (potentially one led by @tgrrr. Let me know if anyone else is interested!)
  • August newsletter still needs to go out
  • Discuss and decide on 2-3 core CB values, so we can have something to put on the new CBV3 website (but also try to observe as a community)
Assets 2
Loading

September 3rd, 2019 Project Updates

04 Sep 07:31
@lpatmo lpatmo
0.0.1
8c3a9c9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
September 3rd, 2019 Project Updates

🎯Short-term Goals

  • Start work on some proof-of-concept prototypes to help decide the tech to use for CBV3
  • Re-launch our community newsletter, with the eventual goal of reaching out to sponsors who can support our Open Collective
  • Work on open source publicly / launch a Twitch channel so we can show off what a CodeBuddies hangout is like, and also have memories we can look back on years later
  • Identify key problems and solutions we want to solve for CBV3, and start sketching out some user stories

🎯Long-term Goals

  • Remote-first platform for people to find study and pair programming partners on any programming-related thing they want to learn
  • Friendly place for beginners to get un-stuck and not feel stupid asking questions
  • Help lift each other up side-project-wise, career-wise, and learning-wise
  • Sustainable open source project and revolving community of contributors
  • Exploratory sandbox where people can experiment, and the goal is learning

🔗New repositories

✅Updates

👥 "User stories"

Some interpretations of what the CB V3 site might look like:

As a user, I'll be like:
1/ "I want to learn Python!"
2/ Search for all resources tagged python
3/ Filter resources by paid/level
4/ Bookmark the ones that look interesting
5/ Click into a group and find ideas of hangout pairing proposals. Also be able to start a discussion thread for the group.
6/ See list of other users who joined that group, and their timezones
7/ See all the resources listed under that group (we need to figure out: who has permissions to move resources under a group??)
8/ Leave notes (either private or public) about a particular resource, and see other public notes about it. 
9/ Start a discussion thread around a resource.
9/ Look at a calendar of upcoming public hangouts in the group
10/ Resource page will also show upcoming hangouts within groups the resource belongs to
11/ Have a study paths profile-y page where I can see my study path and also edit my profile info containing things like my CB Connect info, timezone, and availability this week

Results of the CodeBuddies 2019 survey: https://twitter.com/codebuddiesmeet/status/1136851599043600388

I've never written a "user story" before, so I don't know how I would go about that.
I read the one that was previously posted, though, and the starting point didn't reflect why I joined Code Buddies.  My first thought when I arrived at Code Buddies was that I wanted to find a community to help me and support me in my efforts.  There were plenty of resource lists available and plenty of options out there.  What I wanted was to find people who were willing to slog through the work right with me.

Yes, I think working together on a shared resource has been the most valuable part of my experience on this site.  Working on Exercism's Python track and discussing solutions with Linda,  Bethany, and a few others was very motivating and helped me feel like I could learn to code.
Yet, I noticed in the survey that most users haven't participated in a single hangout.  The most common reason that users raised was that they weren't aware that the hangouts were occurring.  One way to remedy this is to ensure that all Hangouts are announced on Slack (I noticed that the #announcements page does not register all hangout sessions).

I also wonder if the lack of interest in hangouts has something to do with how infrequently they are scheduled and the types of hangouts that are offered.  Most of the meetings that have been scheduled recently have been on intermediate topics, in my view.

Another challenge has been building a group of  participants.  When trying to build membership for the Python Data Science study group, I've kept an eye out for anyone who expresses an interest in anything related to this topic.  My concern is that new Code Buddies members might find it uncomfortable being asked if they want to participate, as soon as they post something on #introduce-yourself.

It would be great if new users were asked to fill out a form when they sign up for Code Buddies, asking what areas they want to learn and if they are comfortable acting as mentors in others.  The site could try to pair users, based on interests and skills.

Many of the components are already available on the existing website.  Some of the steps in the process of creating hangouts could be clearer, but I think the greater challenge here is in motivating the community to create more hangouts, not in the tech.  We need more experienced programmers who are willing to lead more inexperienced members in hangouts.

Perhaps there are private channels that I'm not aware of, so I'm not sure if I'm seeing the full picture here.  But, of the public beginners channels, I've noticed that they tend to be far less active than the more general channels, where advanced users are available to comment (#javascriptbeginers, for example, has only 69 members).
Many of my points come from my recent experience of trying to organize the Python Data Science group.  In this group, one of the biggest challenges is in finding exercises and in pacing the readings.
For the reading, I just chopped up the book into roughly 30 page long chunks.  The book doesn't offer exercises, so we've been using PyCon workshops that cover similar topics and have asked members to download the materials from GitHub.  Then, I'm often rushing to stay ahead of the readings and complete the exercises; but, when it comes time for discussion, I honestly don't know if I can really clear up anyone's misunderstandings (since I literally just learned the material a few days before the meeting).
It's at times like these when I feel we could use a more experienced programmer, to provide a better structure to the discussion and to be able to clear up any of the topics that aren't 100% clear.

^ Some great observations and feedback from @Grimmothy, a hangout and study group organizer

📢❓Help wanted!

🎏Coming soon

  • AMA with @lpatmo about CodeBuddies (project updates, the history, people who’ve contributed, why it exists, etc.)
  • More work on each of the prototypes
  • We should come to a stopping point with each of the prototypes and evaluate each side by side
  • Twitch streams ft. AMAs with other members of the community (BOTH prototype-related and non-CBV3-related)
  • Study groups twitch streamed to the CB Twitch (potentially one led by @tgrrr. Let me know if anyone else is interested!)
  • August newsletter needs to go out
  • Discuss and decide on 2-3 core CB values, so we can have something to put on the new CBV3 website (but also try to observe as a community)
Loading