Login

u/c1rno123

r/docker r/SpecDrivenDevelopment r/ExperiencedDevs r/PiCodingAgent r/devops r/programming r/cybersecurity r/AI_Agents
▲ 5 r/ExperiencedDevs

If service reliability conflicts with cost, what’s your strategy?

Before containers and Kubernetes, I deployed services onto virtual machines. We had a fixed number. When the peak arrived at night, whoever was on call tried to spread the load by hand. Buying more hardware took time, and some unreliability was acceptable.

Then AWS and Cloudflare made it easier to throw money at capacity and let some infrastructure scale. You have to design the system with scaling in mind. And a bill.

Now tokens add cost.

If you own both the service and the bill, what’s your strategy? How do you cap, what cap acceptable? How to gracefully degrade? And how rules applies across the organization?

reddit.com
u/c1rno123 — 11 days ago
▲ 6 r/SpecDrivenDevelopment+1 crossposts

Why does everyone keep the specs? Mine dies in $TMPDIR

Every SDD framework gets the same complaint: spec rot.

Mine: research reads only, one handoff gets written to $TMPDIR, then a build step checks that handoff against the repo and runs the tests. Durable guidance lives in AGENTS.md. The spec dies with the temp file.

So why do the main tools still ship the part that rots? Harness memory, SDD frameworks, tracker docs, all of them persist by default. What am I missing that makes persistence worth the rot?

Full writeup https://bogomolov.work/blog/posts/rotten-specs/

u/c1rno123 — 3 months ago
▲ 1 r/AI_Agents

Sharing some thoughts on AI agents. Right now, one axis differentiates them:

  • are you inside the agentic loop
  • or outside it

Inside works. See Claude Code, OpenCode — you see the plan, approve steps, stay in the loop. Ships real work.

Outside — only narrow tasks. And it still can't tell you "no." It'll happily attempt anything, fail silently, and hand you back something.

Any options I've missed?

reddit.com
u/c1rno123 — 6 months ago