27

analysing a database problem and writing a 4-line fix: 5 minutes.

preparing a foolproof manual for the manager on how to apply the fix: 15 minutes

writing a manager-level explanation what the fix does: 30 minutes.

explaining it to the manager: 30 minutes.

writing a _detailled_ explanation why we need the fix: 60 minutes.

explaining it to the manager again: 30 minutes.

figuring out why our progress is slow:

_priceless_

Comments
  • 9
    Stop explaining things to managers....
    Do you trust me? No? then fix it yourself.
    You do? then no need to explain.
  • 4
    @magicMirror well, in the end, that only creates bigger problems. because if the fix doesn't go out today, it'll break something bigger later on. and that will require exponentially more explanation time, and to multiple people. who have even less a clue than the manager
  • 1
    @tosensei Then include the label

    VALID UNTIL 2022 JULY 26, DO NOT USE IF EXPIRED! If not applied until this date, request an updated version from @tosensei or other db technician familiar with <project>

    Of course, the manager needs to be able to read English and trust you enough to accept something as unusual as an expiry date on software
  • 2
    I like to mimic consumer products in the verbiage of instructions directed towards nontechnical personnel, because that's the phrasing every soul in a consumerist society learns to interpret.
  • 1
    Stop after fool proof manual.

    All others : it's magic
Add Comment