Re: This Mailing List Isn't on Google For No Reason

Tue, 24 Oct 2006 13:57:55 -0700

as a distinctly average php user and a newcomer to cake i'll add my thoughts here for what it's worth.

The fact that Cake is (or can be) such a powerful framework is a double-edged sword - serious developers use it to solve common problems quickly and speed up development of complex apps

but 'newbies' are probably seeing the hype and thinking it's a short-cut to actually putting in the time to learn PHP - it's getting seen as quicker to learn Cake then to actually understand the fundamentals of creating a database connection or knowing the ins and outs of the MVC model.

IMO that's why there are so many 'newbie' php questions and a lack of searching for questions that have been asked again and again.

I think most people who post these 'simple' question have searched but just maybe done searches for a couple of simple keywords and phrases, haven't found the answer they want in the first two or three results of each search so they post a question.

If a set of FAQs is relevant, evolves with the community and is kept updated then it's never a waste of time. I'd strongly suggest that it includes sample code cause otherwise there'll be a load of posts on the group that begin 'i saw this in the faq but how do i actually use it in my app?'

just my 2p... but it seems like something needs to be done to prevent the problem that's been identified from getting out of hand and swamping the group on google.

T

On 10/24/06, Mikee Freedom <[EMAIL PROTECTED]> wrote:

morning all,

just thought i would chime in with my 2.

i agree, there are a lot of beginners about the place.

at one stage being a Cake newbie myself, it has only been through
serious time dedicated have I managed to come out with what I think to
be a pretty good application utilising *some* of the finer points of
CakePHP.

along the way there were a lot of occasions where I didn't know which
direction to choose and found myself procrastinating about a decision
due to a simple lack of knowledge about either MVC or Cake itself.

I have found great assistance in:

1. the manual
2. the wiki (and now the bakery)
3. the various blogs around (thanks fellas)
4. searching google groups
5. the source code
6. the api
7. asking questions in here

roughly in that order.

i think either a faq, or a seperate category in the bakery for 'The
Basics' would be very beneficial.

In a nutshell, i've managed to find my way around using the current
resources. however an area where these basic questions were answered
would be wonderful. every time a question continues to arise in the
groups it would be nice to record it somewhere else in a tagged (and
possibly categorised) trouble shooting or faq section.

doesn't have to be one of the fellas who adds it, i'm sure any of us
can summarise the email thread and include the content in the right
place.

just some thoughts,
mikee

On 25/10/06, kiper < [EMAIL PROTECTED]> wrote:
>
> > Praise the powers that be, the wiki is dead. I suppose I could start
> > a page on the manual that only features FAQs. Anyone want to help on
> > that?
>
> I'll gladly help you with that, John, if you're interested! Still feel
> like a blueberry but I've been around since July :)
>
> I think that the manual and the api are ample information for the
> beginner and the Bakery is shaping up nicely.
>
> Maybe the problem is, as Nate says, that there are too many beginners
> that haven't got a clue about programming, PHP or MySQL. So, a FAQ that
> points them in the right direction and gives them examples of what the
> Cake Foundation think is "good" coding if you're going to work with
> CakePHP, seems like a very good idea.
>
>
> >
>


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cake-php
-~----------~----~----~----~------~----~------~--~---

Reply via email to