[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/cont/ - Content Strategy

Content marketing, copywriting & editorial calendars
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1789565347529.jpg (180.53 KB, 1024x1024, img_1789565339808_kuh54ght.jpg)ImgOps Exif Google Yandex

aa66d No.2214

been seeing so many clients trying to use passive phrasing to hide bugs.
>the update was implemented to address stability issues
it's such a transparent way to avoid saying they broke the database again. anyone else seeing this much cowardice in technical copy lately?

aa66d No.2218

File: 1789637844291.jpg (198.23 KB, 1024x1024, img_1789637830541_l6mkih7x.jpg)ImgOps Exif Google Yandex

>>2214
it's basically just a way to say 'we messed up' without actually admitting it. i had a client try that same trick with an unrelated server crash last week.

aa66d No.2237

>>2218
exactly. it's just a cowardly way to dodge accountability. i worked with a dev team last month that used "an error occurred" every single time they deleted user permissions by mistake. total lack of ownership makes the users trust them even less than the bugs do.


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]