ended up settling on the same pattern. /question enters a mini-plan mode of sorts. As LLMs got better at instruction following some of the hard modes seem redundant at this point

debugging a UI issue and, spoiler, it's useEffect. Everytime it's useEffect Claude is overly keen on writing that and I feel like the only thing that will deter it is a hard-error rule in biome

why is an idle @bunjavascript server consuming so much CPU? Latest version

how are y'all reviewing code (human or AI-generated), what is the best interface or interface patterns you have found that cracks the flow: 1. see diffs 2. explore code 3. add comments

hot version control take: a jj-native forge should dispose with the ‘jj push’ semantics - that’s a relic from git. Change ids are stable, unique and can be immediately synced across all connected hubs or clients

attempted to indoctrinate a few of my colleagues into the obviously better version control system before the Christmas side project season

still trying something like this out but i found jj (jujutsu) model for this particularly suitable. You can get Claude Code to pre-generate commits empty (jj new -m "<change_1>" && jj new -m "<change_2>") and then have it assign the actual code changes to those commits

probably no way for @atuinsh to track this but I wonder what the graph would look like if it tracked interactive shell use time (claude code would obviously top the charts)

it's atuin wrapped time! story of my 2025 shell is that I adopted jj halfway through the year (you can see lg - lazygit - decline) and mostly switched projects from pnpm (shorthand: pn) to bun

i remember my Clojure days fondly

this post was specifically prompted by the behavior were flags are ALWAYS before subcommands when the normal practice is to allow for interleaving

I've slowly been Effect-pilled over the last weeks but I think that effect/cli is overly-opinionated in not the right way

wild how far you can get with markdown files with front-matter, unix-y tools, and some scripts

when invoking a shell command claude code sets the following env vars: CLAUDECODE=1 GIT_EDITOR=true (to prevent interactive git editors) CLAUDE_CODE_ENTRYPOINT=cli would love if they passed in more metadata like the session id

claude code showing % of context used, and codex showing % of context left is pure context rot for my context-switching brain

@mixedbreadai

https://t.co/HP1MYSVyJl

reworked `ragrep` (fully local semantic search that you can use on Claude Code) over the weekend: it's more accurate (using a reranker) works faster if used in a server/client mode (loads the models only once) reindexes incrementally

i made a fully local version prototype of this a while back (using @mixedbreadai ‘s own oss models!) should probably dust it off and update with live indexing and better reranking..

First one was a blast! Demos included: 🧑🏼‍🎨AI building & testing @FlorisWeers 🌚Darker mode emails @MatteoGauthier_ 🔮Visualizing AI logic @CompuIves 🍬Icon studio @robertvklinken ⚙️MCP optimization w/ GEPA @_laurynas 👥AI collab iOS apps @sirian_m 🥽VR + Rust scripting @rikarends