This is an AI translated post.
[Non-Major, Developer Survival] 17. New Developer Portfolio, How Far?
- Writing language: Korean
- •
-
Base country: All countries
- •
- Information Technology
0000-00-00 00:00:00
Select Language
Summarized by durumis AI
- A new developer's portfolio should focus on implementing basic CRUD functions, and it's important to showcase real-world development experience through external API integration.
- Infra such as Docker and Cloud are not essential at the new developer level, and it is more effective to focus on development skills.
- If you are confident in your development skills, you can try using OpenStack, but if not, it is better to focus on strengthening your development skills and building your portfolio.
Non-majors, Survive as a Developer
#17. New Developer Portfolio, How Far?
Personally, through other platforms, I often get requests for portfolio feedback when mentoring.
Most portfolios made at academies are well-made in terms of implementing the minimum CRUD using technology stacks that companies require these days, and they are well-made up to the point of dividing them into Front and Backend, but the difference is the level of experience with Infra.
Generally, they make web services on various topics such as restaurants, pet care, and gatherings, and the
following technology stacks are commonly used.
They are building their portfolio using SpringBoot, Oracle, and JPA, and the technology stack itself is good. However, those who have Infra experience have studied and applied Infra aspects such as Docker, CI/CD implementation through Cloud, and Redis in-memory DB activities in addition to basic development.
However, I personally think that at the entry level, it is more than enough for a new developer's portfolio if you make basic functionalities well and have some experience with external API integration.
Popular external APIs that are easy to use include Naver login, Naver Maps API, Public Data Portal API, etc., and they are actually widely used in the real world, so the experience of developing by looking at API spec documents itself is important, and I think that portfolio is enough.
It is impossible to entrust new developers with development work right away, and Infra is even more impossible.
Therefore, I have the thought that "at least the development is good." I think that a portfolio that is basic CRUD, but well-thought-out and made, will be enough for real-world developers rather than an awkward combination of development + Infra.
Therefore, if you are confident in your development skills, it is good to try various open stacks, but if not, I think it is better to focus more on development and build a portfolio, which will actually help you get a job.
