What do you do during re (build | deploy | start) ing?

Question

What are some good ways to spend time waiting for my project to recover / redeploy / restart?

I'm not interested in suggestions on how to shorten the waiting time. I know that there are many tools, principles and methods to avoid endless waiting times. But still, several times a day, I have to wait until some of these things happen.

Suggestions:

• The visit ...
• Reading a little bit from a book
• Email Scan
• Communication with colleagues
• Getting coffee

In my opinion, not all of them are really useful. There is always the danger of being so distracted from your real work that you will miss important details and make mistakes that can cause additional waiting cycles.

What works well for you?

Answer 1

Required:

Answer 2

I really go over to stackoverflow during build time.

Answer 3

Build faster.

Answer 4

I look at the build progress on my right monitor and on the stackoverflow.com panel on the left. If it's a big assembly, I can go for a cup of coffee.

Answer 5

Twitter You will learn a lot in the river.

Answer 6

I cut my wrists. Honestly, one of the teams here has code analysis for their projects; they do not pay attention to one warning. Do you know how long it will take VS to analyze these warnings (about 24,000 in total - it takes 3 minutes)?

Honestly:

• Take the smoke.
• Get food
• Visit SO
• Do something in another project (most often in a home project)

Answer 7

Plan the next steps. Chart, write, sketch, fill out the to-do list. Get ready for the next action.

And relax a bit.

Answer 8

actually Stackoverflow and IRC, whether at build time or not!

Answer 9

Review your code, think about problems that you can improve and subsequently rework. A day of programmers without rework is almost a lost day.

Answer 10

Check CPU temperature, weather forecast, latest Eve learning skills - typically play with widgets on your Mac control panel.

Never, never skip to watching, as I forgot what I'm doing ...

Answer 11

Wait and, if possible, think about the next problem.

If you are at an early stage of development, there will be errors that need to be fixed.

Later - if you are not doing a complete rebuild - compilation time should not take so long.

Everything else will be distracting.

Answer 12

I often do what you offer (especially visiting Stackoverflow and reading a book).

However, since it takes time to create and deploy, no matter what you do when you return, you probably lost your mind. Thus, you do not need to minimize the time spent on these things, but you need as little as possible. Thinking about a problem / error is much more productive than actually starting the system for debugging.

Answer 13

Rollback or scan. It takes a very small processor, and both are step-by-step, so I can save and go when my actual work is ready to work again.

Answer 14

I run it on one monitor and do some coding or reading on another.

Answer 15

Watch the window and relax your eyes ... you can also close them but not fall asleep

Answer 16

I follow the GTD style of task management. I do not check emails, process documents (physical or digital), plan or answer the phone (if it is important, they will leave me a message for verification), while I focus on coding. I choose very specific intervals, time of day, to do these actions.

With that said, I would advise you to take the time to spend on assembly expectations to do these things. Do not mix them with development time. Take a wait while creating your interval for processing and scheduling inboxes.