|
It depends on why. Some days you'll find yourself in meetings, reviewing code, and emailing/messaging others, but not writing code. You should recognize that this is work, and you should ask yourself whether this was the best use of your time. Which it may or may not be. Ask yourself, was it useful for you to attend the meetings and have those discussions? Other days, you'll find yourself investigating how to do something, or starting down a path only to realize it's a dead end, and so have nothing to show for it. It's also work, and the best way to manage this is to document what you've tried, and time box work to make sure you don't waste too much time. Other times, you won't know what to work on, or feel lacking direction. In my mind, the best way to deal with that is just talk to people - your manager, peers, etc., about what you are trying to do or what to work on. |