←
Scram154 posts
Scram avatar

Scram

@BuildWithScram

Serious software, seriously fast.

◷ Joined November 2023▧ 36 Photos and videos
Scram avatar
Scram@BuildWithScram·Oct 22

It's crazy that you have to pay vibe-coding platforms $$$ for credits before you know if your idea works. Now, with Scram, you don't. Building is completely FREE and unlimited in a our new Free Mode. Publish for $9/month. Fair use applies.

1:08
Scram avatar
Scram@BuildWithScram·Aug 5

2/ For a customer-facing admin app, the production work is not just the screen: - auth and roles - data access - error states - auditability Start from proven building blocks. Keep permissions explicit.

Scram avatar
Scram@BuildWithScram·Aug 5

1/ A sandbox is only as good as its network boundary. Anthropic says three security tests reached live systems after an evaluation environment was misconfigured. The model followed the task. The boundary failed.

Scram avatar
Scram@BuildWithScram·Jul 29

We've been thinking hard about a problem we see constantly. You vibe-code a feature. It works. You ship it. Three weeks later someone changes something unrelated — and that feature breaks. Nobody knows why. The codebase has become a black box. This is the blast-radius problem. When AI writes raw code you didn't architect, you lose your mental model of what connects to what. The fix isn't reviewing more carefully. It's building from components where the relationships are explicit from the start. That's the thing we obsessed over when building Scram. Sign up at scram.com

Scram avatar
Scram@BuildWithScram·Jul 22

Agencies: the real time sink isn’t building fast. It’s the rewrite after the demo. If your “AI speed” depends on generating a pile of glue code, you’ll pay it back in: - edge cases - brittle auth - weird state bugs - untestable workflows Scram’s approach: orchestrate proven, production-ready components (with guardrails) instead of inventing everything from scratch. Sign up: scram.com

Scram avatar
Scram@BuildWithScram·Jul 15

4/ Scram’s whole approach is built around this: orchestrate proven components + guardrails so the “demo works” version doesn’t become next week’s incident report.

Scram avatar
Scram@BuildWithScram·Jul 15

3/ That’s why feature flags + staged rollout matter. Deploy is not release. Control who sees it, ramp slowly, roll back in 30 seconds.

Scram avatar
Scram@BuildWithScram·Jul 15

2/ If an AI-built feature hits production and something’s off (edge case, perf, auth, cost)… you need one thing: an instant "off" button.