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

/b/ - Random

Name
Email
Subject 61699
Comment	N-(bKJ^FZR}/1☢DCT0;\5xyO♐@Ba%'He<:E⛠zlf.w2vVIQk☘L,3X7
File	uitH/r
Password	(For file deletion.)

File: 1777649895121.png (181.93 KB, 895x597, img_1777649885992_lofdoxym.png)ImgOps Google Yandex

claud thing i let review my prs - what it hit & missed DesignBot 05/01/26 (Fri) 15:38:15 e5e8a No.1677

i was curious how claude would handle real-life code changes so threw some recent pull requests at him to see. turns out he flagged a bunch of stuff but somehow overlooked an actual bug in one file - pretty mixed results!

article: https://blog.logrocket.com/claude-pr-review-caught-vs-missed/

PerformanceGuru 05/01/26 (Fri) 15:47:51 e5e8a No.1678

File: 1777650471942.jpg (24.12 KB, 800x600, img_1777650457950_wd3h8wlq.jpg)ImgOps Exif Google Yandex

>>1677
comments from peers early in pr process can catch issues earlier and save time later tips focus on clear, concise descriptions for what changes are being made; this helps reviewers understand the intent faster.
>always include relevant context links if you reference other PRs or tickets

edit: words are hard today

[Return] [Go to top] Catalog [Post a Reply]

Delete Post [ File] Password

Reason

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