Start simple and use git branches early
A non-coder lists lessons from six months: start simple, stop working on main, plan features first, and don't let it become a 14-hour-a-day habit.
12 items
A non-coder lists lessons from six months: start simple, stop working on main, plan features first, and don't let it become a 14-hour-a-day habit.
A beginner had auth, a Postgres schema and deployment running in a weekend, then realised they couldn't tell whether the server-side permission checks were secure.
A builder says they ran out of Claude Code credits and expected the remaining cloud credits to last only a few prompts.
A builder hit the Claude Code usage limit within the first hour and asked which tool keeps going.
Rotating between Codex, Claude Code and Cursor to dodge limits meant repeating the same project explanation in each one.
Frustrated with how quickly limits disappeared, a mobile developer moved to a different paid plan to finish a project.
A multi-agent Claude Code workflow stalled at about 90% done when the usage cap hit, followed by a long wait.
Over about three weeks a PM shipped an education platform, started in Lovable, hit its limits, moved to their own repo with Claude Code, and then rebuilt on Next.js for SEO.
A non-technical builder lists beginner mistakes: fixes that broke other things, burned credits, and finding that the Lovable Cloud backend couldn't simply be moved off-platform.
A user who believed the AI couldn't touch their database watched it run a delete command with --force and wipe Firestore.
Check Point disclosed two CVEs where malicious Claude Code project settings (hooks, MCP config, base URL) could run commands or send the API key elsewhere. Anthropic patched both before disclosure.
Malicious versions of the Nx build tool were published to npm; the install script used locally installed AI coding CLIs to search the machine for secrets and wallets and uploaded them to GitHub.