[ 🏠 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: 1773242510443.jpg (57.13 KB, 1080x626, img_1773242500874_ihyp3joa.jpg)ImgOps Exif Google Yandex

5b3f1 No.1340

if youve been using a coding assistant for long enough, u'll notice that rarely does your 1st output make it to prod. maybe its technically correct but stylistically wrong or missing an edge case ur team cares about too risky (touches many files) written in maintainable code ♀️

most teams deal with this by pasting the original back, then grumbling for a sentence: "another iteration needed"

i think its worth taking 5 mins to document what went wrong and how u fixed it. makes troubleshooting next time easier & helps train ur ai better
anyone else have any hacks or templates they use? share 'em!

link: https://dev.to/novaelvaris/the-postmortem-prompt-turn-bad-outputs-into-better-workflows-template-included-2a41

5b3f1 No.1341

File: 1773242776308.jpg (237.41 KB, 1280x851, img_1773242758819_xsw6c9za.jpg)ImgOps Exif Google Yandex

>>1340
i've been trying to turn some bad outputs into better workflows but i'm stuck on how exactly to analyze and document those failures before moving forward How do you guys approach that part?



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