|
|
|
|
|
by dsr_
1312 days ago
|
|
I know a person who was a technical customer service manager (for a very technical product) and a general-purpose writer. She now writes the customer-visible bug-fixed notes for a very large, very technical software product (with minor releases on the order of every 4 weeks, and major releases annually). A good bug takes 5-10 minutes to write up in an appropriate, customer-friendly, legally and security-appropriate way. A bad bug might take hours of tracking down engineers who did the work, claimed they did the work, mis-tagged the bug entry, improperly closed the bug, improperly left the bug open, improperly merged the bug... But at the end of the day, she isn't responsible for fixing the bug, just documenting it properly. The workday is essentially 9-5. And there's always another bug. |
|