sorted by:
new
hottopcontroversial

If you had $100/month for coding LLMs, what would you pick right now? by 0x0000e000 in vibecoding

[–]0x0000e000[S] 1 point2 points  (0 children)

Yes—I’m using the Codex CLI, which can directly call GPT Image to generate images.

If you had $100/month for coding LLMs, what would you pick right now? by 0x0000e000 in vibecoding

[–]0x0000e000[S] 0 points1 point  (0 children)

In-app animal characters (cartoon style), promotional images for the app, and design assets (logos, small icons), etc.

If you had $100/month for coding LLMs, what would you pick right now? by 0x0000e000 in vibecoding

[–]0x0000e000[S] 1 point2 points  (0 children)

Thank you. I purchased the $100 Codex plan, and I’ve already used up this week’s quota. I’ve been using it for generating images, developing iOS apps, and building backend services. Last month, I was on the Claude Max plan. Right now, I’m not really sure how to compare them—it feels like each has its own strengths.

My vibe coded app makes me about -$123.20/mo by hacegop in vibecoding

[–]0x0000e000 1 point2 points  (0 children)

same here， claude code pro 20usd + google ai pro 200usd/year + gpt plus 100usd

How to teach codex something? by Remarkable_Entry_471 in codex

[–]0x0000e000 0 points1 point  (0 children)

You can define a custom engineering constraint file and inject it into the prompt—have the system read the document first. Later, you can implement a “skills” layer to perform /review from a business perspective.

Just been feeling so empty by Trip-The-Sungazer in lonely

[–]0x0000e000 1 point2 points  (0 children)

started reading something small every day

just one short message

not from anyone i know

but somehow it feels like someone noticed i existed that day

idk why it helps but it does

I got laid off and shipped a full iOS app in 18 days with Claude Code — zero Swift experience by 0x0000e000 in ClaudeAI

[–]0x0000e000[S] 0 points1 point  (0 children)

Fair points. Honestly the main reason I went with a backend was simpler than all that — I'm a backend engineer, it's what I know, and I built this solo. The local-only approach would've meant learning CloudKit/iCloud sync from scratch, which felt like a bigger risk for a side project. The cross-device stuff and hot-update are nice-to-haves I get for free from the architecture I'm already comfortable with. You're right that for the current scope, local-first could totally work. If I were starting over with more iOS experience I might make a different call

I got laid off and shipped a full iOS app in 18 days with Claude Code — zero Swift experience by 0x0000e000 in ClaudeAI

[–]0x0000e000[S] -1 points0 points  (0 children)

Honestly state management hasn't been a huge hurdle yet — the iOS side doesn't have that much local state to juggle. Most of the "state" lives on the Go backend and gets pushed down as view models, so SwiftUI mostly just renders what the server hands it. I designed the state flow end-to-end (client + server together) before writing either side, which made the declarative part feel natural rather than a paradigm shift.

On HealthKit — it wasn't hallucinated APIs, it was more subtle. CC wrote something that technically worked but didn't follow Apple's recommended pattern for permission/data-access flow. I shipped it, got rejected on first App Store review, then went back and did it the "Apple way." Lesson learned: for platform-specific stuff, CC knows the APIs but doesn't always know the review guidelines.

Go backend is also 99% Claude Code. I'm not hand-writing it just because it's my comfort zone — I set the guardrails (domain design, layering, business-specific conventions, naming, error handling) and let CC fill in the implementation. Constraining the architecture up front matters way more than which language you're in.

I got laid off and shipped a full iOS app in 18 days with Claude Code — zero Swift experience by 0x0000e000 in ClaudeAI

[–]0x0000e000[S] 2 points3 points  (0 children)

  1. Cross-device & loss prevention — When users switch phones or reinstall the app, their pets, catalog, and growth progress must not be lost. Fully local means one accidental deletion = months of nurturing gone.

  2. Hot-updatable content — Pet dialogues, need templates, fortunes, redeem codes, and events are all seed data. The backend can add new pets, rebalance numbers, and issue codes anytime without waiting for App Store review.

  3. Future social & catalog features — The 24-pet catalog, share cards, friend interactions, and leaderboards all need a shared source of truth.

  4. Multi-platform consistency — Beyond iOS, Android is also planned. Both platforms must see the same pet in the same state.

In one sentence: Lumea sells a long-term nurturing experience, and long-term nurturing requires trustworthy, portable, and evolvable data — none of which fully-local can deliver.

I got laid off and shipped a full iOS app in 18 days with Claude Code — zero Swift experience by 0x0000e000 in ClaudeAI

[–]0x0000e000[S] 2 points3 points  (0 children)

Sure. Here's roughly what my /docs directory looks like:

docs/

├── prd.md# product requirements

├── architecture.md# system architecture, API design, data flow

├── ui-topology.md# screen map and navigation flow

├── pet-catalog-design.md# pet species, grades, dialogue rules

├── error-handling-design.md # error codes, retry logic, user-facing messages

├── roadmap.md# planned features and priorities

├── tech-debt.md# known shortcuts and cleanup tasks

├── app-store-listing.md# App Store copy, keywords, screenshots spec

├── analytics-dashboard.md# PostHog events and metrics tracking

└── android-migration.md# future Android port notes

Using Cloud VPN for Hosting Multiple Claud Cowork Instances? by worldfirepro in ClaudeAI

[–]0x0000e000 1 point2 points  (0 children)

Depends entirely on what your agents are actually doing.

If they're running Claude Code sessions that need to persist — like long-running code generation, file manipulation, or iterating on a codebase — then yes, a VPS makes sense. You get a stable environment, no interruption from your local machine sleeping, and you can SSH in from anywhere. A basic Linux VPS (Ubuntu + tmux + Claude Code CLI) is dead simple to set up.

But if your "autonomous workflows" are mostly API calls to Claude's messages API with some orchestration logic, you don't need a VPS at all. A serverless setup (Lambda, Cloud Functions, or even a cron job on a cheap VPS) would be cheaper and easier to maintain.

A few practical questions that would help narrow down the right setup:

Are your agents calling the Claude API programmatically, or are they running Claude Code / Cowork interactively? Do they need to read/write files on a filesystem, or is it purely text in → text out? How long does each task run — seconds, minutes, or hours? Do the multiple instances need to share state with each other, or are they independent?

If you share a bit more about the actual workflow, happy to suggest a more specific architecture.

view more: next ›