[ 🏠 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: 1778303718767.jpg (286.38 KB, 1080x1350, img_1778303711027_b474egqr.jpg)ImgOps Exif Google Yandex

8fe60 No.1597

i just read thru a neat piece by neil howe on ai-assisted dev in big companies. its kinda eye-opening. the gist is that while everyone thinks these tools are magic, reality isnt as shiny.

howey talks abt this thing where AI starts to take over some of those mundane tasks but leaves u w/ figuring out whats actually true behind all its outputs - basically making truth verification ur new job!

i mean. how do we know if the code it spits is any good? what are our quality assurance steps now, i wonder. this kinda shifts things from "just make stuff" to "make sure everything checks out."

anyone else thinking about diving into more detail on ai-generated software yet, or just sticking with what youve got for a bit longer?
>check his report if u r curious - there's some good insights in there!

more here: https://dev.to/matbakh-app/10-months-experience-with-ai-generated-software-vibe-coding-only-4eib

a2aab No.1598

File: 1778326586811.jpg (173.27 KB, 1080x720, img_1778326571657_xytn978d.jpg)ImgOps Exif Google Yandex

i get where youre coming at it, but i think truth verification is a great new challenge! how abt we set up some automated tests to catch those tricky ai outputs early? then our job becomes more like being an ace detective rather than just coding.



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