OkayStudy
EN English 한국어 日本語 中文 हिन्दी বাংলা اردو Español Português Français Deutsch Русский العربية Bahasa Indonesia Tiếng Việt ไทย Türkçe

How to enable notifications

Notifications are unavailable in this browser or on this address. Try a supported browser on the secure BaeumNova site.

If notifications are blocked, allow them in your browser settings.

  1. Open the site controls beside the address bar, or your browser’s site settings. Set Notifications for this site to Allow.
  2. In your device settings, allow notifications for your browser and check Do Not Disturb or Focus.
  3. Return to BaeumNova and reload the page. Once notifications are on, the bell disappears.

On iPhone or iPad, add BaeumNova to your Home Screen, open it there, then allow notifications.

Guest

Sign in to see your lesson schedule.

Getting started

Start English lessons step by step

Tap a step to go there.

Free trial

  1. Pick a free trial teacher

    Tap a teacher with [Free trial] on the photo.

  2. Tap a time with a gift

    Tap a free time with a gift picture in the timetable.

  3. Sign in and book

    Sign in and it is booked right away. No payment.

  4. Camera & Mic Check

    Check your camera and mic before class.

  5. Check your booked lessons

    See the time and tutor of your booked lesson.

  6. Enter the lesson

    Join the video classroom when it’s time.

  7. Check your past lessons

    Look back at the lessons you finished.

  8. Rate your tutor

    Rate your tutor after the lesson.

About me

  1. Add your profile photo

    A photo helps your tutor recognize you.

  2. Introduce yourself

    Write a hello on the introductions board.

Take lessons

  1. Book a lesson

    Pick a time on a tutor’s timetable.

  2. Pay the lesson fee with PayPal

    Pay on PayPal — your lesson is booked as soon as PayPal confirms it.

  3. Check your booked lessons

    See the time and tutor of your booked lesson.

  4. Enter the lesson

    Join the video classroom when it’s time.

  5. Check your past lessons

    Look back at the lessons you finished.

  6. Rate your tutor

    Rate your tutor after the lesson.

All steps
Step 7

Collaboration — pull requests and code review

On a team nobody commits straight to main. Branch, push, open a pull request, get reviewed, merge. This is the loop every software team runs on.

What you'll learn

  • You can run the → → review → loop
  • You can write a pull request that's easy to review
  • You know the flow for contributing to someone else's project

On a team you don't directly to main. You branch, do the work, the branch, and open a pull request asking for it to be merged. A reviewer reads it, leaves comments, and once it passes, it goes in. and both work this way, and so does almost every company you'll join.

Teammates around a table look at the same document with small comment bubbles, and one of them holds a green check stamp, ready to approve it.
A pull request asks the team to read your change before it joins .

A pull request isn't a place to have your inspected — it's where you share intent. Put what you did in the title, and why it's needed plus how you verified it in the body, and review gets much faster. And keep pull requests small: past about 300 lines, reviewers find it hard to read carefully and tend to just approve.

When review comments come in, add commits to the same branch and push again — the pull request updates itself. To contribute to someone else's public , fork it to your account first, branch inside your fork, and open the pull request against the original. The gh command () lets you create, list, and check out pull requests without leaving the .

Understand it easily

A pull request is like handing in homework to be checked before it goes up on the class wall. Teammates read the changes and leave comments, and only after approval is it merged into main.

Commands for this step

git switch -c fix/session-expiry
Open a branch for the work. Name it after what it does.
git push -u origin fix/session-expiry
Push the branch to the so a pull request can be opened from it.
gh pr create --fill
Create a pull request from the terminal, filling title and body from your commits.
gh pr checkout <number>
Check out someone else's pull request locally to test it before approving.

Common mistake and how to fix it

Opening one huge pull request with many unrelated changes. Reviewers cannot read it well, so mistakes slip through. Keep one purpose per pull request, and if a change grows large, split it into smaller branches.

You mark this yourself. Nothing is graded here.

Mark this step as understood?

This cannot be undone yet, so mark it only when you really understand.

Marked as understood

You mark this yourself. Nothing is graded here.

Booking time has passed

Voice chat with Lyen Pick a language and a topic, then talk with Lyen by voice

Lyen speaks aloud in English · 한국어 · 日本語 · हिन्दी. In other languages she answers in text.

Voice chat with Lyen is for members. Sign up first, then start talking.