Working diary as a Front End Developer
Nguyen, Chi (2025)
2025
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2025052315478
https://urn.fi/URN:NBN:fi:amk-2025052315478
Tiivistelmä
The subject of this bachelor’s thesis was to report the result of the author’s working days at Trafore Oy as a full-time Front-End Developer during a period of 8 weeks. In this working diary, the author discusses about her daily tasks, obstacles and solutions to those challenges. Additionally, the diary covers supplementary responsibilities such as invoicing and SSL certificate management, giving a broad view of diverse demands. The tech stack for this job includes HTML, CSS, JavaScript and 4D Language.
The methodology includes daily documentation of the author’s responsibilities in various projects, which require the integration of front-end with back-end technologies, specifically relational databases. The diary also presents records of managing administrative tasks such as invoicing and overseeing SSL certification. This approach offers insights in both technical and administrative aspects of the author’s role as a front-end developer in the company.
The working diary was written in around 6 months, which consisted of 8 weeks of active weekly documentation and extra time for polishing and discussions with thesis supervisor. The result emphasizes the importance of efficient code structure, as well as the fact that detailed records of the web development process can enhance problem-solving efficiency and the author’s professional improvement. The findings also highlight the necessity of being flexible within an organization, especially a small sized company, to speed up the operation process to meet customers’ needs.
The methodology includes daily documentation of the author’s responsibilities in various projects, which require the integration of front-end with back-end technologies, specifically relational databases. The diary also presents records of managing administrative tasks such as invoicing and overseeing SSL certification. This approach offers insights in both technical and administrative aspects of the author’s role as a front-end developer in the company.
The working diary was written in around 6 months, which consisted of 8 weeks of active weekly documentation and extra time for polishing and discussions with thesis supervisor. The result emphasizes the importance of efficient code structure, as well as the fact that detailed records of the web development process can enhance problem-solving efficiency and the author’s professional improvement. The findings also highlight the necessity of being flexible within an organization, especially a small sized company, to speed up the operation process to meet customers’ needs.