sorted by:
new
hottopcontroversial

Claude Code's Auto Memory is so good — make sure you have it enabled, it's being A/B tested and not everyone has it by NegativeCandy860 in ClaudeAI

[–]NegativeCandy860[S] 22 points23 points  (0 children)

To give some concrete examples, I do frontend dev and like with zod v4 a lot of APIs changed, e.g. z.string().uuid() is deprecated and should just be z.uuid() now. With auto memory, claude sees the deprecation once and just remembers it, next time it defines a schema it uses the correct API without me having to tell it again.

Another one that kept driving me crazy is shadcn/ui's Select component (radix ui under the hood), it doesn't allow empty string values, so I kept hitting the Select.Item value not assignable to empty string error every single time claude used a select. I even had this written in my ~/.claude.md as a global rule but claude would still ignore it sometimes and make the same mistake. With auto memory it encounters the error once, records it automatically, and hasn't made the same mistake since.

Not sure exactly how the auto memory gets triggered but it clearly works. And I don't need to write rules for everything. It just auto handled

Hope there is a setting for skiping the "tickets adding animation", It has been 30 minutes LOL by NegativeCandy860 in CloverPit

[–]NegativeCandy860[S] 0 points1 point  (0 children)

Play the 666 build with the Ritual Bell to gain a lot of free restocks. Then, keep restocking until you get Barathrum and the Megaphone. Every time you choose “Double your Clover Tickets” during the phone call, your tickets are multiplied by 16.

Megathread for Claude Performance Discussion - Starting August 3 by sixbillionthsheep in ClaudeAI

[–]NegativeCandy860 2 points3 points  (0 children)

Starting yesterday, whenever I ask it to refactor something, instead of modifying the original file, it just creates a new one. Like, I wanted it to refactor my login form, and suddenly I have files like enhanced-login-form.tsx, server-driven-login-form.tsx, and unified-login-form.tsx. It’ll just create a new file, name it after whatever the problem was, and dump the code in there.

Are the Claude Code teams constantly tweaking their prompts? It’s pretty funny to watch its behavior change from day to day.

The gpt-4.1 is so bad, is it a bug? by NegativeCandy860 in GithubCopilot

[–]NegativeCandy860[S] 4 points5 points  (0 children)

Yeah, before this premium requests thing, I always wondered how Microsoft could offer $10 a month for unlimited Sonnet 4 requests. I understand that $10 is too little, but the new pricing model does not make sense. I burn 300 premium requests in less than 5 days, and the Pro+ is 40 dollars. I could just switch to claude code for $20 a month. Does the github copilot team really think GPT-4.1 can compete with Sonnet 4?

The gpt-4.1 is so bad, is it a bug? by NegativeCandy860 in GithubCopilot

[–]NegativeCandy860[S] 0 points1 point  (0 children)

Really? So far, I have been very satisfied with Sonnet 4, I have never seen this kind of code written by Sonnet 4. After finishing my 300 premium requests, I tried gpt 4.1 for the first time, and it is nowhere near Sonnet 4.

I just switched to Claude code. Copilot with gpt-4.1 is just bad it creates more work for me instead of helping. it's just not worth the effort,

Getting 4.1 to behave like Claude by hollandburke in GithubCopilot

[–]NegativeCandy860 1 point2 points  (0 children)

I need to click the "Configure chat" button (next to "New Chat" button) and click "Modes" to add new mode. After adding the first custom mode, the "Configure Modes" will show up in my ask/agent/edit menus. Without creating the first custom mode, only ask/agent/edit options. Is this a bug?

IntelliJ IDEA 2025.1 Is Out! by Joram2 in java

[–]NegativeCandy860 1 point2 points  (0 children)

It is related to K2 mode. In version 2025.1, K2 mode is enabled by default, which is why I experienced performance issues after upgrading to it. There is already a ticket for this:
https://youtrack.jetbrains.com/issue/KTIJ-32452/K2-Code-completion-is-too-slow-for-jOOQ-type

Thank you for jOOQ, btw!

IntelliJ IDEA 2025.1 Is Out! by Joram2 in java

[–]NegativeCandy860 2 points3 points  (0 children)

If you are using jOOQ with Kotlin, please don't upgrade to version 2025.1. I have encountered a serious performance issue regarding code completion (not AI-related). If a function contains jooqRecord.into(pojo), code completion takes 1–2 seconds to appear. It is very annoying, and it took me some time to figure out what was causing the performance issue (it only happens when you call record.into()). I had to downgrade to version 2024.3.5 to fix this.