The most fun you can run into in these instances are when your content is separate from your application and the business tracks you down as a developer to fix all the textual issues that eventually resolve back to poor content. It's even better when it happens and they call a meeting to discuss whether the content should remain as it is, as that's the original state of the content and they may not be able to change it due to copyright or contracts, or if they should attempt to update it, which means it's subject to reverting any time there's a content change/update. That last option is the best, as every time the content changes you get the same work item all over again, but for a new support developer who doesn't know the history of the problem.
Snrky: He cc:ed our manager to make me hurry up. I cc:ed his director. He cc:ed my director and both VPs. And then the CTO got involved. I guess he's serious about that apostrophe-s in the UI.
Title: It's good to feel ownership over the Terms of Service page
No comments:
Post a Comment