Non-majors, Surviving as Developers

#7. What helps and doesn't help when applying for a junior developer position

In developer communities, questions like "Is it okay to ~ when applying for a developer position?" are often raised.
I'd like to summarize what I personally think helps and what doesn't.

1️⃣ Technical Blog
Many people post summaries of what they learned at school or on their own on their blogs. Even companies like Baedal Minjok and famous service companies run their own tech blogs, and it seems like having a tech blog(?) makes you feel more like a developer. I recommend writing one to review and organize what you've learned, but personally I think it's inefficient to invest too much time in posting content to a blog.

You have so much to do, like acquiring and reviewing what you learned at school, and preparing for the next lesson, but instead of spending time organizing and editing content for a blog, I think it's more efficient to spend more time studying. The truth is, most of the content posted on blogs is already on other blogs, and you don't have time to look at it in detail when you're reviewing resumes... Developers are always busy...ㅜ)

I'm writing this blog post now, but I'm only summarizing what I've learned in my spare time or what I've made at work, and only things I think I'll want to review later. It's better to focus on studying than on blogging during your job hunt!

Personal recommendation: ⭐️ ⭐️

2️⃣ Git Hub
Git is used for version control. It's used to share source code, manage different versions, record deployment history, and is almost essential in the industry. It's also used to combine code with team members when working on projects at school, and it serves as a repository for storing the source code you've learned on your own.

I personally recommend managing your source code on GitHub. It's a system that's essential in the industry, but it doesn't seem to be included in school curriculums very often. It's good to study Git to get used to it so you can adapt quickly after you get a job. However, you don't need to commit every day to show your dedication(?), such as "one commit per day" or "growing the grass". Recruiters don't really care about that much detail anyway, and if you're just committing school source code all the time, it's not very meaningful.

Even if it's a small and simple project, classifying it by repository, committing it, and organizing the README.md file with information about the program, what you learned while making it, and what was difficult, is a much better way to study and show off your skills. (It's also a good idea to attach the Git URL of the project you think is the best and a brief summary of the content later.)

Personal recommendation: ⭐️ ⭐️ ⭐️ ⭐️

3️⃣ Obtaining Various Certifications
There are various certifications related to development, such as SQLD and OCJP. Occasionally, you'll see questions like, "Is it helpful to get a SQLD for a developer position?" I, and most developers, think that only the "Information Processing Engineer" certification is necessary for developers. (There are probably many people who don't know about other certifications.)

Depending on your education level, there are Information Processing Specialist / Information Processing Engineer / Information Processing Engineer certifications. If you have a higher level certification, the lower level certifications are not very helpful. If you have the experience or education level to get an Information Processing Engineer certification, it's better to get it in one go. However, if you graduated from a junior college and can't get the Engineer certification, I recommend getting the Industrial Specialist certification and then getting the Engineer certification after gaining experience.

Don't even think about anything else... It's a waste of time and money...

Personal recommendation: ⭐️ ⭐️ ⭐️ ⭐️