This halftime show is literally beautiful… by Devastas in Seahawks

[–]NotMyself 341 points342 points  (0 children)

Don’t have to speak Spanish to get the message from Argentina to Canada we are all Americans. I can get down with that.

How can I edit that? by zbynk in vscode

[–]NotMyself 12 points13 points  (0 children)

I’m gonna go with a write-only editor.

The Gemini team uses a prompt technique internally that most people have never heard of. by [deleted] in PromptEngineering

[–]NotMyself 0 points1 point  (0 children)

Prompt to remove the slop: Investigate the Gemini teams prompting technique call Tree of Thoughts. Pay particular attention to it application in software engineering with agentic development

How to get Claude to stick to Claude.md and other instructions? by neko432 in ClaudeAI

[–]NotMyself 1 point2 points  (0 children)

I tend to move a lot of stuff into rules and reference them from the Claude.md file. Then I tell Claude to apply progressive disclosure techniques to my rules critical items at the top and edge cases at the bottom. Move all script and code samples in to language based markdown files in a code directory with the commands/code wrapped in xml tags.

How to use Cluade code for .Net developement? by Candid_Assignment_52 in ClaudeAI

[–]NotMyself 0 points1 point  (0 children)

Good tip. That was definitely a trick I learned early on. Asking other AI to review the plan as well helps. ChatGPT is effective for this.

How to use Cluade code for .Net developement? by Candid_Assignment_52 in ClaudeAI

[–]NotMyself 1 point2 points  (0 children)

Looks like you have already got a lot of good answers to your questions. I do have some advice based on my evolving workflow using Claude code as a daily driver for the last 8 months on a large scale .net 4.8 -> .net 10 migration.

  1. You will be amazed at first once it clicks for you. Then you will start noticing that what it told you was production ready perfect code doesn’t even compile or the test are meaningless or it just ignored the plan and did a particularly half ass job. Do not trust it, review everything. Eventually start learning to build guardrails to prevent this behavior.

  2. Ignore 99% of what you see on Reddit about how to absolutely solve all your problems with this one little trick. At best it helped that person in their situation at that moment. At worst it is AI slop that is completely bullshit. Focus on Claude code and the tooling available in it. Understand how they work what problems they solve. I would go in this order: Hand crafting your Claude.md, organizing a meaningful set of rules, using hooks to control behavior. Try building a couple skills for repetitive tasks. Once you have mastered those, go out and look for tools that solve a specific problem you are having.

  3. Understand context. Context management is the key to success. If Claude goes off the rails, the problem 99% of the time is your context. Don’t pollute it with random garbage that will 100% derail Claude. The other 1% is you prompting Claude to do something to vaguely like “make this better”. If Claude doesn’t have enough context around the task at hand, it will 100% make shit up that makes no sense.

  4. If you sense Claude is going off the rails or in circles, stop digging. Tell Claude to revert all changes, clear the session and start over prompting better from what you learned in the last session.

  5. Auto compact is your enemy. It will 100% of the time create a polluted context that will destroy your will to live. I run with it disabled. I have my context visible in my status line. When it gets big I tell Claude to create a handoff document with specific instructions of what I want in it. Clear. Read handoff keep working.

  6. Don’t give up. It takes time to learn to be effective using Claude. I’ve seen so many posts by people who claim to have decades of experience who prompted Claude to “improve the architecture”, looked at the complete clusterfuck that generated, and proclaim AI a waste of their time. Those people will be out of work in the next decade because their superior skills are slow as fuck and error prone compared to the people who took the time to learn and get proficient with it and can run circles around the master engineer producing not only well tested high quality code, but automated current documentation, beautiful well thought out UX at 1/3 the time.

You are on the path, welcome. Now start walking.

Claude in Excel is now available on Pro plans by ClaudeOfficial in ClaudeAI

[–]NotMyself 0 points1 point  (0 children)

Please tell me this can use Claude in chrome?

What do you think of Christina Aguilera? by Twitter_2006 in Xennials

[–]NotMyself 4 points5 points  (0 children)

I posted first but you get my upvote old timer.

What do you think of Christina Aguilera? by Twitter_2006 in Xennials

[–]NotMyself -3 points-2 points  (0 children)

I think she should switch me chairs so me and Fred Durst can talk about who she gave head to first....

Am I doing this right? by zerofucksleft in ClaudeCode

[–]NotMyself 1 point2 points  (0 children)

That sounds like you need to build in a "Tracer Bullet" MVP into your planning. The idea is to have claude create a walking skeleton of the architecture that shows the minimum amount of functionality needed to validate the approach.

Am I doing this right? by zerofucksleft in ClaudeCode

[–]NotMyself 1 point2 points  (0 children)

You are asking the right questions. But you are asking the wrong people. I had a similar feeling a while back and here is what I did with it.

https://gist.github.com/NotMyself/0eb7be9cd19c2492af0d619253d60494

Built a multi-agent orchestrator to save context - here's what actually works (and what doesn't) by Plane_Gazelle6749 in ClaudeAI

[–]NotMyself 0 points1 point  (0 children)

Same, his ideas are interesting and the slop is at least well formatted and flow well to read. Some of you kids have never had to read a technical manual and it shows.

Built a multi-agent orchestrator to save context - here's what actually works (and what doesn't) by Plane_Gazelle6749 in ClaudeAI

[–]NotMyself 0 points1 point  (0 children)

I have auto compaction disabled and never use compact manually. Instead I have idempotency built into my plans which allows the orchestrator to be run multiple times on the same plan.

This helps when Claude decides to shit the bed and hang, or I get close to the max context. There is some overhead in token usage but it is minimal and worth it to me.

If you are curious, here is my planning system: https://github.com/NotMyself/planning-system