Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In my experience you can get around it by having a linter rule disallowing it and using a local claude file instructing it to fix the linting issues every time it does something.


You can equally get around a significant portion of the purported issues with dynamically typed languages by having Claude run tests, and try to run the actual code.

I have no problem believing they will handle some languages better than others, but I don't think we'll know whether typing makes a significant difference vs. other factors without actual tests.


I always instructions to have the LLM run `task build` before claiming a task is done.

Build runs linters and tests and actually builds the project, kinda-sorta confirming that nothing major broke.


it does not always work in my experience due to complex type definitions. Also extra tool calls and time are needed to fix linting.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: