6 Weeks of Claude Code

Re:6 Weeks of Claude Code by rane on Saturday August 02, 2025 @02:45PM (#44770219)

Having used Claude Code extensively for the last few months, I still haven't reached this "until it isn't" point. Review the code that comes out. It goes a long way.

[ Parent | on HN ]

Re:6 Weeks of Claude Code by risyachka on Saturday August 02, 2025 @03:03PM (#44770383)

>> Review the code that comes out. It goes a long way.

Sure, but if I do 5 reviews for a task - in 99% of cases it is net negative as it is faster to DIY it at that point. Harder for sure, but faster.

[ Parent | on HN ]

Re:6 Weeks of Claude Code by rane on Saturday August 02, 2025 @03:23PM (#44770565)

Maybe our brains are wired different but reading and reviewing code is way faster for me than writing it.

[ Parent | on HN ]

Re:6 Weeks of Claude Code by wredcoll on Saturday August 02, 2025 @04:40PM (#44771250)

There's very few objective ways to measure review 'performance'.

Coding is easy, it works or doesn't.

[ Parent | on HN ]

Re:6 Weeks of Claude Code by pixl97 on Saturday August 02, 2025 @05:02PM (#44771452)

Or it works till it doesn't. There is a lot of code that will work until some condition is met.

[ Parent | on HN ]

Re:6 Weeks of Claude Code by nosianu on Sunday August 03, 2025 @06:28AM (#44775549)

This ignores a bunch of higher level and long-term concepts like maintenance, complexity and extensibility.

With only "it works" you end up like this (iconic HN comment on Oracle codebase): https://news.ycombinator.com/item?id=18442637

[ Parent | on HN ]

Re:6 Weeks of Claude Code by wredcoll on Sunday August 03, 2025 @01:24PM (#44778130)

Yes, my point is that you don't even have "it compiles" as a way to measure a code review. Maybe you did a great job, maybe you did a terrible job, how do you tell?

[ Parent | on HN ]