One month after joining the company, what a newbie can see about Coding Factory

My name is Kimijima, and I will be writing this article.
I became a member of Coding Factory (abbreviated as CF) in January 2016.
I'm a brand new Monosus coder who doesn't know what to do yet. So, I would be happy if I could take advantage of this opportunity to examine how CF looks from the perspective of a newbie.

Training, daily schedule

09:40 Arrive at work

The start time for work is neither too early nor too late, so it's just right for me, who is not good at mornings.

10:00～ Morning assembly

There is a morning assembly every day.
The role of moderator will rotate between each person.
"Today's Word" is a short story from each department leader about work and daily life. It's a very helpful story that will give you more perspective and open your eyes.
So, today is off to a good start.

10:30～ Check training

Monosus has something called a check team.
New recruits will be trained on the checking team. Checking involves checking the websites created by coders, such as whether images are displayed properly, whether there are display issues on each browser (IE, Chrome, Firefox, Safari, etc.), whether there are display issues on various devices, etc.

12:00～ Lunch

You can go eat around the station! You can buy it at a nearby convenience store! You can bring your own lunch! We also have a company cafeteria on Wednesdays and Fridays! You can eat alone or with someone! It's an exciting lunch time.

13:00～ Check training resumes

We will resume check training after lunch.
The coder is informed of the areas that were checked. If there are any problems, they are corrected and the code is checked again.

~19:00 Training ends

My eyes were itchy at this time of day. After all, checking things requires concentration. I used some eye drops to make them better.

19:10～ Return to work

There is tomorrow. Taking care of your health is part of your job. Be careful on your way home.

After repeating this training for several days, Monosus' new coder had a thought.

It's amazing to have a check team!
The people on the check team are amazing!

I've been a coder for a long time, so of course I've been checking things myself. That's why I thought it was amazing!
I think the checking process is basically looking for mistakes.
It seems easy, doesn't it? It even seems fun. But what happens when you go through 50 pages, 100 pages, 1000 pages, and then more and more...? You spend your entire working day looking for mistakes. You can't make mistakes, you can't make mistakes.
Of course, this was a task done by the human body. My eyes lost moisture in inverse proportion to the concentration I maintained while staring at the monitor. My limited patience was gently sustained by lunch... so, what am I trying to say? I've never been so careful in checking things before... I honestly reflected on my actions and felt grateful.

That was in October 2015, before I had even become a new coder at Monosus.
On the day of the interview, I was reading Monosus' company profile in a stylish building in a residential area a little way inside Yoyogi.
The part that caught my eye was the explanation of the coding factory.

This is a service that provides HTML+CSS coding that complies with web standards. Because we have absolute quality, we do not charge you if there are any mistakes. From mobile to large-scale projects, we will use our accumulated know-how to provide services that will satisfy all our customers.

Company information materials given at the time of the interview

It's one part of the above sentence.

If there are any mistakes, we will not charge you. * 1
If there is a mistake, there is no charge.
If there is a mistake, you won't be charged...

I said to myself, quite emphatically, "I wish I could have it."
In fact, I think I even asked the interviewer, "Aren't you going to get it?"

I was reminded of this during my training.

However, if we look closely at the previous sentence,
"Because we have absolute quality, we don't charge you if there are any mistakes."

Because of the absolute quality,
Because of the absolute quality,
Because of the absolute quality...

Absolute quality can be interpreted as "standardized high quality".
Huh? "Standardized high quality..."
Not only is it of high quality, but it is also standardized. The average score is 100 points.
50 pages, 100 pages, 1000 pages, and then more...and then more...an average of 100 points.
This is really hard work for both the people who produce it and the people who check it.
Still, let's change our perspective and think about the people requesting the production.

thought the new Monosus coder.

If you're going to put a lot of effort into making something, you want it to be something that will make someone happy. You want it to lead to something new. But to be honest, you still can't shake the thought, "I wish someone would just give it to me."

But eventually, I thought to myself, "I want to become a coder with solid technical and human skills, who can honestly say, 'I won't charge you if there are any mistakes, because the quality is absolute.'"

And I hope that this mindset will continue.