Diary thesis of a Java Developer
Barreto, Diego (2024)
Barreto, Diego
2024
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-2024051210991
https://urn.fi/URN:NBN:fi:amk-2024051210991
Tiivistelmä
This is a diary thesis of a software developer where the author will express his work experience and intends to provide a personal perspective of the work process which conveys working in the field. The intention of this document is to provide effective insights into the process experienced by software developers and the nature of the work itself, and this thesis intends to provide a valuable source of information where new software developer can gain important knowledge and understanding of what it is like working in the IT field. Through this document, it is expected that the reader will be able obtain a deep perception of the technical knowledge and soft skills required in order to excel effectively in the workplace.
This thesis proposes to explain the daily process of a software developer who recently started working in the field. The thesis consists of the introduction, work description, diary entries, and conclusions. The primary focus of this thesis are the diary entries, which covers an 8-week process with daily and weekly updates. The author provides daily entries detailing his personal journey and the work performed during this period. In this entries, the author explains his daily progress and provides relevant information such as the difficulties found, and how those difficulties were approached and solved. These entries includes not only the technical perspective, but also the personal perspective including the process outside coding such as the communication with stakeholders and the various challenges which faced during this process.
At the end of each week, the author will explain theoretical concepts which are directly related to the topics covered during that week. This will enable the reader to link and relate the work performed and the technical and theoretical concepts. For those conclusions, various topics are covered, and the author will attempt to demonstrate how these topics are interconnected. The aim is to help the reader find coherence and understand the importance and relevance of these topics in software development. Furthermore, in the concluding part of this document, there are final conclusions and pertinent recommendations provided for the reader to consider and analyze. These conclusions are not only related to technical knowledge but also to non-technical skills such as team work, communication and professional development.
This thesis proposes to explain the daily process of a software developer who recently started working in the field. The thesis consists of the introduction, work description, diary entries, and conclusions. The primary focus of this thesis are the diary entries, which covers an 8-week process with daily and weekly updates. The author provides daily entries detailing his personal journey and the work performed during this period. In this entries, the author explains his daily progress and provides relevant information such as the difficulties found, and how those difficulties were approached and solved. These entries includes not only the technical perspective, but also the personal perspective including the process outside coding such as the communication with stakeholders and the various challenges which faced during this process.
At the end of each week, the author will explain theoretical concepts which are directly related to the topics covered during that week. This will enable the reader to link and relate the work performed and the technical and theoretical concepts. For those conclusions, various topics are covered, and the author will attempt to demonstrate how these topics are interconnected. The aim is to help the reader find coherence and understand the importance and relevance of these topics in software development. Furthermore, in the concluding part of this document, there are final conclusions and pertinent recommendations provided for the reader to consider and analyze. These conclusions are not only related to technical knowledge but also to non-technical skills such as team work, communication and professional development.