3 ms·

It sounds to me like you're worrying about problems you don't have. You're talking scalability and acquisition before you have a single line of code, let alone

by bwh2 17y ago

It sounds to me like you're worrying about problems you don't have. You're talking scalability and acquisition before you have a single line of code, let alone any users.

lauken 17y ago
Excellent point but isn't it prudent to take these factors into consideration before choosing a path? We don't want to dwell on the irrelevant but we would like to make a sound decision based on where we envision the product going. Do you have any words of wisdom for choosing a framework? Any recommendations?
- bwh2 17y ago
  Worrying about scalability and acquisition is not prudent at this stage, it's a waste of time IMO. Odds are that nobody will use your CMS. That being said, my advice is to get something up and running now and fail fast. I'm not a 37signals fanboy, but I think you should read: http://gettingreal.37signals.com/toc.php http://gettingreal.37signals.com/toc.php Your problem right now is to figure out what customers want. You need a product up and running. If you have a (good) HTML/CSS/JS/PHP developer on board who knows Drupal, he can probably get a Drupal+CCK prototype of your customized CMS up and running in a couple weeks, if not days. Who cares if Drupal isn't your long term solution? It just doesn't matter.
  - lauken 17y ago
    I am a huge fan of the 37signals content. As opposed to failing fast, we are attempting to do it right quickly. Some failures are the nature of the business but we are doing are best to take all parameters into consideration when making decisions. Thank you very much for your response. We truly appreciate the perspective and reminder that building products for and engaging customers is more important than the framework.
    - bwh2 17y ago
      Glad I can help. Just to be clear about one point: I'm not suggesting that you intentionally fail. Rather, I'm just suggesting you lower the cost of failure.

by bwh2 17y ago

It sounds to me like you're worrying about problems you don't have. You're talking scalability and acquisition before you have a single line of code, let alone any users.

lauken 17y ago

Excellent point but isn't it prudent to take these factors into consideration before choosing a path? We don't want to dwell on the irrelevant but we would like to make a sound decision based on where we envision the product going. Do you have any words of wisdom for choosing a framework? Any recommendations?

bwh2 17y ago
Worrying about scalability and acquisition is not prudent at this stage, it's a waste of time IMO. Odds are that nobody will use your CMS. That being said, my advice is to get something up and running now and fail fast. I'm not a 37signals fanboy, but I think you should read: http://gettingreal.37signals.com/toc.php http://gettingreal.37signals.com/toc.php Your problem right now is to figure out what customers want. You need a product up and running. If you have a (good) HTML/CSS/JS/PHP developer on board who knows Drupal, he can probably get a Drupal+CCK prototype of your customized CMS up and running in a couple weeks, if not days. Who cares if Drupal isn't your long term solution? It just doesn't matter.
- lauken 17y ago
  I am a huge fan of the 37signals content. As opposed to failing fast, we are attempting to do it right quickly. Some failures are the nature of the business but we are doing are best to take all parameters into consideration when making decisions. Thank you very much for your response. We truly appreciate the perspective and reminder that building products for and engaging customers is more important than the framework.
  - bwh2 17y ago
    Glad I can help. Just to be clear about one point: I'm not suggesting that you intentionally fail. Rather, I'm just suggesting you lower the cost of failure.