>>105467329
>Is deepseek good for finding out why my code doesnt work like its supposed to?
if you feed them enough context, it'll find the problem. I usually uses Roo Code in VSCode for this kind of workflow. basically,
- open roo code in your project folder
- switch to Orchestrator mode and tell everything you need step-by-step, for example:
1. your task is to troubleshoot FunctionName()
2. this function is placed in some/folder/file.name
3. this function is called in where/was/called.name
4. expected behavior is "something" but currently it return "something else" instead
- press enter, wait and see roo code will switch from orchestrator to code mode automatically, reading all of your mentioned file. sometime it will switch to architect mode when creating a plan how to troubleshoot your function, then it'll switch to debug mode to actually test / trying to execute your code. once enough data is gathered, roo code will switch to Code mode automatically offering you a patch & it'll continue debugging once you accept it.
>Does this work on AMD GPUs? I never got AI to properly work when it came out.
AMD is not worth it to run something as big as non-distill deepseek. rocm/vulcan on amd are toy tier at performance level. it's generally just pain in the ass.
>>105467337
plenty but not enough, you have to read their privacy policy and see if it fits your use case
>>105467349
hardly surprising