I would say the reverse is true, that it's only after you have worked your way through building your own framework (or two) that you appreciate the structure and power that a framework can give you. I can only speak for myself but I wouldn't have known how to figure out why and how a framework behaves like it does as a novice developer.
Robin -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Berend de Boer Sent: 30 November 2010 09:59 To: [email protected] Subject: Re: [phpug] Cribz Network >>>>> "Robin" == Robin <[email protected]> writes: Robin> Hi, I agree with Harvey about the spelling and grammar Robin> being pretty bad (although my England isn't the best), but Robin> I would say that as you are new to php and you want to get Robin> your hands dirty on a project that I presume you care about Robin> and that you are using this as a vehicle to learn and Robin> experiment on, then this is a great way to do it. Don’t Robin> expect anyone else to care about it as much as you do. I Robin> haven't looked at the code yet but, good on ya!. Wouldn't it be more helpful to get to know an existing framework really well, and only then make another one? Else it will be the usual stuff from 25 years ago, full of security holes, missing things that everyone takes for granted, etc. Only when you know certain frameworks really well, you know enough to write something better. -- All the best, Berend de Boer -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
