|
|
Posted by NC on 10/12/05 21:49
Nikolas Hagelstein wrote:
>
> i spend a lot of time on thinking and researching about how to
> make developing webapplications with php a more structured/systematic
> thing.
Why stop at development? Or, rather, why start in development?
Structure and system should be first introduced in sales and
implementation...
> Anyway my current attitude is that fullfilling the following
> needs would make application depvelopment via PHP a really
> fast/professional/structured thing:
>
> - An MVC -architecture framework (e.g MOJAVI)
> - template parser (for View part)
> - severall helper toolkits/frameworks
> (DB abstraction layer/Form validation etc.)
> - disciplined/skilled Devloper ;)
I respectfully disgree. No matter how professional your
development is, your success will NOT be determined by the
quality of development. Whether or not your product uses MVC
(or another fashionable development technique) is of no
consequence to the buyer. The buyer wants to see the relevant
feature set (which is a design issue, ultimately rooted in
marketing), reasonable cost of ownership (which a purely
marketing issue), knowledgeable sales people and responsive
implementation people (which are human resources issues).
On the development side, what you really need is a combination
of coding AND DOCUMENTING guidelines with a code repository and
a defect tracking system. Over time, this will ensure you have
a large base of potentially reusable and reasonably bug-free code.
Whether you want to introduce guidelines that require the use of
MVC or, say, forbid the use of OOP altogether, is a matter of
secondary importance...
> Wouldn't it be nice to have something like the
> "PHP professional webapplication development guidline" ?
> containing:
> - toolkits/frameworks
> - techniques
> - tutorials etc.
I think it's called PEAR; it includes code repository (complete
with dependency checks and defect tracking) and coding guidelines...
Cheers,
NC
Navigation:
[Reply to this message]
|