Hello, I'm Matsubara, a coder.
Strictly speaking, I'm now mainly in charge of a different job, so the title on my business card has changed to Director.
I will explain more about that later, but today I will share with you, as a mid-career member who has been with the company for five years, the memorable experiences I had at Coding Factory (hereafter referred to as CF), in the form of "My Coding Factory Incidents."
Even though I'm a coder, I go on business trips.
Travelling to Nagoya, Osaka and Fukuoka for seminars.
CF has held many seminars so far. After I joined the company, we held the "Coding Guidelines Seminar" from 2013 to 2014, and the "Responsive Web Design Seminar" from 2014 to 2015. I accompanied these seminars to Nagoya, Osaka, and Fukuoka as a support staff member.
Department manager Kojima took the stage.
To be honest, I never thought I'd have to travel so much after becoming a coder.
I was mainly in charge of the reception. You might think that reception is just about taking names and checking people in, but all the venues were thankfully very busy, so I did thorough simulations and preparations beforehand.
In addition, the lecturers at the seminars are also active coders. While listening to the lectures of the senior coders I always work with, I fantasized, "I wonder if one day I will be able to speak as a lecturer in such a large venue in front of a large audience." However, in reality, the lecturers at the seminars are not fixed, and a new coder takes on the role of lecturer every time.
I have extreme stage fright, so if something like that were to happen I think it would be extremely difficult, but I think it would still be a very valuable experience.
A busybody who loves coding.
Become responsible for training new employees.
Just as I was starting to get used to working on projects on my own and figured out my own way of working, or the tricks of the trade, I looked around and noticed that there were just as many junior coders as senior coders, and before I knew it, I could no longer just work thinking about myself.
However, since I'm an engineer and I'm often assigned to projects alone, it may not be a problem if I only think about myself...or rather, about my own projects, as long as I can deliver the work properly. But when I do something well, I want to teach someone else, "Here's how to do it," and I feel happy when new employees ask me questions, so I talk about all sorts of things, even if they didn't ask me.
In my third year at the company, I was put in charge of training new employees.
By the way, when I was interviewing for Monosus, I was asked, "Where do you want to be in three years?" and I answered, "I like to communicate and teach people, so I want to be someone who trains the next generation of coders." I'm now living the future I envisioned back then. It may sound a bit exaggerated, but it was something I wanted to try, so I decided to do everything I could.
However, I felt more pressure than I had imagined in teaching what I had taught as a senior coder. I sometimes got emotional when a newbie made a mistake, and even though I was able to code, I was a complete amateur when it came to teaching. I thought this wasn't good enough, so I started by learning about training newbies.
After going through many twists and turns, I created some materials for training new employees. I called it the "CF OJT Set."
The contents were OJT guidelines for trainers, training plans and review sheets, and communication sheets for new employees and their trainers. Later, this incident led to me receiving the "MVP of the Month" award.
It may sound like I'm bragging, but I feel like I've grown a bit through training new employees. I think it's surprisingly rare for people to feel like they've grown as adults, but that kind of thing directly connects to motivation.
CF OJT set.
A coder who doesn't code?
Serve as a point of contact for project and technical consultation.
Now in my fifth year at the company, I work as a project and technical consultation desk.
When a customer asked for specific advice before accepting a project, our senior coders would calculate the amount of work required to create the website in between production work. However, the content of the consultations has become more diverse over the past few years, and more and more cases require more time to calculate the amount of work required. Therefore, starting this year, I will be the sole point of contact for pre-order projects and technical consultations, so that our senior coders can continue to focus on production as before.
I've just started, so I don't have much to say, but I'm sure I can make use of all the experience I've gained in Cloud Developers. Although I don't have as many opportunities to write code, I'm constantly being asked about websites that incorporate new technologies, so I need more front-end knowledge than ever before. I also create demos from time to time, so I'm studying hard every day and want to continue doing the coding I love.
Heck, he's even written a book.
Finally, I would like to report on a significant incident that should not be forgotten.
A book on CF has just been published!
In addition to detailed direction methods and practical coding tips, the book also provides a thorough explanation of how to formulate coding guidelines. This book is packed with on-site know-how, such as the actual production flow and checklists at the Coding Factory, so be sure to check it out.
I'm mainly in charge of matters related to direction.
It's not a textbook-like book, but a fairly in-depth look at things from the perspective of the field, so I think you'll be able to find answers to questions like, "What do you actually do in these situations?" Of course, I never dreamed that I'd become a coder and write a book.
Published by Mynavi Publishing. In "Web Designing," I was in charge of a serial column in CF (December 2011 issue to March 2014 issue), and also had a special feature on coding guidelines (April 2013 issue).
Conclusion
From seminars, training new employees, and even writing books to being a project liaison. Looking back, I realized that being a CF coder isn't all about coding. I think there are some people who like that and some who don't, but I get bored easily, so I quite like this kind of thing.