log/ianHyeonseok JeongGitHub

Experience / Backend Education · Communication · Code Review

Java Backend Teaching Support

I answered Java questions, gave short explanations of core concepts, reviewed learner code, and helped learners understand backend request and database flows.

  • Experience
  • Java
  • Teaching
  • Code Review
  • Documentation
Role
Teaching assistant · Java Q&A · Basic instruction · Code review
Period
2025.12.31 ~ 2026.07.08
Type
Java backend education programs
Status
Teaching-support experience

Proof at a Glance

Evidence
  • Teaching support for Java backend education programs
  • Java Q&A, basic explanations, code review, and assignment feedback
Public and Validation Boundary
  • I do not claim learner outcomes or education-performance metrics.
  • Individual learner information is not disclosed.

Work flow

Structure and Flow

  1. 01Questions

    Received questions about Java, Spring, APIs, database connections, and assignments.

  2. 02Explanation

    Explained the concept or request flow in smaller steps and gave short basic lessons when needed.

  3. 03Code Review

    Reviewed code structure, naming, error flow, and responsibility separation.

  4. 04Feedback

    Helped learners find the next action instead of only giving the final answer.

Summary

This is work experience, not a selected development project.

I supported Java backend learners through Q&A, short basic lessons, code review, and assignment feedback. The main subjects included Java Core, OOP, Spring MVC, REST APIs, and SQL/database connection flow.

What I Did

  • Answered questions about Java syntax, OOP, collections, exceptions, and backend flow.
  • Gave short basic explanations when a learner needed the concept before solving the task.
  • Explained how a request moves through controller, service, database, and response layers.
  • Reviewed learner code for structure, naming, responsibility separation, and error handling.
  • Helped with REST API, SQL, JDBC/JPA, and assignment questions.
  • Used repeated questions to improve later explanations.

How I Worked

I tried to find where the learner’s understanding stopped. Sometimes the problem was syntax. In other cases, the learner could write each part but could not see how the parts connected.

I explained the flow in smaller steps, checked the code together, and helped the learner choose the next debugging action. I did not present myself as the lead instructor, and I do not claim learner-performance results.

What This Experience Shows

  • I can explain technical ideas in clear language.
  • I can read another person’s code and narrow down a problem.
  • I can give practical feedback without taking over the work.
  • I treat communication and documentation as part of technical work.