2 ms·
So the thing about task switching is, everyone is bad at it. And the studies indicate that people who think they’re good at it are even worse at it.
by bunderbunder 8mo ago
So the thing about task switching is, everyone is bad at it. And the studies indicate that people who think they’re good at it are even worse at it.
- falcor84 8mo agoI was responding to: > It’s even worse than the bad old days of long compile times because at least then I could work on tests or something like that while I wait. To me it seems like the exact same context switching situation that it always was.
- kaffekaka 8mo agoNot exactly maybe. Different worktrees can still lead to possible merge conflicts later. This may get messy. Working on tests during compilation seems like a more separate task.
- bunderbunder 8mo agoIf I’m writing tests and implementation for the same problem, there isn’t so much context switch. Same business domain, same domain model, same API, same contract and invariants. I’m just switching between taking the measurements and making the cuts. Which is a smart thing to do anyway because you can accumulate a lot of need for rework very quickly if you make a bunch of cuts in a row without stopping to confirm you’re making them correctly.