Core Competencies and Practices for Growing Junior Developers

If you want to be a growing junior developer, I think it's about more than just learning technology -- it's about being someone who keeps exploring, communicating, asking questions, recording, and sharing in a continuous cycle.
In this post, I'll walk you through concrete methods and attitudes for junior developers to grow on their own, plus growth strategies through technical writing and open source participation.

1. Exploration -- "Research First, Then Act" Over "Figure It Out on Your Own"#

For a growing developer, it's important to responsibly handle your work, but even more important to research thoroughly before acting rather than making decisions alone.
When you encounter a problem or requirement, start by looking up resources and examining prior cases.
If possible, experiment directly and learn the principles firsthand.
Building a habit of meaningful exploration -- not just idle curiosity -- broadens your thinking.

2. Communication -- Share, Participate, and Learn#

Development isn't a solo activity -- please remember that.
Growing juniors actively communicate and grow together.

• Share: When you solve a problem or learn something, share it with colleagues and write it up in team docs or a blog.
• Participate: Go to conferences and tech meetups, and don't be shy -- ask experts "How would you handle this?" Most pros actually want to teach someone. Through these conversations you leave a good impression, and after a thank-you, you can ask for a business card and expand your network.

3. Questioning -- Good Questions Lead to Better Answers#

Questioning is a skill that deepens your thinking.
If you include traces of your exploration in your question -- like "From what I understand, it works like this, but could you also approach it this way?" -- you'll get much better answers.
Good questions ultimately become opportunities for better growth.

4. Recording -- Turn Project Issues into Assets#

Whether it's an error or a small problem, recording your experiences creates a trail of growth.
When a problem occurs, try organizing it like this:

1. What was the problem?
2. How did you solve it?
3. What was the conclusion?
4. What did you learn from this experience?

Records organized this way can be expanded into blog posts or technical documents, and they become the foundation for technical writing skills.

5. Technical Writing -- A Developer's Power to Convey Knowledge#

Technical writing is the power to convey complex technology simply.
This ability plays a huge role in building your personal brand, improving collaboration efficiency, and earning others' trust.

Purposes of Technical Writing#

1. Efficient knowledge transfer -- Deliver information quickly and clearly.
2. Persuading others -- Draw understanding and empathy through logical flow.
3. Increasing personal value -- Build trust and influence by accumulating public records.

Expanding Developer Competencies#

• Work fundamentals: Focus, persistence, character
• STEM fundamentals: Math, science, engineering
• ICT knowledge: Algorithms, programming languages, computer science
• ICT application: The ability to connect technology with business

4 Principles of Technical Writing#

• Consider internal and external context: Understand the purpose, audience, and situation.
• Logical flow: Write logically without redundancy or omission using pyramid structure and MECE principles.
• Visual elements: Actively use charts, code, and other visual materials.
• Ethical foundation: Write with credible materials based on facts.

6. Open Source Participation -- Infinite Fuel for Growth#

The most effective way to turn what you've learned into shareable assets is open source participation.

What is Open Source Software (OSS)?
It's software where anyone can view, modify, and distribute the source code. In contrast, proprietary software often has restricted access and usage.

Advantages of OSS#

• You can learn production-level code and collaboration processes.
• You can network with developers worldwide.
• You can grow both your technical skills and credibility simultaneously.

How Do You Get Started?#

• Browse issues on GitHub projects you're interested in, and start with small contributions (documentation fixes, typo corrections, etc.).
• Check the contribution guide (CONTRIBUTING.md) to learn the official participation process.

Myths and Truths About OSS#

• Myth: "Only experts can participate."
• Truth: Beginners can contribute in many ways too -- documentation improvements, translations, testing, and more.

The Virtuous Cycle of Exploration, Communication, Questioning, and Recording#

Growing developers repeat the cycle of Exploration -> Communication -> Questioning -> Recording -> Writing -> Sharing -> Participation.
I believe that through this virtuous cycle, developers can leap from being mere technicians to professionals who create and share knowledge.

The self is not something ready-made, but something in continuous formation through choice of action.

-- John Dewey