> You're not meticulously stacking the last card on top of a 10 ft house of cards exhibit where tens of hours of work will be completely lost if your concentration strays to show your face to another human being and utter a few words.
You have no idea.
Thank god we have this WFH thing now. I can build this house of cards without anyone interrupting me saying I'm not building a house of cards.
But really, as a software engineer you should not be building a house of cards, right? Surely you should not boldly insist that you never be subjected to collaboration from other members of your team because you are intent on building a system that is in constant danger of collapse.
In my experience, the house of cards is usually debugging, not building. I've had to do some pretty crazy debugging, stepping through deep call stacks frame by frame, keeping track of big data structures as they change along the way. This can take a huge amount of focus that would absolutely be ruined by even a 5 second conversation.
I fully accept that programming is purely a mental task. I choose to think with others and then code in my own time. The tasks are now so short that there is literally no space for someone to interrupt.
I don't think the suggestion is to "never" be subjected to collaboration, but certainly there should be a balance between collaboration and deep work that shouldn't be interrupted if possible.
You have no idea.
Thank god we have this WFH thing now. I can build this house of cards without anyone interrupting me saying I'm not building a house of cards.