Used to do DevOps before they even called it that way: Linux. Python. Perl. Java. Docker. For fun and profit. CTO level generalist working for a mid-sized tech-centric company.
Dresden, Germany
This possibly should include all kinds of notifications, at least once in a while in order to stay focussed. Disable notifications. Shut down apps that don't support disabling notifications. Mute your phone(s). But make sure this works in your environment and your corporate culture. Actually, making the shift to a working mode where this kind of uninterrupted work is possible might not be trivial and something you don't start just by "virtually going offline". ;)
Used to do DevOps before they even called it that way: Linux. Python. Perl. Java. Docker. For fun and profit. CTO level generalist working for a mid-sized tech-centric company.
Dresden, Germany
This possibly should include all kinds of notifications, at least once in a while in order to stay focussed. Disable notifications. Shut down apps that don't support disabling notifications. Mute your phone(s). But make sure this works in your environment and your corporate culture. Actually, making the shift to a working mode where this kind of uninterrupted work is possible might not be trivial and something you don't start just by "virtually going offline". ;)
Your last statement made me laugh :).
Maybe I distilled the post too much, but in one of the drafts I had something like:
"Your team lead should be the one dealing with the interruptions and external communications. The hard life of the team lead."
Thanks for the comment!
Dan
You're welcome. Yes... the hard life of the team lead. That's pretty much it. ;)