471,066 Members | 1,177 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,066 software developers and data experts.

The structure of PHP/Web Application coding.

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

Jun 30 '07 #1
3 1643
In article <11**********************@n60g2000hse.googlegroups .com>,
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. <snip>
or am I just
still too new to the game and just need to practise my coding a lot
more?
I think you'll probably find that that *is* the problem.
Experience is a marvellous thing.

Regards
Mark

Jun 30 '07 #2
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.
js*******@attglobal.net
==================
Jun 30 '07 #3
On Sun, 01 Jul 2007 15:46:35 +0000, Peter D. wrote:
I have been looking into a PHP framework called symfony for the last
couple weeks and have been enjoying the learning experience a lot. I
think I just need to look at more code and just read a lot more.
I'm a symfony developer (contractor) in the UK and I'd recommend just
stick with symfony. It's a really great framework once you get used to it
and it can really help keep your code organised.

I'd try to practice refactoring if I were you though (Martin Fowler's book
Refactoring is great) - it can help when you're feeling bogged
down/disorganised to be able to refactor with confidence.

Cheers,
Andy
Jul 6 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

9 posts views Thread by Big Slim | last post: by
4 posts views Thread by Mikkel christensen | last post: by
7 posts views Thread by Brian K. Michalk | last post: by
4 posts views Thread by Aaron Walker | last post: by
2 posts views Thread by lltaylor | last post: by
6 posts views Thread by Laurent | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.