Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
How do you guys deal with interruptions / task-switching while you're deep into something?
Generally I don't mind quick interruptions if someone needs help with a shell command or a library, or some other quick ask.
But I had four full new priority tasks/tickets come my way yesterday, and for each one I had to pop open a separate workspace and juggle a separate conversation.
It's not the end of the world, but whenever I'm forced to juggle multiple tasks, I find I end up frozen and frazzled while I try to recalculate my priorities.
This is partially my fault, since I've sort of situated myself as the devops guy for a few systems, so I get regular tickets as well as systems/data tasks.
Any tips? Preferably I'd still receive the tasks, but just deal with them better.2
a tale of daily frustration:
*yup I'm up-to-date ...*
git add -p .
*hack in beautiful patch ...*
git status -bs
*correct branch, didn't forget any files ...*
git diff --cached
*yep, that is what I mean to commit ...*
git commit -m"[TKT-NUM] Meaningful commit message"
git log -p -1
*double-checking ... looks good ...*
git push remote tkt-num-etc
*for a brief moment feel accomplished ...*
*notice typo in commit message ...*
I don't have a funny image or punchline to sum this post up. But know that if you recognise this feeling, then I am your brother in git.6
Share your look-busy scripts
I'm talking about some script, or command(s) which output impressive garbage to the screen. For instance, `tree / | od` or `ping google.ca | xxd` might be enough to dazzle an executive, but to really ensnare a fellow dev, you need to get a bit more complex.
So let's see those scripts! From stupid simple, to application-level complex, I wanna see 'em all! :D11