developer tooling

Om Patel @om_patel5 · 10h claude code has a hidden setting that makes it 600x faster and almost nobody knows about it by default it uses text grep to find functions. it doesn't understand your code at all. that's why it takes 30-60 seconds and sometimes returns the wrong file there's a flag called ENABLE_LSP_TOOL that connects it to language servers. same tech that powers vscode's ctrl+click to jump straight to the definition after enabling it: > "add a stripe webhook to my payments page" - claude finds your existing payment logic in 50ms instead of grepping through hundreds of files > "fix the auth bug on my dashboard" - traces the actual call hierarchy instead of guessing which file handles auth > after every edit it auto-catches type errors immediately instead of you finding them 10 prompts later also saves tokens because claude stops was[ting] context searching for the wrong files [text cut off at bottom of screenshot]

[Above, cut off: video thumbnail from a parent tweet, "Next: Create string-utils.ts with slugify, truncate, capitalize", a terminal/coding session with a "Run Prompt" timestamp overlay "21:11 02-Jan-26", 0:20 length. Engagement: 69 replies, 38 reposts, 726 likes, 35K views] ian @ianpatrickhines i've been running a similar idea in the statusline using ccusage. super helpful. [Embedded image: a statusline widget showing "$18.23 day, $717.54 month, 718% plan | 🔥 $5.55/hr | 🧠 69.3 ktok ...und tasks"] 5:47 AM · Jan 2, 2026 · 329 Views