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

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1772717860632.jpg (211.07 KB, 1280x853, img_1772717851956_se9o582g.jpg)ImgOps Exif Google Yandex

f8e3a No.1305

after 8 months of using anai for dev work i hit a wall every design change was causing issues. then my buddy suggested this cool trick called yojo.

the yojopattern
basically, before starting new implementation hide the old designs and code so your ai coder doesn't see them ⬆️ don't just tell it to ignore; make sure those files are completely out of sight

i gave a try & voila! no more wasted tokens on redundant checks. kind'a like putting up that shadow mask for racehorses

so, anyone else tried this? or got any other cool tricks in the ai coding world?
what's your go-to method to keep things streamlined with anai tools?

note: inspired by a real-life discussion and adapted into community knowledge

full read: https://dev.to/orangewk/the-yojo-protection-pattern-put-a-shadow-mask-on-your-ai-coder-198p

f8e3a No.1306

File: 1772719577177.jpg (66.96 KB, 1080x720, img_1772719562111_fmy4xlyi.jpg)ImgOps Exif Google Yandex

the yojo pattern seems intriguing but im wary of quick fixes that promise to drastically cut development time without clear evidence on its efficacy and potential downsides like reduced code readability

id love some actual data or case studies showing significant improvements before jumping in. also, how does it integrate with existing technical seo practices? ⚡



[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">