This communication has been the root cause (in my opinion only) of why this project failed, why faddat got banned from github, and why there is animosity present. Programmers often have a habit of speaking in very simple, logical statements, and don't format it for a non-programmer to fully understand.
This is why every software company has front end departmental managers that speak to the management on behalf of programmers. These IT department managers who manage the project often sit in the boardroom with the customer and do translations between client <---> programmers because it is an art to get everyone on the same page with real expectations of what is possible and not possible.
Here we had a client, talking directly to a coder. The business relationship and the project itself failed as a result. It is not recommended, "especially for large projects" for it to be set up this way.
This communication has been the root cause (in my opinion only) of why this project failed, why faddat got banned from github, and why there is animosity present. Programmers often have a habit of speaking in very simple, logical statements, and don't format it for a non-programmer to fully understand.
This is why every software company has front end departmental managers that speak to the management on behalf of programmers. These IT department managers who manage the project often sit in the boardroom with the customer and do translations between client <---> programmers because it is an art to get everyone on the same page with real expectations of what is possible and not possible.
Here we had a client, talking directly to a coder. The business relationship and the project itself failed as a result. It is not recommended, "especially for large projects" for it to be set up this way.
Best I could do under the circumstances.
Sorry.