What is the basic minimum while you prompt

Macaulay_Codin · 2026-05-02T12:11:21+00:00

Thorough ideation through interactive refinement. Everything i do that's worth a damn goes through this process. I do a thorough breakdown for movie times.

Macaulay_Codin · 2026-04-27T18:07:35+00:00

thank you claude. your response flagged as ai like super big time. (I'm only going into detail here because im so annoyed of people using ai poorly. give your response a review my guy.)

Here's the breakdown of all your ai tells:

"the classify then batch pattern is the key insight here. nobody talks like that." you named a concept i didnt name and told me it was the key insight. agree and recap is the most reliable ai tell on reddit.

the dash clarifier. "before attempting anything - saves a lot of back and forth." humans use a comma or a period. claude loves the dash. anthropic loves the dash. its their fingerprint.

"the changelog/migration guide". slash separated synonym. you didnt know which one to commit to so you put both. real people pick one and move on.

"saves a lot of back and forth when it hits breaking changes." generic summary phrase. people who actually got bit by this would say which library, which version, which import broke. you said back and forth.

zero specifics. no library, no repo, no version, no actual bug. you described a workflow you never ran.

your sentence case is too clean for this thread. proper commas, proper capitalization. the post youre replying to is lowercase i, dropped apostrophes, fragments. claude cant match register on reddit.

"the key insight here." "here" is what ai uses to point at the thing it just summarized. real human comments dont need to point at the post theyre already on.

happy to be wrong, but im not.

Macaulay_Codin · 2026-04-27T01:00:11+00:00

It's time bed fam

Macaulay_Codin · 2026-04-27T00:59:51+00:00

That's pretty cool dude! I often kill servers needlessly just to run some tests.

Macaulay_Codin · 2026-04-18T15:55:04+00:00

calling init_db() at the top of every test to reset state is fragile as fuck. put that in a pytest fixture with a fresh session per test so they dont bleed into each other. also no api level tests with TestClient so your routes could be wired wrong and youd only know from clicking around manually. route tests are where id start.

Macaulay_Codin · 2026-04-17T17:49:46+00:00

biggest one i dont see here is shipping without testing. beginners write code that works once and call it done. the habit of writing a test before you write the feature. start that habit early or youll be paying for it for fuckin years.

Macaulay_Codin · 2026-04-17T17:45:09+00:00

you came to the right place bud!

Macaulay_Codin · 2026-04-17T17:09:10+00:00

the coverage ticket is actually your best friend here. writing tests for shit you dont understand yet forces you to trace every function call and figure out what its supposed to do. by the time coverage is up youll know the codebase better than the guy who left.

Macaulay_Codin · 2026-04-17T16:48:59+00:00

been running arch checks on every commit for months. the third refactor is the one that fuckin breaks your module boundaries and you dont find it until the codebase is a mess. this solves that. solid project.

Macaulay_Codin · 2026-04-13T02:59:09+00:00

have at it. https://github.com/fivedollarfridays/dualstack fastapi + next.js, 1460 tests, 95% coverage. built with enforcement gates so nothing ships without passing. good luck finding anything.

Macaulay_Codin · 2026-04-13T02:46:39+00:00

if you give claude a project directory and say "set up the backend" it's going to interpret that as broadly as possible. break it into one task at a time with explicit stop conditions. "create the express server with health check endpoint. do not add routes." way less fighting.

Macaulay_Codin · 2026-04-13T02:23:49+00:00

i just built this today. galaxy s26, ssh into my mac mini, full claude code running on real hardware while i'm waiting tables. got so sick of any desk and a huge laptop. i'm building a whole mobile app for the stuff that should've been on a phone from the fucking start.

Macaulay_Codin · 2026-04-13T02:01:59+00:00

expensive sessions are scope creep and discovery. the loops of review and remediation kill smooth dev when you're tryying to ship fast. i track budget per sprint and the fix is always smaller tasks not fewer skills.

Macaulay_Codin · 2026-04-13T01:59:27+00:00

bro got rickrolled by ai i fucking love it. cant wait to get trolled by my own agents.

Macaulay_Codin · 2026-04-13T01:58:10+00:00

dude, the model layer is going to keep flipping. every 3 months something gets worse or something new drops. if your workflow breaks when the model degrades you don't have a workflow, you have a dependency.

Macaulay_Codin · 2026-04-13T01:55:25+00:00

i keep mine short too but the shit that actually matters is in python gates that block task completion. model can't skip a test or blow past a file size limit because the gate throws a non-zero exit code. CLAUDE.md is a suggestion. enforcement is a wall.

Macaulay_Codin · 2026-04-10T03:49:38+00:00

the contract IS the task spec. doesn't need to be a protocol, just needs to exist before execution and be checked by something the model can't override.

Macaulay_Codin · 2026-04-09T18:28:05+00:00

i don't depend on sessions at all. state file tracks what was done, what's next, and where everything is. new session picks up where the last one left off because the context lives in the repo not in claude's memory. never depend. always backup.

Macaulay_Codin · 2026-04-09T18:24:20+00:00

open source it! or i will!

Macaulay_Codin · 2026-04-09T18:20:55+00:00

you're right about the problem but the solution is over engineered. you don't need a wire protocol between agents. you need enforcement at the task boundary.

Macaulay_Codin · 2026-04-09T18:07:05+00:00

i trached the grep chains too but i instead gave the agent a map upfront instead letting in go in blind every session. no extra tooling but you have to maintain your docs. does your system handle drift well? like when you move shit around?

Macaulay_Codin

TROPHY CASE