So other than following up on shit that should have been done but wasn't, sifting through miles of forwarded emails (all with full quote below a statement saying "my comments in red” or “+cindy”), and cursing Slack "threads", I spend a good chunk of my day juggling Jira tickets.
So much of our work is ticket driven, yet many of us seem to lack basic best practices and habits that could make our (ok: my) life a lot easier. So let me present a quick primer:
Essential Ticket Skills - just because Jira sucks doesn't mean you have to!
(Note: most of this applies equally to Bugzilla, GNATS, or whatever bugtracking software; I just happen to use Jira at the moment, so that's what my examples are based on.
And don't you fucking start with Trello or sticky notes and "swimlanes". Those can fuck right off here.)
Slack has been detrimental to my productivity; it seriously induces ADD. Let me rant for a moment...
When it works well, online chat allows for immersion in a team or group and absorption of tribal knowledge merely by hanging out there. I don’t know what specifically it is about Slack, but it seems to implicitly discourage this.
First: sooooo many channels. Right now, there are >50 security-related channels in our Slack. People are only half-jokingly asking if there should be a channel where it's on-topic to ask which channel to ask a question in.
Most users get a minimum of at least 10 mails a day or so that all basically say "click here, then log in" *and that are legit*. They're continually being _trained_ to do this.
Instead of phishing them (with overwhelming success, of course), we (the industry) should make sure that (1) clicking on things doesn't pwn you, and (2) legitimate mails are obviously legitimate.