April : Work Review

A quick review of my work in April.

2024.3~2024.4 is my first month in the new company, I haven't updated my blog for a while since I am busy. I am taking advantage of the Labor Day vacation to record my work.

In April, I did the following things

• Familiarize myself with the company's products and structure.
• Use JavaScript and Java to do front-end and back-end data connection and communication, total development and modification of four functions.
• Setup RabbitMQ for data flow.
• Setup Nginx for Linux remote server redirect.

There are some challenges, and I learned a lot.

Facing the unknown

Some of the frameworks and technologies I haven't used before, and how to find the right resources to solve the problem within time is important. If I can't solve the problem, I can record the process of trying, and set a time limit for myself to try it out myself, so I won't delay for too long. If the time is up and I can't solve the problem, I 'll ask for help from my coworkers.

Structure

Before the development, think of the structure, such as how to connect the data. Try to find the core the concept behind it, and the logic of code itself can be resolved after understanding the concept.

Communication

How to discuss the requirements clearly before development with PMs and think about the possible exceptions or blind spots beforehand. If the possible problems of the requirements can be confirmed before development, we can save a lot of time.

Most of the focus is still on how to quickly clarify the problem to be solved. Once we know the direction we can have better idea of how to execute.

Simply record it.

快速的紀錄一下 4 月的工作

2024.3~2024.4 是在新公司滿一個月，因為真的太忙了，有一陣子沒更新 blog ，趁著 51 休假的空檔來記錄一下新工作的心得和遇到的狀況

4 月份大概做的事有

1. 熟悉公司產品和架構
2. 用 JavaScript 和 Java 做前後端資料的串接與溝通，總共開發和修改四個功能
3. 架設 RabbitMQ，設定資料流，參考資料
4. 架設 Nginx，設定 Linux 遠端 redirect，參考資料

其實還有遇到一些挑戰的事，但也學習到很多

面對未知

遇到一些沒有碰過的問題，大部分是框架和技術沒用過，怎麼在時間內找到對的資源把問題解決，如果不能解決也能把嘗試的過程記錄下來，給自己訂下嘗試解決的時限，別把問題拖太久，如果時間到無法解決就勇敢求助同事

架構

在開發時如何把架構先想好，例如資料怎麼串接，先把最簡單的框架跟概念實現出來，邏輯可以等架構解決之後再處理

溝通

在開發前如何先把需求討論清楚，把可能的例外或是盲點提出，如果可以在開發前把需求可能遇到的問題確認好，會減少很多意外發生，省下很多時間

大部分的重點還是放在怎麼快速釐清要解決的問題，知道方向之後才比較好執行

簡單記錄一下囉