If I create a CRM and I needed web developers to work on the CRM, would web devs not work on it if it was not successful?

So web developers will do this, is this apart of web development?

What "this"? What do you mean by "work on it"? Web developers do web related stuff, you need to be more specific.

Like improve the code.

I don't see why a developer wouldn't do it, properly rewarded especially.

Okay

So if the code is bad, then you would not work on it?

If the code is bad, I would make it maintainable.

No what I mean is I know my code won't be that bad and if I put effort into it and build a REI CRM then if I start to hire web developers to join my team, my question is will a web developer see my REI CRM code and say this does not seem like good code I think I will pass. Or will some web developers I think the word is "refactor" and like if they think for example, "You failed to add a http status code like 200" or "You did not add a API resource", or "You have used way to many if statements and can be easier maintained like this:

if('votes' == 100){
}

if('age' > 35){
}
etc...

and the web developer says this can be done easily with Eloquent ORM like this

$user->posts()->where('votes', '=', 100)->where('age', '>' , 35)->get();

or the web developer wants to add something I have never hear of before (which would be a good thing) like "middleware", which I do know what it is but it's just an example.

So would a web developer try to refactor this and modify it since the REI CRM has already active users and is generating some revenue? Or will the dev just look at the code and say "I'll pass".

And no I don't mean hiring a web developer to use the REI CRM. I mean if he can work with me to improve the REI CRM, or even if I can get team of 2-3 they can improve the REI CRM, not me.

If it's working code just needing some refactoring, why wouldn't they.

Okay thanks.

Depends on your requirements.

I just realized that I'm not a developer, I'm an engineer.

A developer may work on anything if you pay them enough, but an engineer knows when to stop because the project is no longer worth the time, money, or technical debt. Developers are often focused on delivering code; engineers are expected to evaluate whether the system, business model, and long-term economics actually make sense.

That’s why some people can recognize a failing project early and walk away before the collapse becomes obvious to everyone else.

@digitalartisan So what about “engineers“ that have worked on projects where a load of money has been sunk into it, and the project’s then failed or just been canned? Such as Metaverse, Apple Car, Windows Phone, etc?

If I were to build a successful MVP, would I need engineers? I would only want the code refactored until I would actually need others like DevOps, QA, UX, and Frontend Web Developers, etc...

@martinbean That’s exactly the point. Even good engineers work on projects that fail. The difference is whether they recognized the risks, communicated them, and understood when the economics or technical direction stopped making sense.

@june92 For an MVP, you usually don’t need a full engineering organization. You need enough technical skill to validate the idea quickly and avoid painting yourself into a corner.

@digitalartisan so you are saying I just have to enough technical skill to understand why the web developer or web developers refactored the code. So if I had built an MVP and the new web developers working on the MVP said I refactored the validation logic you had for the Contact Controller to have a Form Request Validation. This is not a good example it is very simple and I know that validation logic should be in Form Requests. But what I am trying to say this is the "technical skill" I should have so that I can validate the code the web developer just reviewed with me. There will be way more advanced code the web developer will review with me but that is the "technical skill" you are referring to correct? Or what do you mean "enough technical skill to validate the idea"?