Sign in

nark3d

@nark3d.bsky.social
34 followers 41 following 174 posts

Product Engineer/Architect

PostsRepliesMedia
nark3d @nark3d.bsky.social · 29/09/2026
Simplicity gets agreed and then broken by a flag added for one caller. Hard caps beat intentions, because the linter doesn't get tired at 5pm. Tenets don't stop the deadline, but a cap the build enforces does. prickles.org/tenet/simpli...
prickles.org
F4 Simplicity · Prickles
F4 Simplicity: No line of code is cheaper than the one you didn't write. Reasoning, evidence, the counter-argument and the reply, on Prickles.
011
nark3d @nark3d.bsky.social · 22/09/2026
Every fact one home, but merge on meaning, not on shape. Two identical lines in different bounded contexts are two facts that happen to look alike, and fusing them makes one change touch two products. The word in the original is knowledge. prickles.org/tenet/dont-r...
prickles.org
F3 Don't Repeat Yourself · Prickles
F3 Don't Repeat Yourself — Every fact has one home. The second copy is the bug. Reasoning, evidence, the counter-argument and the reply, on Prickles.
000
nark3d @nark3d.bsky.social · 19/09/2026
Put the brief in the repo as CLAUDE.md, not in the chat. Paste it fresh each session and by the tenth everyone has a slightly different version. Under 200 lines, because past that the model skims. prickles.org/tenet/persis...
claude.md
Overview - Claude Code Docs
Claude Code is an agentic coding tool that reads your codebase, edits files, runs commands, and integrates with your development tools. Available in your terminal, IDE, desktop app, and browser.
000
nark3d @nark3d.bsky.social · 18/09/2026
Five positional arguments and you're counting commas to find the timeout. Naming the clump fixes it, and max-params: 3 in eslint means the third caller has to. prickles.org/tenet/parame...
prickles.org
S3 Parameter Object · Prickles
S3 Parameter Object — Three parameters, then a struct. Reasoning, evidence, the counter-argument and the reply, on Prickles.
000
nark3d @nark3d.bsky.social · 02/09/2026
Everyone agrees naming matters and almost nobody spends time on it. My review check is to say what a function does from its name and parameters alone. If I can't, the name's bad or it's doing two jobs, and it's usually the second. Best names are the product owner's. prickles.org/tenet/intent...
prickles.org
F2 Intention-Revealing Names · Prickles
F2 Intention-Revealing Names — The signature is the spec. Reasoning, evidence, the counter-argument and the reply, on Prickles.
010
nark3d @nark3d.bsky.social · 01/08/2026
Nobody argues with SRP in principle. The argument is about whether a given function is one thing or six. The name usually gives it away, if you need an "and" to describe it it's two jobs, and past that I ask who pays when it changes. prickles.org/tenet/single...
prickles.org
F1 Single Responsibility Principle · Prickles
F1 Single Responsibility Principle — Every thing should do one thing and one thing only. Reasoning, evidence, the counter-argument and the reply, on Prickles.
000
nark3d @nark3d.bsky.social · 07/06/2026
New post. Most things that get called a spec fall apart the moment a coding agent touches them. What's worked is writing the acceptance criteria as runnable checks, not paragraphs the agent has to interpret. prickles.hashnode.dev/a-spec-the-a...
prickles.hashnode.dev
Verifiable Specifications
Spec-Driven Development. A spec the agent can grade itself against is a contract. A spec the agent has to interpret is a wish.
110
nark3d @nark3d.bsky.social · 25/05/2026
Built a thing: Prickles. 50 software-craft tenets, each one argued and sourced - book, page, the strongest counter-argument I could find against it. The principles don't change; the pair programmer does. Half of mine is an agent now. prickles.org
010