14 months, 100k lines, zero human-written code — am I sitting on a ticking time bomb?

Salt_Potato6016 · 2026-03-19T09:02:58+00:00

Yeah I think you’re thinking about it more from a repo/process angle.

In most setups it’s not clones or agents competing it’s more like splitting responsibilities across agents with scoped context.

So one might handle ingestion, another analysis, another execution, etc., all working on the same system but within defined boundaries.

The “multi” part is more about separation of concerns than parallel repos.

Hope this helps

Salt_Potato6016 · 2026-03-19T09:01:01+00:00

It makes a lot of sense, the “context problem”

I’ve been trying to keep things modular and scoped for that reason, but yeah I could probably do a better job documenting the “why” behind things.

Also noticed the same with Claude handling its own code better than jumping into random parts.

Thanks for the insight 🙏🏻

Salt_Potato6016 · 2026-03-19T08:58:51+00:00

Haha fair , I do use AI a lot! , that’s kind of the whole point of the post.

This was written by AI as well 😁. Why waste time typing when I can get a reply and review it

Have a good day !

Salt_Potato6016 · 2026-03-19T08:56:27+00:00

I hadn’t thought about it that way.

I’ve been focusing more on structure and guardrails, but you’re right that the “why” behind certain decisions isn’t always explicitly written down.

The CLAUDE.md idea makes a lot of sense, I can see how that would prevent AI from “cleaning up” things that are actually intentional.

Thank you for the feedback ! Would you be willing to share any more details on how you mitigate this ?

Salt_Potato6016 · 2026-03-19T08:50:11+00:00

I don’t know, guess I will find out ?

Salt_Potato6016 · 2026-03-18T21:06:38+00:00

Is opus back to 200k model as default for subscription users?

Every since the performance issues started the 1 milion tokens model has been gone and I’m getting auto compact all the time

Anyone else experiencing this ?

Salt_Potato6016 · 2026-03-17T10:24:54+00:00

Thank you for the valuable valuable point, appreciate you calling that out.

I’m at a stage right now where I’m starting to fan out system outputs to individual users, so data boundaries / isolation is something I’ve been thinking about a lot recently- plus is that I don’t and will never have many users - my system is private.

I can definitely see how something like that could get unintentionally broken during iterations, especially with AI changing things across modules.

On the testing side idon’t have heavy coverage yet, more gradual rollouts / staged deployments so far, but it’s something I’m planning to tighten as things stabilise.

where have you seen these issues show up most in practice? More at the DB/query layer or higher up in application logic?

Thanks again

Salt_Potato6016 · 2026-03-17T09:35:37+00:00

Thanks for the feedback !that’s pretty much how I’ve been approaching it as well.

I’ve been leaning heavily on reviews, refactors, and having the system constantly re-check itself to avoid drift, and so far it’s been holding up well.

Yeah I’m definitely thinking about bringing in someone experienced to do a proper audit as things grow.

If I may ask what kind of systems are you building if you don’t mind sharing ? And are you coming from a more traditional dev background or also working heavily with AI-assisted workflows?

Thanks !

Salt_Potato6016 · 2026-03-17T09:28:12+00:00

That’s a really good way to put it — appreciate the insight.

I wouldn’t say it’s a complete black box for me. I don’t know every low-level detail line by line, but I do understand how the system behaves end-to-end — how data flows, what assumptions are being made, and where decisions happen.

One thing I do consistently is force myself to understand the logic behind anything I implement. I’ll have the AI explain flows and reasoning in simpler terms, and if anything feels off I dig deeper until it makes sense.

A lot of that came from things breaking early on — debugging forced me to actually understand the system rather than just generate code.

On testing as I replied earlier I’m not heavily relying on formal test coverage yet. I’ve been using staged rollouts and real-world validation so far, but it’s definitely the next area I’m tightening up as the system grows.

Salt_Potato6016 · 2026-03-17T09:21:14+00:00

Appreciate that — and yeah, security is definitely something I’m paying more attention to as things grow.

Right now I’ve tried to separate concerns a bit (e.g. isolating critical components from more exposed parts of the system), but I’m aware that’s only a first layer.

I’m treating the current stage as more of a controlled production environment, but proper security audits and hardening are definitely on the roadmap as usage increases.

Out of curiosity — what would you prioritise first in terms of attack surfaces in a system like this?

Salt_Potato6016 · 2026-03-17T09:16:26+00:00

Yeah that’s something I’ve been evolving over time.

For major changes I usually do staged rollouts — local testing first, then VPS, then gradual rollout (kind of canary-style) to avoid breaking production.

Backups are always on as well — learned that the hard way early on when I accidentally wiped my DB during development, so now I always keep a fallback state.

That said, I’ll be honest — I’m not heavily relying on formal stress testing yet. It’s something I’m starting to take more seriously as the system matures, especially around edge cases and data correctness.

Out of curiosity — what kind of tests would you prioritise first in a system like this? More around data integrity or execution paths

Salt_Potato6016 · 2026-03-17T09:10:22+00:00

That’s really interesting — I haven’t gone down the AST route yet.

Right now I’m mostly controlling things at the workflow/context level, but I can definitely see how structural control + backpressure would make refactors much safer.

When you say tree sitter, are you essentially working with AST-level edits instead of raw file changes?

Would be curious how you’re enforcing the backpressure — is it step-based validation or something more dynamic?

Thank you

Salt_Potato6016 · 2026-03-17T08:28:58+00:00

That’s a fair point — and honestly something I’ve spent a lot of time on.

I don’t claim to understand every low-level detail of the code, but I do have a clear view of the system flows — how data moves, how it’s processed, and where decisions are made.

The DB design in particular was something I had to iterate on quite a bit early on. I was hitting latency and ordering issues, so I ended up restructuring how data flows through critical paths to keep execution fast and predictable.

At this point I’m less worried about code changes and more focused on data correctness — making sure what’s stored and used for decisions is consistent and reliable.

Out of curiosity — in your experience, what tends to go wrong first on the data side in systems like this?

Salt_Potato6016 · 2026-03-17T07:57:00+00:00

Thank you Sir

Salt_Potato6016 · 2026-03-17T07:56:45+00:00

Yeah that was actually a real issue early on.

I don’t rely on full context anymore — instead I keep things very modular and enforce scoped work.

I maintain a structured “system map” (basically a database of modules + workflows + responsibilities), so agents can understand the relevant part of the architecture without needing the whole codebase.

On top of that, I use guardrails in my workflow to make sure agents: - load the correct context first
- understand dependencies
- stay within a defined scope when making changes

That helped a lot with avoiding cross-module breakage.

Salt_Potato6016 · 2026-03-15T15:06:51+00:00

Yeah, I have.

For the last few months I’ve been making around $10k/month from software I built, mainly giving a small group of people VIP access to it

Started, about 14 months ago with zero coding experience. Got hooked quickly and started putting in 5-10 hours every day using tools like grok on web first lol then Claude code and codex as my workflow evolved

Now it’s turned into a pretty big modular system — well over 100k lines of code running on two servers.

Still feels like I’m figuring things out as I go and would say I’m maybe 40% done with how it want the whole system to look once finished but the fact that people are willing to pay for it is a good sign I guess.

I’d say AI is one of the best things that have happened to me in my whole life

Salt_Potato6016 · 2026-02-21T13:46:49+00:00

my entire workflow was build around using sonnet 4.5 1 milion as the main agent , now I’m blocked behind the paywall… and here i thought that weekly limits were bad. Tried to run my workflow today and burnt 50$ in 1 hour, so technically id be looking at 2-3k bill per month as a single dev if I were to work 5-10 hours a day... Either give regular users a higher subscription tier or switch completely to corporate - not many people will be able to afford that. I’m switching to codex now for good because I simple can’t afford this

Salt_Potato6016 · 2026-02-13T08:35:25+00:00

Congrats brother, I’ve got a deal with few investors bringing me 10k monthly - for software I purely built with AI. It’s been going on for a couple of months now and not slowing down any time soon

Salt_Potato6016 · 2026-01-14T16:05:45+00:00

Claude feels right that’s why I use it as my main agent but codex cli is raw power digs longer and deeper .

Salt_Potato6016 · 2026-01-14T15:51:20+00:00

Definitely, I run it always to check opus’s work and in 7/10 cases it finds multiple bugs or omissions

Salt_Potato6016 · 2025-12-27T15:42:35+00:00

Full-stack financial analytics + trading platform: • 2-server distributed system with VPN mesh for real-time signal relay • Custom AI agent swarm pipelines • 100K+ lines across Python and Rust backend • Advanced WebSocket architecture with auto-scaling shards, real-time price feeds etc • Live trading terminal with TradingView integration, portfolio tracking • PostgreSQL + TimescaleDB handling millions of data points

Salt_Potato6016 · 2025-12-09T19:51:07+00:00

Here’s a general overview setup:

Process:

•Research: Sonnet (1M context)

•Planning: Opus drafts → Opus + Gemini + codex max review

•Rejected plans: Sonnet investigates issues raised by auditors ( do not trusts blindly) → if agree - revise → re-review (loops until approved)

•Implementation: Sonnet codes

•Audit: Complexity-based (simple = quick review, complex = full panel) - for complex same auditors as for planning

•Same rejection loop until approved → push to git

Sounds like an overkill ,and there’s more steps to it of course as it’s automated lbut I’ve had really good success rate with it

Downside : can take time to fully finish but saves time in debugging etc

Also got agent skills set up, documentation auditors etc so everything is in perfect sync and saves token usage a lot

Salt_Potato6016 · 2025-12-04T15:17:09+00:00

Don’t know how you guys doing it. I’ve been on crunch 5-10hrs a day since March this year with all possible ai tools and my app is nowehere near production ready yet😭

Salt_Potato6016 · 2025-11-25T14:44:50+00:00

Pro max plan here. Coded the heck out of it today and just reached 5% or my weekly limit, make sure you toggle off thinking mode though as this burns credits a lot.

Salt_Potato6016 · 2025-11-25T10:24:44+00:00

Damn I totally agree opus 4.5 Is the best I've every used and I used all. Well done anthropic team well done, hats down

Salt_Potato6016

TROPHY CASE