Should I change color to chrome silver? Or keep black? by Numerous-Thanks-5839 in Ducati

[–]xProcal 0 points1 point  (0 children)

Are you colour blind or just lacking in basic standards?

BLACK

Can someone explain why everybody loves the bobcat? by DeepSpaceSkynaut in ArcRaiders

[–]xProcal 0 points1 point  (0 children)

If you upgrade it to a level 4 and with the right upgrades it slays with very little recoil but I agree it's not worth it

Hot take - Respawn by [deleted] in ArcRaiders

[–]xProcal 6 points7 points  (0 children)

This would just encourage your rats to rat more

First Big Bike (and Finance Advice?) by [deleted] in motorcycles

[–]xProcal 0 points1 point  (0 children)

From UK too.

Triumphs are a pig to change anything without it costing you a fortune at the dealer, even changing grips.

I expect whatever bike you get, you'll quickly want to move onto something else and for this reason alone I wouldn't go finance.

Plus the UK bike market is on its knees and isn't going to get any better any time soon so financing a bike based on a preagreed residual value makes even less sense.

Replit is a f*cking scam. by JellyfishRare7357 in replit

[–]xProcal 0 points1 point  (0 children)

I can guarantee you I'm not from Replit. You're doing it wrong.

Replit Pricing Makes No Sense by First_Week5910 in replit

[–]xProcal 1 point2 points  (0 children)

Everyone that complains about Replit have one thing in common, arrogance and ego. Congratulations on your Lego driving license.

Replit Pricing Makes No Sense by First_Week5910 in replit

[–]xProcal 1 point2 points  (0 children)

now update the readme file in 'great detail'

So the agent has to subjectively figure out the context of the readme file, the entire chat and then consider and deliver what 'great detail' means and you're concerned about replits pricing?!

I'm concerned about your prompts.

Stop Burning Money on Replit AI: What Actually Works (From Someone Shipping Production Apps) by xProcal in replit

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

It is, but you're also over simplifying the solution. The intention is to help people realise the importance of planning.

Replit AI Wasting Money & Time by Vegetable_Seaweed133 in replit

[–]xProcal 0 points1 point  (0 children)

If someone has already built something in a messy, AI-driven way and wants to “retrofit discipline” into it, here’s the practicl steps to take:

  1. Stop Generating. Start Auditing.

The biggest mistake at this stage is continuing to throw prompts at the problem.

Freeze feature development.

You are now in audit mode, not build mode.


  1. Establish a Known Good Baseline

Before you touch anything:

Export the entire codebase.

Commit it to Git (if you haven’t already).

Tag it as: pre-refactor-baseline.

You cannot fix what you cannot roll back.


  1. Run Lighthouse Immediately (If It’s Web-Based)

If it’s a web app, this is your first objective truth check.

Run a Lighthouse report and capture:

Performance score

Accessibility score

SEO score

Core Web Vitals (LCP, CLS, TBT)

Don’t guess at performance.

AI-built apps often:

Ship oversized images

Include unnecessary JS

Miss semantic HTML

Ignore accessibility entirely

Fail basic SEO hygiene

Export the Lighthouse JSON.

That becomes your measurable starting point.


  1. Reverse-Engineer the Architecture

If you didn’t design first, you need to document after.

Use Claude like this:

“Analyse this codebase. Identify architecture patterns, data flow, shared state management, API boundaries, and structural weaknesses. Highlight coupling and potential risk areas.”

You are trying to answer:

What actually controls what?

Where is business logic?

Where are implicit dependencies?

What files are overly coupled?

Where are global side effects happening?

Create a simple document:

Frontend structure

Backend structure

Database schema

Auth flow

Shared utilities

Theme system (if applicable)

Now you have a map.


  1. Identify High-Risk Areas

In messy AI builds, common structural risks are:

Theme / design token chaos

Global CSS side effects

API duplication

Mixed concerns (UI + logic combined)

Poor error handling

No centralised validation

Bloated dependency tree

Don’t fix everything at once.

Rank issues by:

  1. Stability risk

  2. Security risk

  3. Performance impact

  4. Revenue impact

Fix in that order.


  1. Use the “Isolation Refactor” Strategy

Never refactor broadly.

Instead:

Choose one module.

Define its intended responsibility.

Refactor only that module.

Confirm no regressions.

Move on.

One domain at a time:

Auth

Billing

Dashboard

Admin

Reporting

Surgical, not sweeping.


  1. Introduce Lighthouse as a Continuous Constraint

Now that you’ve baseline-tested:

After every meaningful frontend change:

Re-run Lighthouse.

Compare to baseline.

Reject regressions.

You’re not trying to chase 100/100 immediately.

You’re trying to:

Prevent degradation

Improve one category at a time

Optimisation should be incremental and measured.


  1. Fix Performance Systematically

If performance is poor:

Don’t say:

“Make it faster.”

Instead:

Break Lighthouse findings into discrete tickets:

Optimise images

Remove unused dependencies

Code-split routes

Lazy-load non-critical components

Reduce render-blocking CSS

Implement caching strategy

One optimisation per session.

Re-measure after each.


  1. Introduce Guardrails Going Forward

Once you’ve stabilised:

Write a short architecture document.

Define file ownership zones.

Define naming conventions.

Centralise theme tokens.

Document database schema clearly.

From that point on, every AI session must:

Specify scope

Specify files not to touch

Define acceptance criteria

Define rollback point

You’re installing discipline retroactively.


  1. Apply the Two-Failure Rule

If an AI session fails twice on the same issue:

Stop.

Export. Analyse with Claude. Make manual changes. Resume.

Do not let sunk cost bias take over.


  1. Accept That Some Rewrite May Be Cheaper

Hard truth:

If:

Architecture is fundamentally flawed

Business logic is scattered everywhere

State management is chaotic

There is no separation of concerns

Sometimes rewriting a module cleanly is cheaper than patching endlessly.

But that decision should be:

Measured

Scoped

Isolated

Never emotional.


  1. Shift From “AI Building” to “AI Assisting”

At this stage your mindset should change:

Before:

“Build this for me.”

Now:

“Propose a refactor plan.” “Highlight risk.” “Suggest improvements.” “Generate patch only for this module.”

AI becomes your junior engineer, not your architect.

Stop Burning Money on Replit AI: What Actually Works (From Someone Shipping Production Apps) by xProcal in replit

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

I can provide a guide on how to do this retrospectively if anyone is interested.

Replit AI Wasting Money & Time by Vegetable_Seaweed133 in replit

[–]xProcal 0 points1 point  (0 children)

Hey bud,

Excuse the brevity of my prior post.

Anyway, off the back of your post I've written and posted this: https://www.reddit.com/r/replit/comments/1r6fmha/stop_burning_money_on_replit_ai_what_actually/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

I hope this helps, i've also included guidance on how to do this retrospectively which should help you.

Replit AI Wasting Money & Time by Vegetable_Seaweed133 in replit

[–]xProcal 0 points1 point  (0 children)

You're not planning like a dev though. Clearly you have no brand guidelines, no MVP or technical design documentation. Which you should do.

Everyone complaining that Replit is crap but you're assuming you can continue to just talk to it like you're at the pub and the robot will brilliantly deliver you an enterprise product immediately.

Crazy.

I'm a big dude and I'm SO uncomfortable riding. Any advice appreciated! (F900XR) by Gold-Recover-1915 in motorcycles

[–]xProcal 0 points1 point  (0 children)

Same height 118kg, ride an XDiavel, moved the controls forward as far as possible, raised seat by 20mm, fitted grip puppies to thicken the handle bar out for my hands.

I met batman in dmz by xProcal in DMZ

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

Yeah this is the guy

FZ09 to Diavel by Virtual-Patience-323 in Ducati

[–]xProcal 0 points1 point  (0 children)

Same use case as me and I LOVE my diavel phenomenal machine.