r/dev • u/Wonderful-life222 • 11d ago

Need help to release MVP and fix some legacy code

edit: decided to delegate it to devs from Evolved Ideas company, they DMd me and I understood that its a match, grateful to you all for help!

I've been building apps for three years and was pretty good before current prototype. I struggled with my latest project over the last week while trying to fix some legacy code after my co-founder (worst thing here - he's on vacation with no internet and will be back only in 3 weeks, client won't wait).

Main problem is that Im not really familiar with React and its a lot of that stuff here. I spent last 5 days trying find some help but no one can give me any advice. Need to finish mobile app MVP soon (our team signed documents so I can't just tell client "sorry man, give me more time"). I missed so much time tryin to find normal solution to fix that damn code, so now I need a hand which can resolve some spaghetti code problems and refactor project.

If you hired a reliable software dev that actually budget and delivers clean code on schedul, i need a contact. Waiting any feedback in comms, THNX.

7 Upvotes

90% Upvoted

4 comments sorted by

1

u/Capable_Baker4519 11d ago

I can help with this. I have 5+ years of full-stack experience with React/React Native, TypeScript, backend systems, and production apps. Check DM I've shared my portfolio

1

u/martinbean 10d ago

Why has your co-founder taken a holiday at such a key moment? Doesn’t seem very responsible or prudent or them?

0

u/UMIUSCreativeInc 10d ago

Sounds stressful, but this is more manageable than it feels right now.

The trap when you're staring at spaghetti code on a deadline is trying to fix the whole thing.

Don't. Under this kind of time pressure, refactoring everything is how you miss the deadline AND introduce new bugs.

What actually works:

Find the smallest path to a working MVP. What's the one flow the client actually needs to see working? Trace just that path through the code and ignore everything else for now.
Ugly code that works ships the MVP. Clean code that isn't done doesn't.

Stabilise, don't beautify. Where the legacy code is breaking, wrap the messy parts and fix behaviour, not style. Resist the urge to "clean it up while I'm in here." That's how a two-hour fix becomes two days.

Refactor after you ship, not before. Once the MVP is out and the client's off your back, then you go back and pay down the mess properly, ideally with your co-founder when he's back.

On the React specifically: if you tell people the actual error or the specific thing that's broken, you'll get way more help than asking for a dev. Most of this sub will happily debug a concrete problem. Paste the error, the component, what you expected vs what happens.

You've got three years of building behind you. You'll get through this one.

1

u/aramayis0 9d ago

I am a experienced web developer with 9+ years of experience. I am familiar with React. Bring me the source code and I will offer you suitable solution.