3 ms·

Thank you for this comment, it is very insightful. It's also interesting how perception of these bottlenecks differs. I wouldn't care much if tests are running

Thank you for this comment, it is very insightful. It's also interesting how perception of these bottlenecks differs. I wouldn't care much if tests are running 30% slower, I run them in the background from my editor anyway. I usually tidy up stuff in the meanwhile or git stage some lines (which needs to be done anyway). However, if an editor has a higher latency than I am used to, it drives me crazy.

anarazel 9y ago
> It's also interesting how perception of these bottlenecks differs. I wouldn't care much if tests are running 30% slower, I run them in the background from my editor anyway. I usually tidy up stuff in the meanwhile or git stage some lines (which needs to be done anyway). Heh. I do that too, but I'm anxious enough that I rerun tests after finalizing the commit. I'll still use the time for the tests to finish to do another read through the commit, but especially when pushing to many supported branches at the same time, tests still take longer (work on a pg, which has 5 years of supported back branches...). > However, if an editor has a higher latency than I am used to, it drives me crazy. Oh yea, but I wouldn't use a web based editor, ever ;). The point I was trying to make was less about something as central as an editor - where I spent a lot of my time, fighting for first place besides terminals - but more around secondary non-critical path stuff like IM.