From "Seeing" to "Making": The Story of a Newbie Coder Who Switched from Checker to

Hello, I'm Kojima, a new coder. However, I haven't been with the company for long. After working as a checker in the Check Team within the Coding Factory Department for about a year, I moved to become a coder in the same department. I'd like to tell you the story of how I got transferred to a coder position.

Reason for joining the company

While I was studying to become a web creator who could direct, design, and code, I was looking for a job that related to that, and I noticed a catchphrase in a Monosus job posting that said, "You can see the site being created in the actual site." They were looking for staff to check the completed site. When I saw that, I thought to myself,
"That's right! Here, I can go to school and study web design while also seeing websites being made in the field! I can steal (techniques)!" I decided without hesitation that I would be able to gain good experience.

The quality of production revealed through the checking process

I started working at the company almost at the same time as I started school, working during the day and going to school in the evenings and on weekends.

Now that I've actually worked as a checker, I'm amazed at the high quality of the work I see.
Until then, the sites that came to mind were mostly old, but as I checked them out, I saw that recently there are many sites that use cutting-edge flat design, and even the fine details of the design are beautifully reproduced, and I realized that this is the way things should be.

I also remember thinking, "Well, if I were to make something of this level quickly on my own, I'm nowhere near that level." (Well, to be honest, I still feel that way...)
However, I think this is because I still have little experience, so I tell myself that if I study hard, I'm sure I'll be able to do it, and that I'll be fine if I keep learning.

Checking work and its rigor

Just the word "check" sounds easy, but in reality, checking is a tough job that requires detailed confirmation. We check from the user's perspective, assuming that the person viewing it does not know the HTML source or structure.

We check every detail to make sure that everything is accurately reproduced, including the commonly visible parts, font size, 1px misalignment of images, and rounded corners.
Moreover, you have to check dozens of pages a day, and for large projects up to hundreds of pages, with the same quality, so it requires stamina.
It is extremely strict that the coded page must match the design exactly.

However, that is why we only have high-quality products.
This allows us to maintain high quality within the company.
So everyone is inspired.
So we're going to adopt more advanced technology.

I felt that this created a virtuous cycle.

In addition, we work closely with other checkers to compile the check results, even for minor details, and check with the coder if we have any questions, allowing us to carry out more precise checks.
In fact, we sometimes hear coders say things like, "Huh? That's off here!?" or "You're actually looking at this much?"
They also uncover issues that the production team may not notice, as well as differences in behavior between browsers and devices, so I think the quality of the checks is very high.

Moving from checker to coder: full of hope and anxiety

After about six months of working at the company, I began to get the hang of checking small to medium-sized projects.
Two months later, all of my classes at school had finished and I was nearing the end of creating a simple website on my own.

At that time, I was seriously thinking about what I wanted to do, asking myself, "What do I want to do? Should I continue working as a checker and do some independent coding?" I was busy asking coders what I could do there and looking at job-changing websites.

Meanwhile, from the coder,
"If you work here, you'll be involved in actual projects, so your technical skills will definitely improve."
After receiving this advice, I became more determined to stay in this environment and believe that it would definitely be beneficial for me.

However, I thought about it for about a month, wondering how I could change from a checker to a coder, since there had never been a model for such a transfer before, and wondering if my only option was to quit Monosus and find another job.

One day.
From Coding Factory Division Manager Ito:
"Oh, Kojima-kun, you'll be a coder starting next year!"
And then, as we passed each other, he said something shocking.

I shouted in my heart, "It's here!"

However, I was skeptical about my abilities and wondered, "Can I do it in my current condition?"
Despite this sense of urgency, I tried to become more familiar with coding by looking at the source code as much as possible when checking.
However, he is still a novice in this area.
Even though I could check the source code using developer tools, when it came to actually coding, I would get confused about where the code should go, and due to lack of knowledge and experience, I could only do a rough check.

I myself have already worked as a checker at a coding factory, so I understand the quality control aspects of CF and feel some pressure.
I'm already used to checking things in production, so it's just my habit to notice even a 1px misalignment.
This means that coding takes longer, but that may just be because production is slower.
That being said, if you focus on improving accuracy rather than speed, I think you will naturally increase your speed. This will not only help you meet the deadline, but also reduce the amount of work required for corrections.

First, to improve accuracy, you need to look at many websites to recognize patterns. In addition to looking at the source code, you also need to look at the entire website and write down any points that seem to be broken, and you also need to practice coding repeatedly.

The skills of a checker can be utilized as a coder

The main purpose of a checker is to check for mistakes; they are not simply there to "have someone take a look at something that's in the middle of production."
The checkers don't just look for mistakes made by the coder, but also notice points that the customer should confirm, such as "Is the look and movement of this part really okay?" and communicate these to the coder, building reassurance one step at a time.

I think this is a necessary skill for any coder.
There will probably be things you check before production, and things you notice and check after production has begun, so the practice of "always asking questions and eliminating anxiety" will come in handy.
In addition, both the checker and the coder have a common awareness of understanding the intentions of the person being requested, which I believe helps prevent problems from occurring.

Here is a summary of the similarities between checkers and coders.

It's about naturally creating an environment where the production progresses while taking into account various intentions.

Also, checking skills can be applied to coder skills.

is.

What I have realized at this stage is that they are able to check themselves and have the awareness to eliminate mistakes by questioning themselves.
I plan to gain a deeper understanding once I get involved in an actual project.

The first step as a coder

Finally, in May, I was transferred to a new location and a new desk. I was familiar with the atmosphere and most of the coders around me, so I didn't feel any discomfort or confusion.
This is where my journey as a coder really began.

Now, let's get ready to get started!
I would like to say that, but to be honest, I am nervous because I have a written test on the coding guidelines implemented by the department, which will be the criterion for whether I can get a job or not, and a practical test on creating something based on that.
(I have a test coming up at the end of this month, so I'm going to give it my all.)

However, the good thing about Monosus is that it "never leaves anyone alone."
I really appreciate the advice and comments I receive from my seniors. Even though the senior coders around me are working seriously, they sometimes have fun conversations and laugh out loud, and the good atmosphere makes me feel a little better.

I would like to take this opportunity to express my sincere gratitude to Director Ito for giving me the opportunity to get closer to the web and broaden my horizons. Thank you very much!

What we aim for from now on

My immediate goal is as I mentioned earlier, which is to gain a solid understanding of the basics and then produce something.
First, I want to reach the benchmark and then decide on my direction.
Looking at the big picture, there are various roles such as coder, direction, planning, sales, etc., so you will naturally decide the direction you want to go in.
There are still many new possibilities ahead, so first I need to improve my quality as a coder and become a fully-fledged professional.
I'm looking forward to broadening the scope of my abilities.

Now, the dawn of my new life begins! I'll do my best!