Restarting this account. I'm a solo indie dev building 5 products at once - a fishing app, a beta testing platform, a macOS cleaner, a TCG collector app, and a minimalist project tool. Going to share the real build, the real numbers, the real mistakes. 🧵
@farukmertkapar The dust settling into the plan reads really well. Curious how you built it: particles sampled from a snapshot of the goal row in a Canvas, or a Metal shader through .layerEffect?
@Codelaby Nice shape. If you animate the reels later, putting .rotationEffect inside a TimelineView(.animation) keeps the spin smooth and lets you tie speed to play/pause state. Did you draw it with addArc segments or one path loop?
@GodsBoy7777 Agreed on the failing case. One cheap trick: have it run xcrun simctl io booted recordVideo before.mp4 on the repro, then again after the fix. Two short clips in the handover beat a "works now" summary.
@mayank0324 Nice. One thing that creeps up with SwiftPM-only builds: every project keeps its own .build folder and they get big. rm -rf .build on repos you're not touching is safe, it just rebuilds next time.
@imsonup_ For evals, pin the sim state per run: xcrun simctl clone a golden device, boot it, erase it after. And simctl status_bar override (fixed time, full battery) keeps screenshots diffable between runs.
@whysumancode Congrats on #2. Curious how you handle the Screen Recording permission on Sequoia, since it can re-ask. Have you tried SCContentSharingPicker for the recording flow? The user picks the window in the system UI, so the grant feels less scary.
@UniekLee Makes sense. A middle ground some teams use: snapshot only a few key screens, run them in PR checks, and keep the reference images in Git LFS so the repo doesn't balloon.
@dani_avila7 Nice. Worth checking build outputs too: .next, dist, Rust target/ and a separate Xcode DerivedData folder per worktree often outweigh node_modules. With pnpm all worktrees share one store via hard links, so node_modules stays cheap and git worktree remove frees the rest.
@gordysc That's a full target/ per worktree. cargo sweep --time 3 clears old artifacts in each one, and debug = "line-tables-only" under [https://t.co/F5sacQARHL] makes every build a lot smaller. Also worth deleting target/ in whatever removes a merged worktree.
@criccomini Same pain here. Two things that shrink it: set debug = "line-tables-only" under [https://t.co/F5sacQARHL] in Cargo.toml (debug info is most of target/), and run cargo sweep --time 7 in each worktree to drop stale artifacts. Deleting target/ when a worktree merges frees the rest.
@Jay__Coder The permission part is the real question. On macOS it needs Accessibility and Screen Recording, which is close to full control of your session. I'd run it under a separate macOS user or a spare Mac so it can't see your mail or password manager.
@_wickyjohn Good one. If the list is long, tmutil thinlocalsnapshots / 999999999999 4 clears them now. For devs the other big ones hiding in System Data are ~/Library/Developer/CoreSimulator, Xcode DerivedData and Docker.raw. I'm building a Mac app for exactly this, DevCleaner.
@VictorMotricala Tip if you try this: give the agent its own simulator (xcrun simctl create) and boot it by UDID, so it never taps around in the one you're using. xcrun simctl io <udid> recordVideo run.mp4 gives you a replay of every tap to review later.
@priyank_sharma One thing that helps: give the agent its own simulator with xcrun simctl clone, then erase it after each run. Keeps your main device's state out of the test and stops old sim data piling up in CoreSimulator/Devices.
@fagnersales25 Check where it actually goes first: du -sh ~/Library/Developer ~/.npm ~/.cache ~/Library/Caches. With agents it's often one node_modules per worktree, so git worktree prune plus a shared pnpm store helps. Docker.raw is another big one.
@never_settles_ If the envs run in Docker, docker system df shows where it goes, build cache is often the surprise. ~/.cache/uv and ~/.cache/huggingface are the other usual suspects. Datasets can live on an external SSD behind a symlink.
@lotus_sbc Same problem with many side projects. The big ones for me are node_modules in projects I haven't opened in months, .next and build caches, and Xcode DerivedData. I'm building a Mac app for exactly this, DevCleaner.
@claudioatilano Same here. Each agent worktree gets its own node_modules and build folders. pnpm helps a lot since worktrees share one store via hard links, and git worktree remove after merging frees the rest.