I am an engineer in the CAMPFIRE Community. This is Matsui.
My hobbies are watching sports and traveling. In 2020, professional baseball, UEFA Champions League, and F1 & F2 were personally exciting. My favorite driver is Max Verstappen. (I don't think anyone can tell, but I really like the combination scene with Daniel Ricciardo.)
2020 was a year of taking a leave of absence from university and challenging engineers from inexperience. Using this Advent calendar, I will summarize what I experienced, learned, and conscious in 2020.
-Almost no programming experience. (Only SQL has some experience)
-Computers and the Internet are relatively familiar. (As a user, not a creator.)
-I attend the Faculty of Arts and Sciences of a national university.
--Do rails new for the first time.
--Do the tutorial for Rails Guide.
--Become able to read the CAMPFIRE code. --Add a column for data acquisition and add date and time insertion process to the task in-house.
-Support Service code separation and service addition. --The code that was in a tightly coupled state was separated at the controller level, and the code was separated. ――Since there are some differences in the nature of services between crowdfunding and the community, we have added a support service unique to the community.
--Development of backend required for Community page design change. --The code in the tightly coupled state has been separated.
-Support service is managed in DB, and can be added and edited from the internal management screen. --In the past, it was necessary to ask an engineer to deploy for addition and editing, but now it is possible to add and edit without an engineer.
--Repaired functions of the management screen used in-house and de-libraryd. ――Since there was a flow of de-library of management screens used in-house throughout CAMPFIRE and building and migrating an original system, I was mainly in charge of migrating functions related to the community. (It is still in progress.)
――It's important to think about the organization, but I wasn't strong enough, so I just focused on myself. Focusing on myself was so diligent for the organization.
――Technology progresses quickly and new information always flows, so it is better to catch up as much as possible, but even if you catch up without the basics, the efficiency remains low and it does not lead to output, so concentrate on solidifying the basics first Did. (Especially in the early days.)
――Since I don't know where the learning is rolling, I was consciously and actively reading the PR, issue, Slack discussions and reviews on GitHub, even if they were not related to me. (And when implementing it, I thoroughly referred to it ~~ Pakuri ~~. I think that the thoughts and brains of others are external libraries.)
――It's commonplace, but at the beginning I couldn't do this and it would be a nuisance to hear, so I thought it would be better to think about it myself. However, I have come to think that it is better to ask quickly because what I do not understand is usually not solved even if I worry for more than a certain period of time (1 hour etc.). It's not annoying to hear, and even if it's annoying, it's open to the point where I can get it back elsewhere.
There are too many missing parts and issues to write, and not all of them are recognized, so I will omit them.
Thank you for reading to the end.
If you have any questions, comments, or advice, please leave a comment.
The university is going to graduate. end.
Recommended Posts