With anything above a toy project, you need to be really good with context window management. Usually this means using subagents and scoping prompts correctly by placing the CLAUDE.md files next to the relevant code. Your main conversation's context window usage should pretty much never be above 50%. Use the /clear command between unrelated tasks. Consider if recurring sequences of tool calls could be unified into a single skill.

Instead of sending instructions to the agent straight away, try planning with it and prompting it to ask your questions about your plan. The planning phase is a good place to give Claude more space to think with "think > think hard > ultrathink". If you are still struggling with the agent not complying, try adding emplasis with "YOU MUST" or "IMPORTANT".

The failure case I see most often is when this thinking is applied to some kind of a wicked problem.

1. The problem is not understood until after the formulation of a solution.

2.Wicked problems have no stopping rule.

3. Solutions to wicked problems are not right or wrong.

4. Every wicked problem is essentially novel and unique.

5. Every solution to a wicked problem is a "one shot operation".

6. Wicked problems have no given alternative solutions.

Source: Dialogue Mapping: Building Shared Understanding of Wicked Problems 2006 Jeffrey Conklin ISBN: 978-0-470-01768-5

When it gets cold, the homeless congregate in the warm interiors of malls. The guards on duty won’t let them sleep there, but they prefer it over being out in the cold.

When you fail, it can be due to many things. Not everything in the world is controllable. This is one of the reasons why expecting zero ”What ifs” at the end of your post-mortem is unreasonable.

If you really want to use MacOS's smooth scrolling, use MOS (https://mos.caldis.me) and get a beefy Mac because the base models will stutter like I mentioned.

The rest of my life also revolved around recovery and nutrition because very quickly I realized that I needed to make extraordinary efforts to allow my body to recover from the regimen. I slept 10+ hours and ate around 3300 cals daily (TDEE was massive).

Being on antidepressants at the time made eating these amounts much easier, as it seemed to turn off something in my brain responsible for me feeling satiated.

I started gym after being diagnosed with the psych issues. I really put 110% effort into it and got… big stretch marks because my muscles grew so fast. I don’t think what I was doing was ”healthy” as much as it was ”I am super depressed and heavy barbell squats is my coping mechanism”.

I just wanted to say, you don’t need PEDs to get ”scary” jacked. But you probably need to be crazy like me.

Comments URL: https://news.ycombinator.com/item?id=42145582

Points: 20

# Comments: 9

From vscodium.com:

Microsoft’s vscode source code is open source (MIT-licensed), but the product available for download (Visual Studio Code) is licensed under this not-FLOSS license and contains telemetry/tracking. According to this comment from a Visual Studio Code maintainer:

When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license.

When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. Therefore, you generate a “clean” build, without the Microsoft customizations, which is by default licensed under the MIT license

The VSCodium project exists so that you don’t have to download+build from source. [VSCodium] includes special build scripts that clone Microsoft’s vscode repo, run the build commands, and upload the resulting binaries for you to GitHub releases. These binaries are licensed under the MIT license. Telemetry is disabled.

Really, you have a ”one-system” where you can see _ALL_ the logs? I don’t believe that. This whole software thing is abstractions everywhere, and we are probably using some abstraction somewhere that isn’t compatible with this fabled ”one-system”.

Often the most debugging takes place on the least observable systems.