3 ms·
Bruh. It's getting hard to track down all these MAKE_IT_ACTUALLY_WORK settings that default to off for no reason.
by andersa 6mo ago
Bruh. It's getting hard to track down all these MAKE_IT_ACTUALLY_WORK settings that default to off for no reason.
- deleted 6mo ago[deleted]
- ethbr1 6mo agoThat's the beginning of Googlification of feature evolution, via population statistics rather than quality. If it increases a KPI by 5% for 95% of users but torpedos the experience for 5%? Ship it.
- hnben 5mo agothat sounds like a win-win to me. on one hand 95% of users get an improved experience. While a competitor gets the chance to build a business for the remaining 5%.
- matheusmoreira 6mo agoFor me it's gotten to the point where I have a wrapper script that applies like 5 environment variables and even patches the system prompt strings prior to every Claude Code invocation. After the Claude Code source code leak someone discovered that some variables are read directly from the process environment. Can't even trust that setting them in ~/.claude/settings.json will work! I've actually started asking Claude itself to dissect every Claude Code update in order figure out if it broke some part of the Rube Goldberg machine I was forced to set up.