Please note that the daily activities will vary for software engineers. Here, I'm going to tell you mine :) First of all, to give you more background, I'm a software engineer, to be specific, I'm the frontend developer. I'd things related to the user (interface, user experience, and something that users see on a product).

I usually wake up at 5 or 5.30. Typically I do workouts or small exercises in the morning, and a light breakfast will follow it. Today's breakfast is not fancy. Only a bowl of cereal with fresh milk that I bought yesterday.

This is my first meal of the day 😁

After finishing the breakfast, I will take a shower (if I'd workout 😬)

I usually start the day at 9 or 9.30 by checking GitHub and email. I'll see if there is a new pull request, issue, or task I am assigned to. Sometimes I do a review of the pull request my peers made, and occasionally I'm also being reviewed. Oh ya, for those who don't know, a pull request here is when a developer is ready to begin the process of merging new code changes with the main project repository. So it's more like code checking or code reviewing before it's finalized and merged. We do this to make it easier when working on the same projects.

At 10 or 11 AM, usually, my colleagues will arrive, and we start the day with the daily catch-up. After we present the update, we'll continue to code new features or fix bugs until lunch is ready. Btw today's lunch is nasi padang guguak, our favorite go-to meal when we are confused about what to eat 🤗 

Psst, it is very tasty and delicious 😋😋

Post lunch will be mostly the code hour 🧑🏻‍💻🧑🏻‍💻. I am focused on my weekly task. Sometimes I can finish daily code early, but most of the time, I am stuck in an issue for the rest of the day 😅. Until the next day, I realized that the problem was only a semicolon or something thing that was very absurdly unexpected. So which one is more often then? I don't have any idea, like this meme.

At 3.15, when starting to get frustrated, founding a hard issue, don't know how to solve it, and got really confused with it. Later then you will be questioning yourself why you became a programmer and why the hell you still stick into it. Then, of course, the thoughts come more often as you begin to debug and think of it. BUT, once you find a solution, you immediately will feel that you are the best engineer in the world, and you are really proud of that 😎. Anyway, this quitting phase will often come when you start coding for the first time. But, to be honest, it was only just in the past for me. Right now, I just accept it and don't think of quitting anymore 😁

When about 6 PM, I usually almost complete the day's task. If not, I will continue to finish the feature that I'm working on. This can take a lot of time, depending on the task's complexity and familiarity. Sometimes I also deploy features or fix the bug in the afternoon on some occasions. And after deployment, I will just standby if there is a crucial bug that needs to be fixed asap. At the end of the day, I will be chilling and joking around with my workmate during dinner -btw dinner is also provided here- before I finish the job.