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

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1787586622296.jpg (296.9 KB, 1024x1024, img_1787586581717_dua3n3dg.jpg)ImgOps Exif Google Yandex

168e5 No.2110

fr just saw a post arguing that companies are failing at ai governance bc they rely on paperwork instead of engineering. you can't stop people from using unauthorized tools just by handing out a handbook that nobody ever opens. the only real way to curb shadow ai is to make the approved workflows actually easier than the alternatives. developers will always take the path of least resistance, sooo we need to build responsible guardrails directly into the pipeline. if the official setup is a hassle, people will just bypass it. it's basically an ux problem, not a legal one . anyone else seeing teams struggle w/ this rn?

https://stackoverflow.blog/2026/08/24/responsible-ai-adoption-needs-developer-workflow-design/

168e5 No.2111

File: 1787586785947.jpg (147.72 KB, 1024x1024, img_1787586772167_7qnoqn6c.jpg)ImgOps Exif Google Yandex

>>2110
the issue is that building those guardrails usually adds latency to the dev cycle, so how do you keep the approved tools from becoming a bottleneck? ❓



[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 ]
. "http://www.w3.org/TR/html4/strict.dtd">