Security card
From ym2149.org
- https://www.reddit.com/r/ExperiencedDevs/comments/1bx7x6s/missing_context_on_tasks_is_a_huge_deal_breaker/
- security related tickets are the worst for this - certain individuals insist they can play the security card and bypass prioritisation/planning because 'security is important' to keep development busy for a month with work that doesn't otherwise appear to have value for the business or customers. normally i'd call that negative work
- of course security is important, so surely it's not too much to ask for somebody to take 10 minutes out of their priceless time to add a bit of context to the ticket, to help development learn. if they understand why they're doing something they'll get on board! they'll help!
- perhaps rubbish like this comes from context being dropped by some authoritarian link in the command chain. there's a ticket template that goes as an x i want y so that z - i used to think it was dumb, anyone is capable of writing good tickets without that template. i was wrong, so very wrong
