11 ms·

I am sorry, I disagree with >Bug-filled/half implemented seems to be more a comment on programming ability than the decision to write a framework. How you

by mrtron 19y ago

I am sorry, I disagree with >Bug-filled/half implemented seems to be more a comment on programming ability than the decision to write a framework. How you can write a fully featured, bug free framework better than an entire web community? Sure writing your own framework is interesting, but I feel my skills are lesser than a huge community of people working together. A smaller project you would not build a large framework, you would build a tiny subsection of features, however then you cannot easily add caching, internationalization, etc if needed. Many programmers will write their own framework. Most of these programmers will jump on a common framework afterwords. I fully agree with >For fun. To learn a new language. Because you have a new idea to explore.

axod 19y ago
"How you can write a fully featured, bug free framework better than an entire web community?" How can a small startup team write software better than an entire corporation? Sorry, but bigger+more developers isn't necessarily better.
- mrtron 19y ago
  >How can a small startup team write software better than an entire corporation? Sorry, but bigger+more developers isn't necessarily better. In a startup I would suggest your efforts would be better working on your core competency. For many people, publishing to the web is just a tiny piece of their startup.
bsaunder 19y ago
I think to be one of the principle developers at a start-up, you need to do better than feeling like your "skills are lesser than a huge community of people working together". IMHO, the two/three primary developers at a start-up should be able to code up a new framework that better meets their needs (though possibly less total features) in less time and with fewer bugs than a huge community. It shouldn't even be a close race. Also, by developing their own framework they will know exactly what parts suck and still need work and be better able to support it at launch.
- mrtron 19y ago
  Sure, but what if publishing to the web is about ~10% of your business, and not your competitive advantage? Do you really want your primary developers coding up a new framework?

by mrtron 19y ago

axod 19y ago

"How you can write a fully featured, bug free framework better than an entire web community?" How can a small startup team write software better than an entire corporation? Sorry, but bigger+more developers isn't necessarily better.

mrtron 19y ago
>How can a small startup team write software better than an entire corporation? Sorry, but bigger+more developers isn't necessarily better. In a startup I would suggest your efforts would be better working on your core competency. For many people, publishing to the web is just a tiny piece of their startup.

bsaunder 19y ago

I think to be one of the principle developers at a start-up, you need to do better than feeling like your "skills are lesser than a huge community of people working together". IMHO, the two/three primary developers at a start-up should be able to code up a new framework that better meets their needs (though possibly less total features) in less time and with fewer bugs than a huge community. It shouldn't even be a close race. Also, by developing their own framework they will know exactly what parts suck and still need work and be better able to support it at launch.

mrtron 19y ago
Sure, but what if publishing to the web is about ~10% of your business, and not your competitive advantage? Do you really want your primary developers coding up a new framework?