Building a strong robust client-server system
I need some help with regards to implement a pre-designed system that has 4 components and several constraints. I’ve spent approximately 50 hours trying to determine the best way to build this system; however, I do not think I have a strong enough solution as of right now.
I need to start Getting Clients
How can I get clients or are there any available clients
Should we be completely honest to our clients about a time frame for a project?
I have been having this experience for sometime now, when a client needs a software product and contacts me, the client usually wants to know the time frame on which this product will be accomplished. Usually as a software developer I might not be able to fully determine how long it will take me to finish the job since I may encounter an error that may take me weeks (sometimes months) to solve.
Should we be completely honest to our clients about a time frame for a project?
I have been having this experience for sometime now, when a client needs a software product and contacts me, the client usually wants to know the time frame on which this product will be accomplished. Usually as a software developer I might not be able to fully determine how long it will take me to finish the job since I may encounter an error that may take me weeks (sometimes months) to solve.
Should we be completely honest to our clients about a time frame for a project?
I have been having this experience for sometime now, when a client needs a software product and contacts me, the client usually wants to know the time frame on which this product will be accomplished. Usually as a software developer I might not be able to fully determine how long it will take me to finish the job since I may encounter an error that may take me weeks (sometimes months) to solve.
Should we be completely honest to our clients about a time frame for a project?
I have been having this experience for sometime now, when a client needs a software product and contacts me, the client usually wants to know the time frame on which this product will be accomplished. Usually as a software developer I might not be able to fully determine how long it will take me to finish the job since I may encounter an error that may take me weeks (sometimes months) to solve.
Should we be completely honest to our clients about a time frame for a project?
I have been having this experience for sometime now, when a client needs a software product and contacts me, the client usually wants to know the time frame on which this product will be accomplished. Usually as a software developer I might not be able to fully determine how long it will take me to finish the job since I may encounter an error that may take me weeks (sometimes months) to solve.
constants/enums in API
What are a few ways constants and enums are dealt with when creating an API Client? I’m writing a client in python for our API and I’ve hit a sticking point with this. We use a lot of mappings to numbers (to save space) and I was wondering what the best technique is. I can hard code them into the client, but if a new enum/constant gets added, the consumer would have to update his version of the client. I also thought about grabbing the maps/enums when the client is first initialized and cached until there is an update. Are these typical approaches, or is there a more effective way to do this?
constants/enums in API
What are a few ways constants and enums are dealt with when creating an API Client? I’m writing a client in python for our API and I’ve hit a sticking point with this. We use a lot of mappings to numbers (to save space) and I was wondering what the best technique is. I can hard code them into the client, but if a new enum/constant gets added, the consumer would have to update his version of the client. I also thought about grabbing the maps/enums when the client is first initialized and cached until there is an update. Are these typical approaches, or is there a more effective way to do this?
Make an app that communicates with an app on a server over wifi [closed]
Closed 10 years ago.