Posted by Jerry Stuckle on 06/30/07 13:38

Peter D. wrote:
> I have been programming PHP for a while now and always seem to run
> into the same problem when working on more than trivial apps. Most of
> my coding is for personal projects anyway so it really isn't a big
> deal but I hopefully plan on doing more serious coding in the future.
>
> My problem is that as I code and the app grows ever larger, I always
> feel like I am digging myself a hole I can't get out of in the end. My
> code is alright, readable and not too bad to debug but I always get
> that feeling like I shoul d be re-considering my design choices now or
> I might really be in trouble later.
>
> Do you guys ever get to that point? If not, how do you avoid it?
>
> I know that with the right amount of planning anything can be
> accomplished in a reasonable amount of code/time. I guess what I
> really want to know is if there is any kind of code strategies that
> work well when designing an application.
>
> I've read a lot about Design Patterns (Factory, AbstractFactory) and I
> just can't seem to think far ahead enough in my code to be able to
> implement these patterns succesfully.
>
> Are there any sites which clearly give examples on how to design
> medium to large applications that are scalable/simple... or am I just
> still too new to the game and just need to practise my coding a lot
> more?
>
> Thanks
>

It takes experience. But a good design is always the best way to go.

Try to design your site and code before you ever start typing. I do it
on every project I work on. Sometimes it's some scratchings on a piece
of paper, for larger projects its more formal. But it really cuts down
on the total project time. I'm only doing things once, not over and
over again.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[Back to original message]