Have you ever thought how much time do you spend waiting on your code to compile? On your local development server to reload or refreshing your browser for some UI change in your code?
I've been thinking about it a lot for past few days, because it bothers me to spend time just waiting and looking on spinning loaders.
Yeah, sure, there are things like hot module replacement to boost your productivity, but that's NOT what I want to talk about.
I want to talk about the question - How much time do I actually spend waiting for these things every day. And sure, I've been thinking how to measure it.
What if I made an app to measure these reload times, on the server-side (your local server) and client-side (in the browser). Which could show you at the end of the day that you spend 38 minutes just waiting for your code to compile? Would you be interested in using it?
There are some other interesting things you could get from the data, like automatically measuring your time in work, which is another thing I would like to know.
You might be wondering about the technical implementation. I can explain it in another post if it has shown to be interesting.
Oldest comments (2)
Android Studio would not be pleased
App might be an overkill in my opinion. But that's just me. I usually keep track of how much time a build is taking and how many builds I am doing in a day and get an average time spent building. Yesterday, I did the same at work and turns out I am spending roughly an hour just building. Which is a lot. Build times tend to creep in, gotta keep them in check.