open summer of code
HomeWebsiteGitHub
  • Welcome to osoc!
  • Code of Conduct
  • The osoc Way of Work & Play
    • Working Together in a Remote Setting
  • Students
    • Applying as a student at osoc
      • Privacy Policy for Open Knowledge Belgium
    • Being a student at osoc
      • Practical: When, where, how long, food
      • Health, COVID, Insurance, Sick Days
      • Study material
    • The Student Job
    • Salary & Reimbursements
  • Coaches & Student coaches
    • Being a coach at oSoc
    • The Coaching Job
      • Soft Skills & Expectations
      • Tasks
      • How to Manage a Team: Techniques
      • Coaching Cases
      • Battle Prep
      • Student Coaches
      • Screening students
    • Projects
    • Partner Communication
    • Practical
  • partners
    • Being a partner at oSoc
      • Apply
      • Attend
    • The Partner's Job
    • Projects
  • Tools & Resources
    • Discord
      • Basics
      • Discord etiquette
      • Setting your nickname & description
      • Managing notifications
      • Offering and Receiving Help
      • Find Your Discord Username
    • NextCloud
    • The #osoc Emoji
    • Big Blue Button: Video Calls
    • Deployment
    • Maps & Cartography
  • Tutorials
    • Create Crests
    • Pitching
      • Pitch and Interview Tips
      • Pitch on Discord
      • Pitch Content Tips
    • Interviews
    • Hosting
    • Deliver Like a Pro
      • Publish a Github Page
    • Conduct (Remote) Tests and Interviews with Real People + Archetypes
  • Organisers
    • How to set up oSoc for your country
      • Preparation
      • Selection
      • Practical
        • Setting Up a Remote Edition
      • Informing people
    • On-site editions: 4 weeks of well-organised serendipity
      • Calendar Example Remote Edition (BE)
        • Week 1: Explore
          • Day 1: Welcome (to the Madness 😏)
          • Day 2: Meet the Client + Prepare for Hackathon
          • Day 3: Hackathon & Pitching
          • Day 4: Pitch & Battle Plan
        • Week 2: Build
          • Day 1: Build, test, document + Learn how to vlog
          • Day 2: Build, test, document
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 3: Build more
          • Day 1: Build, test, document + How to deploy
          • Day 2: Day off!
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 4: Deliver
          • Day 1: Ship ship ship
          • Day 2: Pitch pitch pitch
          • Day 3: Delivery Day
          • Day 4: Demo Day
      • Kick-off day 1 (or chaos day)
      • Hackathon day 2 — 4
      • Build — week 2
      • Build — week 3
      • Delivery week — week 4
      • Evaluation — follow-up
    • Taking over the world
    • Salary & Reimbursements
    • Managing teams
  • test
Powered by GitBook
On this page
  • Asking for Help from Anyone
  • The Rubber Duck Debugging Technique
  • Asking for Help
  • Making Yourself Available to Help

Was this helpful?

  1. Tools & Resources
  2. Discord

Offering and Receiving Help

Osoc was built on people helping each other out, by offering their skills, knowledge and enthusiasm!

PreviousManaging notificationsNextFind Your Discord Username

Last updated 3 years ago

Was this helpful?

Asking for Help from Anyone

We have a bunch of help channels in Discord. Got a question? Pop in in there. Someone might pick it up 👀.

The Rubber Duck Debugging Technique

You take rubber (or imaginary) duck, and you explain the problem. Out loud. Yes, really. Observe how talking to yourself makes you smarter.

Asking for Help

Whenever a someone types "@helping-hand" in one of the help channels, everyone that clicked the little hand in the #help channel, will get a notification. If you can help out, you can just react on that message in the corresponding channel!

Making Yourself Available to Help

Click the little hand emoji in #help to make yourself available to help!

Tip: As a coach, whenever you have some time off – AKA letting your students go 🔥, you can offer your time to help out students by clicking the hand emoji in the help channel #start-consulting.

Aim to be available to people outside of your team approximately for one hour a day (fulltime coaches) or half an hour a day (halftime coaches).

Even if you're not actively consulting, and you see a message pop up in one of the help channels, you don't have to hold back. Open summer of code was built on people helping each other out!

Have you ever asked someone a question, and by asking it, and then you realise you know the answer? Let's avoid the awkward "Oh never mind.. sorry" moment by using the !

Couldn't figure out find the answer? or !

You can read more about this technique on – specifically for development. However, it's also useful for problems, like finding out how a certain tool works. Try it and let us know if it worked!

Rubber Duck Debugging technique
Wikipedia
Ask in one of the help channels
consult a coach
A duck
#help channel