Re: [Phpwebsite-developers] Module Substitution

[Geoff S. <ge...@ge...>]

Adam:

As someone who has programmed in God-only-knows how many languages over the 
last 30 years, I can tell you that phpWebSite will die a slow and agonizing 
death unless you maintain architectural and programming standards. Here's why:

As a system ages, bugs are fixed, features are added, and things are 
changed for dozens of reasons. If the work is simply done to meet a 
deadline without any real thought to architecture and standards, eventually 
(and I guarantee this will happen) the code becomes so patched and so 
unwieldy and so tied-in-together weird ways that no one actually knows how 
the code really works and changing one thing will break another seemingly 
unrelated thing. Programmers make it even worse by changing code that looks 
like it should have something to with what they are working on for extra 
insurance. At this point, you can only program the system by folklore and 
eventually you have to do a complete re-write of the system because it is 
so cumbersome, nothing can be done.

So, when folks complain about you pushing them on standards and 
architecture, tell them to shut their traps and get back to work!

By the way, this usually works: "OK, you can code this any way you want as 
long as you agree to be available 24 hours a day 7 days a week for as long 
as your code is part of this system." (That's not really a good bargain for 
you because the code usually affect other areas of the system as well.)

Geoff

At 08:25 PM 12/31/2002 -0500, ad...@tu... wrote:
>Doh!  I guess I missed this before I posted my last mail.  I like this
>idea, especially the part about "Continues to reflect architecture and
>coding standards".  I'm sure the guys hate me sometimes since I'm kind of
>the defacto standards and structure dude and I get onto peeps about their
>code.
>User interface can be flexible as far as how it looks since all modules in
>the future should template ALL their output.  This will allow admins, or
>Phil :), to setup their user interfaces anyway they wish ().
>
>+1 from me Geoff
>
>Adam
>
> > Also, if the module becomes part of the distribution, then the in-house
> > developer is de facto responsible for it even if the original developer
> > is  still involved. The in-house developer takes on responsibility to
> > insure  that the module:
> >
> > 1. Continues to reflect architecture and coding standards.
> > 2. Maintains consistent user interface.
> > 3. Enhancements meet the approval of the in-house team.
> >
> > Seems to me there ought to be three levels of module:
> >
> > 1. Those developed in-house or "taken over" as part of the distro. 2.
> > Those that meet  a certification standard and are considered "official"
> > modules developed by a third-party.
> > 3. Those that work with phpWebsite but which have not been reviewed and
> > approved.
> >
> > Geoff
> > www.hostricity.com
> >
> >
> > At 01:46 PM 12/28/2002 -0500, Matthew McNaney wrote:
> >>This is not in direct response to Eloi's new module (good job btw) but
> >> just a question that needs consideration for the future.
> >>
> >>Suppose someone creates a better content module than one produced
> >> in-house. I know that many of the developers here have several things
> >> going on at one time (I can think of two huge ones off the top of my
> >> head). Perhaps, if an outside developer is willing, we could ask if
> >> they would like their module to become part of our distro.
> >>
> >>Here is the rub though.
> >>- We would all need to agree it should be done.
> >>- The in house developer would need to agree
> >>- The outside developer would have to guarantee support.
> >>
> >>Again, this may not come up, but I know that there are some modules we
> >> are working on that might have a more dedicated developer outside the
> >> unversity.
> >>
> >>Please discuss with pros and cons for both sides.
> >>
> >>Matt
> >>--
> >>Matthew McNaney
> >>Internet Systems Architect
> >>Electronic Student Services
> >>Appalachian State University
> >>Phone: 828-262-6493
> >>phpwebsite.appstate.edu
> >>ess.appstate.edu
> >>
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>This sf.net email is sponsored by:ThinkGeek
> >>Welcome to geek heaven.
> >>http://thinkgeek.com/sf
> >>_______________________________________________
> >>Phpwebsite-developers mailing list
> >>Php...@li...
> >>https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Phpwebsite-developers mailing list
> > Php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>
>---------------------------------------------------------------------
>Adam Morton
>Developer - Electronic Student Services
>http://phpwebsite.appstate.edu
>Founder - Appalachian Linux Users Group
>http://alug.appstate.edu
>
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Phpwebsite-developers mailing list
>Php...@li...
>https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers