Incomplete project opinion

FatStratCat

I have a project that was abandoned by a programmer I hired. He just disappeared when it was probably 95% done. Sucks, because I paid for it and can't use it.

So I wanted to ask the opinions of those with a lot of experience custom designing Php/mysql database websites (programming wise) what they would suggest.

Is it easy to jump into someone elses project that is mostly done and try to figure out what is left to complete it? I have to make some decisions about what to do with this pile of crap, whether to pursue completion, strip it down and build it back up, or just begin over.

It's not a critical part of the things I do, but It would make life a lot easier for sure. It's one of several reasons I've decided to take on learning php, so I can begin to develop things myself. I've been through 3 programmers, don't wanna deal with that any more.

So what do you experts think? Should I bail on it, or try and get the dang thing finished?

FYI it is a billing program., so there are lots of calculations .

pohopo

If it is 95% done then you should just finish it.

FatStratCat

You know how when you run a PC in safe mode you can have it so that each of the steps in the boot process is listed so you can see what starts up and find where the problems are?

Is there something like that for a menu driven php webpage? For example, say my menu has a button that says "Open up billing period for 01/15/06", is there a program that would show me the steps it takes from that point forward to the next user input place, or do I just have to study the code and figure it out little by little?

Sorry if that's a dumb question. I thought if I could see how he laid out the whole thing, I would know where to pick it up.

Three programmers in, my website looks a little like grandmas attic. 🙁

pohopo

Certain editors have debuggers that let you run the code step by step. If you are new to development though it might be tricky for you to set the debugger up. You should logically be able to follow the code also by just looking at it.

khendar

What you could do is build a testing regime. Develop use-case scenarios for each of the projects major functions, and run them on the system, verifying the results of calculations, returns, data formatting, any bugs encoutered etc. Map all of this thoroughly and you should have a good basis for completing the development.

FatStratCat

khendar wrote:
What you could do is build a testing regime. Develop use-case scenarios for each of the projects major functions, and run them on the system, verifying the results of calculations, returns, data formatting, any bugs encoutered etc. Map all of this thoroughly and you should have a good basis for completing the development.

The guy who abandoned this project did that. He had a test database, with some fake records, and he ran all of his stuff on that, but,,,

I'm still learning, and I don't know how to do all that yet. I still have to figure out how every thing is linked together

khendar

Draw a map 😃

Might sound stupid but when I'm trying to debug something or track data flow through a program I draw a map of all the files/function/scripts etc and how they link up.

FatStratCat

khendar wrote:
Draw a map 😃

Might sound stupid but when I'm trying to debug something or track data flow through a program I draw a map of all the files/function/scripts etc and how they link up.

I figure a flow chart will do it.

The only part that will be hard is where the roads dead end.

But I'll figure it out. Thanks for the advice.

I do look forward to the day when I'm able to do stuff like set up a fake database, one that won't impact the real one.