πŸ‘―

Pair Programming

Learn practical Japanese for pair programming situations through realistic conversations.

100 lessons

Log in to track your progress.

  1. 1

    Requesting a Code Review β€” Senior colleague

    To ask a senior colleague to review your pull request politely.

  2. 2

    Daily Standup Update β€” Senior colleague

    To report yesterday's work, today's plan, and any blockers.

  3. 3

    Reporting a Production Issue β€” Senior colleague

    To report that an error is happening in production and coordinate a fix.

  4. 4

    Discussing Requirements β€” Senior colleague

    To clarify the specification before starting implementation.

  5. 5

    Confirming a Deployment β€” Senior colleague

    To confirm it is safe to deploy to production.

  6. 6

    Giving a Time Estimate β€” Senior colleague

    To estimate how long a task will take honestly.

  7. 7

    Asking for Help While Stuck β€” Senior colleague

    To ask for help politely after trying yourself first.

  8. 8

    Giving Feedback in Code Review β€” Senior colleague

    To suggest a change kindly without sounding harsh.

  9. 9

    Scheduling a Technical Meeting β€” Senior colleague

    To find a time to discuss a topic together.

  10. 10

    Handing Over a Task β€” Senior colleague

    To hand over your work clearly before being away.

  11. 11

    Requesting a Code Review β€” Department manager

    To ask a department manager to review your pull request politely.

  12. 12

    Daily Standup Update β€” Department manager

    To report yesterday's work, today's plan, and any blockers.

  13. 13

    Reporting a Production Issue β€” Department manager

    To report that an error is happening in production and coordinate a fix.

  14. 14

    Discussing Requirements β€” Department manager

    To clarify the specification before starting implementation.

  15. 15

    Confirming a Deployment β€” Department manager

    To confirm it is safe to deploy to production.

  16. 16

    Giving a Time Estimate β€” Department manager

    To estimate how long a task will take honestly.

  17. 17

    Asking for Help While Stuck β€” Department manager

    To ask for help politely after trying yourself first.

  18. 18

    Giving Feedback in Code Review β€” Department manager

    To suggest a change kindly without sounding harsh.

  19. 19

    Scheduling a Technical Meeting β€” Department manager

    To find a time to discuss a topic together.

  20. 20

    Handing Over a Task β€” Department manager

    To hand over your work clearly before being away.

  21. 21

    Requesting a Code Review β€” Section chief

    To ask a section chief to review your pull request politely.

  22. 22

    Daily Standup Update β€” Section chief

    To report yesterday's work, today's plan, and any blockers.

  23. 23

    Reporting a Production Issue β€” Section chief

    To report that an error is happening in production and coordinate a fix.

  24. 24

    Discussing Requirements β€” Section chief

    To clarify the specification before starting implementation.

  25. 25

    Confirming a Deployment β€” Section chief

    To confirm it is safe to deploy to production.

  26. 26

    Giving a Time Estimate β€” Section chief

    To estimate how long a task will take honestly.

  27. 27

    Asking for Help While Stuck β€” Section chief

    To ask for help politely after trying yourself first.

  28. 28

    Giving Feedback in Code Review β€” Section chief

    To suggest a change kindly without sounding harsh.

  29. 29

    Scheduling a Technical Meeting β€” Section chief

    To find a time to discuss a topic together.

  30. 30

    Handing Over a Task β€” Section chief

    To hand over your work clearly before being away.

  31. 31

    Requesting a Code Review β€” Team leader

    To ask a team leader to review your pull request politely.

  32. 32

    Daily Standup Update β€” Team leader

    To report yesterday's work, today's plan, and any blockers.

  33. 33

    Reporting a Production Issue β€” Team leader

    To report that an error is happening in production and coordinate a fix.

  34. 34

    Discussing Requirements β€” Team leader

    To clarify the specification before starting implementation.

  35. 35

    Confirming a Deployment β€” Team leader

    To confirm it is safe to deploy to production.

  36. 36

    Giving a Time Estimate β€” Team leader

    To estimate how long a task will take honestly.

  37. 37

    Asking for Help While Stuck β€” Team leader

    To ask for help politely after trying yourself first.

  38. 38

    Giving Feedback in Code Review β€” Team leader

    To suggest a change kindly without sounding harsh.

  39. 39

    Scheduling a Technical Meeting β€” Team leader

    To find a time to discuss a topic together.

  40. 40

    Handing Over a Task β€” Team leader

    To hand over your work clearly before being away.

  41. 41

    Requesting a Code Review β€” Coworker

    To ask a coworker to review your pull request politely.

  42. 42

    Daily Standup Update β€” Coworker

    To report yesterday's work, today's plan, and any blockers.

  43. 43

    Reporting a Production Issue β€” Coworker

    To report that an error is happening in production and coordinate a fix.

  44. 44

    Discussing Requirements β€” Coworker

    To clarify the specification before starting implementation.

  45. 45

    Confirming a Deployment β€” Coworker

    To confirm it is safe to deploy to production.

  46. 46

    Giving a Time Estimate β€” Coworker

    To estimate how long a task will take honestly.

  47. 47

    Asking for Help While Stuck β€” Coworker

    To ask for help politely after trying yourself first.

  48. 48

    Giving Feedback in Code Review β€” Coworker

    To suggest a change kindly without sounding harsh.

  49. 49

    Scheduling a Technical Meeting β€” Coworker

    To find a time to discuss a topic together.

  50. 50

    Handing Over a Task β€” Coworker

    To hand over your work clearly before being away.

  51. 51

    Requesting a Code Review β€” Client

    To ask a client to review your pull request politely.

  52. 52

    Daily Standup Update β€” Client

    To report yesterday's work, today's plan, and any blockers.

  53. 53

    Reporting a Production Issue β€” Client

    To report that an error is happening in production and coordinate a fix.

  54. 54

    Discussing Requirements β€” Client

    To clarify the specification before starting implementation.

  55. 55

    Confirming a Deployment β€” Client

    To confirm it is safe to deploy to production.

  56. 56

    Giving a Time Estimate β€” Client

    To estimate how long a task will take honestly.

  57. 57

    Asking for Help While Stuck β€” Client

    To ask for help politely after trying yourself first.

  58. 58

    Giving Feedback in Code Review β€” Client

    To suggest a change kindly without sounding harsh.

  59. 59

    Scheduling a Technical Meeting β€” Client

    To find a time to discuss a topic together.

  60. 60

    Handing Over a Task β€” Client

    To hand over your work clearly before being away.

  61. 61

    Requesting a Code Review β€” Person in charge

    To ask a person in charge to review your pull request politely.

  62. 62

    Daily Standup Update β€” Person in charge

    To report yesterday's work, today's plan, and any blockers.

  63. 63

    Reporting a Production Issue β€” Person in charge

    To report that an error is happening in production and coordinate a fix.

  64. 64

    Discussing Requirements β€” Person in charge

    To clarify the specification before starting implementation.

  65. 65

    Confirming a Deployment β€” Person in charge

    To confirm it is safe to deploy to production.

  66. 66

    Giving a Time Estimate β€” Person in charge

    To estimate how long a task will take honestly.

  67. 67

    Asking for Help While Stuck β€” Person in charge

    To ask for help politely after trying yourself first.

  68. 68

    Giving Feedback in Code Review β€” Person in charge

    To suggest a change kindly without sounding harsh.

  69. 69

    Scheduling a Technical Meeting β€” Person in charge

    To find a time to discuss a topic together.

  70. 70

    Handing Over a Task β€” Person in charge

    To hand over your work clearly before being away.

  71. 71

    Requesting a Code Review β€” Junior colleague

    To ask a junior colleague to review your pull request politely.

  72. 72

    Daily Standup Update β€” Junior colleague

    To report yesterday's work, today's plan, and any blockers.

  73. 73

    Reporting a Production Issue β€” Junior colleague

    To report that an error is happening in production and coordinate a fix.

  74. 74

    Discussing Requirements β€” Junior colleague

    To clarify the specification before starting implementation.

  75. 75

    Confirming a Deployment β€” Junior colleague

    To confirm it is safe to deploy to production.

  76. 76

    Giving a Time Estimate β€” Junior colleague

    To estimate how long a task will take honestly.

  77. 77

    Asking for Help While Stuck β€” Junior colleague

    To ask for help politely after trying yourself first.

  78. 78

    Giving Feedback in Code Review β€” Junior colleague

    To suggest a change kindly without sounding harsh.

  79. 79

    Scheduling a Technical Meeting β€” Junior colleague

    To find a time to discuss a topic together.

  80. 80

    Handing Over a Task β€” Junior colleague

    To hand over your work clearly before being away.

  81. 81

    Requesting a Code Review β€” Manager

    To ask a manager to review your pull request politely.

  82. 82

    Daily Standup Update β€” Manager

    To report yesterday's work, today's plan, and any blockers.

  83. 83

    Reporting a Production Issue β€” Manager

    To report that an error is happening in production and coordinate a fix.

  84. 84

    Discussing Requirements β€” Manager

    To clarify the specification before starting implementation.

  85. 85

    Confirming a Deployment β€” Manager

    To confirm it is safe to deploy to production.

  86. 86

    Giving a Time Estimate β€” Manager

    To estimate how long a task will take honestly.

  87. 87

    Asking for Help While Stuck β€” Manager

    To ask for help politely after trying yourself first.

  88. 88

    Giving Feedback in Code Review β€” Manager

    To suggest a change kindly without sounding harsh.

  89. 89

    Scheduling a Technical Meeting β€” Manager

    To find a time to discuss a topic together.

  90. 90

    Handing Over a Task β€” Manager

    To hand over your work clearly before being away.

  91. 91

    Requesting a Code Review β€” The whole team

    To ask a the whole team to review your pull request politely.

  92. 92

    Daily Standup Update β€” The whole team

    To report yesterday's work, today's plan, and any blockers.

  93. 93

    Reporting a Production Issue β€” The whole team

    To report that an error is happening in production and coordinate a fix.

  94. 94

    Discussing Requirements β€” The whole team

    To clarify the specification before starting implementation.

  95. 95

    Confirming a Deployment β€” The whole team

    To confirm it is safe to deploy to production.

  96. 96

    Giving a Time Estimate β€” The whole team

    To estimate how long a task will take honestly.

  97. 97

    Asking for Help While Stuck β€” The whole team

    To ask for help politely after trying yourself first.

  98. 98

    Giving Feedback in Code Review β€” The whole team

    To suggest a change kindly without sounding harsh.

  99. 99

    Scheduling a Technical Meeting β€” The whole team

    To find a time to discuss a topic together.

  100. 100

    Handing Over a Task β€” The whole team

    To hand over your work clearly before being away.