I purchased rights to open-source dating software, and sent out a proposal for substantial modifications to a programmer who came highly recommended from another dating site owner using the same platform.
I was quoted two prices and two options, Here is what he said:
"After clearly understanding the amount of work required, I estimate that it would take around 320 hours of coding. That means it would take around 8 weeks to complete the task ... There is also another plan with around 240 hours of coding and 6 weeks for completion ... The difference between the two is level of accuracy, stability and standardization of code (which means that while making your functions functional, I also take care of the unwarranted conditions that may or may not happen). That makes your website robust, stable, and your website do better error handling for fast debugging. In first case the code is well documented and tested to make it robust and easy for future integration/upgrades, but in later case emphasis is on towards completing the features. You will get your work done in both cases with the functionality you mentioned. But the differences are clearly mentioned."
Option # 2 costs 25 percent more than Option # 1.
Ultimately I decided I would do some 80/20 analysis, prioritize the proposed modifications, then break the modifications into phases, with an eye to getting the site on the market sooner than later. Some features (like blogging, for example) are just not that important to what I am trying to accomplish and can wait for a subsequent upgrade. .
In any event ... I know very little about programming and it does not make sense for me to try to become an expert in it. I'll stick to site design and marketing. So I have a few questions (if you don't mind my asking).
First: How important do you suspect the optional "code standardization" is in the big picture ...? Is this essential ... or do you think the potential "debugging" issues can be just as easily addressed at some later date if and as they arise?
Second: (and I know this is a rookie question for programmers) ... what is the main cause of bugs? Faulty programming ...? Or faulty hardware ...?
Thanks!
I was quoted two prices and two options, Here is what he said:
"After clearly understanding the amount of work required, I estimate that it would take around 320 hours of coding. That means it would take around 8 weeks to complete the task ... There is also another plan with around 240 hours of coding and 6 weeks for completion ... The difference between the two is level of accuracy, stability and standardization of code (which means that while making your functions functional, I also take care of the unwarranted conditions that may or may not happen). That makes your website robust, stable, and your website do better error handling for fast debugging. In first case the code is well documented and tested to make it robust and easy for future integration/upgrades, but in later case emphasis is on towards completing the features. You will get your work done in both cases with the functionality you mentioned. But the differences are clearly mentioned."
Option # 2 costs 25 percent more than Option # 1.
Ultimately I decided I would do some 80/20 analysis, prioritize the proposed modifications, then break the modifications into phases, with an eye to getting the site on the market sooner than later. Some features (like blogging, for example) are just not that important to what I am trying to accomplish and can wait for a subsequent upgrade. .
In any event ... I know very little about programming and it does not make sense for me to try to become an expert in it. I'll stick to site design and marketing. So I have a few questions (if you don't mind my asking).
First: How important do you suspect the optional "code standardization" is in the big picture ...? Is this essential ... or do you think the potential "debugging" issues can be just as easily addressed at some later date if and as they arise?
Second: (and I know this is a rookie question for programmers) ... what is the main cause of bugs? Faulty programming ...? Or faulty hardware ...?
Thanks!
Dislike ads? Become a Fastlane member:
Subscribe today and surround yourself with winners and millionaire mentors, not those broke friends who only want to drink beer and play video games. :-)
Access Restricted: Unlock 1,000,000+ Posts
Stop Peeking Through the Keyhole.
Open the Door.
You hit a wall because the best advice isn't free—it's earned. Since 2007, MJ DeMarco has been active here daily (99.9% active rate), building a war room for entrepreneurs who refuse to settle for mediocrity.
- Active Daily: Life-changing content posted dozens of times every day. No dead threads.
- MJ's Inner Circle: Direct access to the author of The Millionaire Fastlane.
- Vetted Network: Connect with founders scaling to 7 and 8 figures.
- Proven Roadmaps: Strategy over motivation. Execution over "hustle porn."
"SCALED TO 6-FIGURE MONTHS"
"Tips and advice here saved me from huge mistakes, others allowed me to scale my business to 6-figure months."— User MitchC
"INSANE QUALITY OF PEOPLE"
"The number of high quality people I've met from this forum has been insane. All of it predicated on building real value."— User Richard Peck
"You are the average of the five people you surround yourself with."
Are you surrounding yourself with success?
