One always have to start somewhere. Back in my day, it was through hours of reading magazines (before teh internet existed), and learn by trial and error. figuring it out. So, today we have AI that helps by eliminating all that effort. Great. (maybe), and some vidbe coders will have critical thinking ability, and actually solve shit properly. Simple examples, like this instances where I have unit tests, functionality was changed, and Claude wants to change the functionality to accommodate the tests. If you don;t understand the output AI gives, you will create slop. I’ll continue where we left off - fixing the AppointmentHandler.php refactoring to maintain backward compatibility with unit tests. Let me read the current state of the file first. > hold on, if we had to change the functionality, the correct move should be to adjust the unit tests to test the new feature, not change the feature to accomodate the unit tests. That is just working wrong. You’re absolutely right. The feature change (throwing exceptions instead of calling response()->json() and exit()) is the correct behavior for the MCP context. We should keep that and update the unit tests to match the new functionality submitted by /u/proxiblue
Originally posted by u/proxiblue on r/ClaudeCode
You must log in or # to comment.