from Hacker News

What labels would you use to classify time spent at work?

For example a really simple (unrealistic) labeling for someone whose only job is to write source code in one language, for one project, on a "normally" structured team. Labels = Programming, Debugging, Meeting, On-Break. (For the sake of the example, I'm excluding all other common tasks programmers are expected to perform)

Of course many people's jobs have a lot more scope than this example, so I'm curious how you would classify your own work.

I'm asking because I'm trying to get a better handle on how I spend my time at work by classifying chunks of time spent on different tasks. While the core of my job might be "shipping code", there are many work items and projects that might involve very little "shipable code". So when I have days that don't involve "shipping code" it can be hard to .

For context, I currently work as a "software engineer" and my team and role have a pretty wide-ranging scope from maintaining/writing APIs and Web-Apps, to creating new infrastructure. So, I'm curious how my first classification scheme (which I won't share to avoid bias) compares to other people in different roles.