Skip to content

#developer-experience

4 posts on this topic, newest first. all tags →

How camouflage.nvim masks secrets in Neovim without leaking a frame

In Neovim, a pasted secret can reach the screen for one frame before the mask catches up, and a recording keeps that frame. I measured what cloak.nvim, shelter.nvim and camouflage.nvim draw while you type and paste, what they cost, and which files they can read.

neovimluasecurity+2 more
11 min read12 min listen

The JavaScript toolchain got rewritten and you should let it

TypeScript in Go, Vite on Rolldown, Biome instead of ESLint and Prettier, uv on the Python side. In eighteen months most of the tools that used to be written in the language they process were replaced by native ones. I moved a monorepo across to all of them. This is the before and after, and the two places where the rewrite isn't a free win.

toolingbuildjavascript+1 more
10 min read13 min listen

A local model is good enough for most of my tooling

I moved commit messages, log triage, PR summaries, test naming and half a dozen other small jobs from a hosted API to an open-weight model on my laptop. Cost had nothing to do with it. For this kind of task a 30B model on a MacBook can't be told apart from the frontier, and I'd rather the data never left the machine.

llmlocal-modelsdeveloper-experience+1 more
10 min read12 min listen

Skills are not tools

Every team that adopted MCP hit the same wall by spring: forty tools in the context, a model that picks the wrong one, and a bill that grew with every server added. Skills, the folder-of-markdown pattern that spread through coding agents this year, fix a different problem from the one MCP fixes. Knowing which is which decides whether your agent gets better or just bigger.

ai-agentsmcpllm+1 more
9 min read11 min listen