My Journey Learning Java: From Fundamentals to Frameworks and Key Lessons

"Think, output, and solidify. Explain technology in plain language so both you and others benefit." – Author Yi Hang.

Preface

If you are a Java developer, consider listening to the author’s painful learning journey, hoping the experiences can inspire your own study.

Beginning – Entry JAVA

The author, then a confused university student, bought a book titled "< >" from 明日科技, learning basic data types, control flow, exception handling, and collections, which set them on a long‑term Java path.

Development – Entering the Java Web World

The initial book focused heavily on Java Swing , leading the author to over‑invest time in UI components that later proved less relevant. This taught the importance of researching a technology’s ecosystem before deep diving.

Later, the author switched from books to video platforms like Bilibili, following channels such as 尚学堂 to relearn Java fundamentals repeatedly due to academic workload interruptions.

When moving to Java Web, the author learned Servlet + JSP development, found the mix of Java logic and front‑end code confusing, and self‑studied front‑end basics (HTML, CSS, JavaScript, Node.js).

Faced with career indecision between front‑end and back‑end, the author realized that too many concepts cause anxiety and suggested focusing on essential ideas, especially when reading source code like Spring’s container loading.

To combat information overload, the author emphasized “subtraction”: summarizing and distilling knowledge into concise statements, iterating constantly to achieve clearer understanding.

Deepening – Touching Framework Source Code

After mastering native Java Web, the author tackled frameworks such as SSH, SSM, and later SpringBoot, noting the configuration pain of older stacks and the simplicity of SpringBoot starters.

Motivated by the hype around source‑code reading, the author attempted to debug frameworks without guidance, eventually turning to paid courses (慕课网, 咕泡, 黑马, 尚硅谷) but still felt anxious, leading to the advice of committing to a single direction rather than chasing many trends.

The author stresses the importance of forming personal opinions, not blindly following trends like “algorithm is essential” or “source code is crucial,” and warns against self‑doubt and endless comparison with others.

Conclusion

The article summarizes the author’s Java learning pitfalls and insights, links to previous columns on MyBatis and Spring MVC source analysis, and promises future deep dives into Spring source code and a mini‑implementation project, hoping the shared experience helps readers.