Top improvements for PHP developers
jeremyhutchings.com
Top improvements for PHP developers
1–7 of 7 posts
Re: Top improvements for PHP developers
#2I like the points about using php for logic instead of mysql, I've been doing that for years because I prefer to always do the heavy lifting in php which I know better than SQL.
I always felt it was against best practices though, but now I won't worry about it so much.
Re: Top improvements for PHP developers
#3I like the points about using php for logic instead of mysql, I've been doing that for years because I prefer to always do the heavy lifting in php which I know better than SQL. I always felt it was against best practices though, but now I won't worry about it so much.
One of the PHP devs who is also at Facebook suggested I do it that way, so I don't worry too much either!
Re: Top improvements for PHP developers
#4[deleted]
Re: Top improvements for PHP developers
#5While interesting, if you haven't read the original article, most of the points lose their meaning.
http://blogs.sitepoint.com/2010/11/19/mysql-mistakes-php-dev...
Also, aren't most PHPers using frameworks (like CakePHP or Symphony) now instead of raw-coding PHP? I can imagine this being useful for dealing with small or legacy systems, but I haven't had to write a raw SQL statement in almost a year now.
Re: Top improvements for PHP developers
#6[deleted]
Re: Top improvements for PHP developers
#7While interesting, if you haven't read the original article, most of the points lose their meaning. http://blogs.sitepoint.com/2010/11/19/mysql-mistakes-php-dev... Also, aren't most PHPers using frameworks (like CakePHP or Symphony) now instead of raw-coding PHP? I can imagine this being useful for dealing with small or legacy systems, but I haven't had to write a raw SQL statement in almost a year now.
Indeed, most of the time I use codeigniter, though I was focusing on "where" you do the logic, opposed to just how.