@sairahul1 Copy-Paste prompting is not the way. Governance is the way. Steal my stack model at https://t.co/h4cjtD8wwH
You don’t even need to read it, point your preferred coding agent at it and let it rip.
Salty’s hosting Wishlist Wednesday with a pick for gift cards to tackle unexpected barn needs. Check out the Big Blue Vase plan and help out! https://t.co/K2HonbFWmN 🐐💳
I can see that. I glossed over your reference to 4.7
In that case, a session running without an efficient file handling protocol can, and in my early use, certainly did spin up the costs. If you’re interested, when I finish the ambiguous version of my efficient file handling protocol that uses my file system as long term memory and checkpointing system, I’d appreciate your review.
I’m not sure about those $ amounts; I’m not seeing anywhere near that level of inefficiency. This is my foundational stack, ambiguated for universal application. I’m working on putting up my automated backend agents, so more to come, but this was a hard-won stack that has 100% eliminated hallucination, ensures we never push unmapped code, and has resulted in nearly zero bugs. I accept it isn’t for everyone, but for a Lone Ranger running over 20 repos for private clients, with a single Sr Eng advisor, we are nearing $10k MRR … having started at $2k MRR in Feb 2026.
https://t.co/krLHDZU3mw
Part of your answer is here:
Accusing polished writing of ‘AI slop’ just because of em dashes or rhythm? That’s not discernment—it’s lazy pattern-matching dressed up as wisdom.
This biting essay nails the pedant’s tell and flips the script … the real question has never been ‘did a tool touch this.’ It’s always been ‘did a mind shape this?’
Essential reading for anyone tired of superficial takes:
https://t.co/Jp2iqMylAj
@kritikakodes There is a market for someone to either garner a following that pays on view time or sells preconfigured governance stacks for vibe coders.
@1ssve When using Grok (Strategist) and Claude Code (Executor) in a two-actor model, the Claude app started referring to Grok in a contemptuous manner…
I went to bed.
@BenjaminPDixon Between the bots and the paid influencers, you have about a 30% chance that you’ll see authentic comments on anything.
But yeah, lots of “vibing” out there from the “didn’t do my homework” crowd.
@Umesh__digital Move the file to the Postgres server.
Validate for malformed.
Prep db for bulk.
Python in 10m chunks.
Don’t die params.
Done in 2 hrs.
Renable db.
It really depends on your use-case. What are you hoping to get from it?
If you just want better answers than Google can provide, your X account gives you plenty of access to Grok…$40/mo gives you whatever level you’re paying for to get that blue checkmark, plus access to Grok.
Perplexity w/out Computer gives same but it decides which make&model serves your query.
For coding, you’ll need more than one and spend well over $20/mo.
PPLX is $200/mo for Computer and it can write directly to your GitHub repo.
Claude Max is $100 to $200 /mo and you can run it in two lanes: run Claude Code in Terminal or an IDE to direct write your codebase; run the latest model in the app or your architect and strategy work, then have Claude Code write the plans to your codebase.
Codex has improved, but I abandoned it at 5.3
Grok Build is $300 /mo and will run in your Terminal or IDE and is awesome.
@pmarca It appears that Ai-assisted authorship would have utility after-all. I suspect that @claudeai or @grok would have found this “unit” error in short order.
I run a coherent multi-project enterprise across three families of sites + shared infrastructure, ~18 repositories, and two specialized AI actors … with almost zero human oversight post-spec.
It’s not a single tool. It’s a lightweight governance OS built on four interlocking systems:
1. Enterprise Schema
Instantly answers: “Which project family does this belong to? Which rules apply?” Everything lives under a clean /Projects/ structure with shared orchestrator + architecture registry.
2. CLAUDE.md Cascade
Global → Shared Resource → Family → Project rules. Precedence is explicit and conflict-proof. The most specific file wins, but higher levels always govern routing and cross-family behavior.
3. Two-Actor Framework
• Strategist (https://t.co/8rZo3iAbaf): researches, architected designs, writes detailed handoff specs. Never touches code, env files, DBs, or git.
• Executor (Claude Code in Terminal): reads production state, runs sanity checks, writes/tests/commits/deploys. Only actor allowed to change the filesystem.
4. Efficient File Handling
Checkpoints in every repo (docs/checkpoints/) + handoff documents + persistent filesystem writes + session-start resume protocol. Sessions time out? Nothing is lost. Work flows asynchronously between actors and across days.
Supporting protocols that make it actually work at scale:
• Pre-edit Sanity Check (queries live data before any change)
• Post-execution QA gate (type safety, diff audit, security scan, clean commit)
• Governance Sync between strategist and executor
• Dual Roadmap System (product strategy vs. execution ledger) + complementary registries
Result: three distinct project families stay aligned, shared infra stays healthy, AI handoffs survive context resets, and the entire surface evolves without anyone holding the full graph in their head.
@nattyshaps@0xDesigner Agreed. They are likely lacking in a curated Claude.md, have no governance protocols, and are running in the desktop app. They just need to use terminal mode or even an IDE, setup sanity checks with bounded deviance deltas, and turn perceived-failures into protocol improvement.
@bettersafetynet Yup. No disagreement here. Assuming they went retaining dopes, they have a captive crew they upskill and ontool for near immediate forceX.