<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Mon, 21 May 2012 07:58:12 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Mike Bernat's Blog: How Do GOOD Developers Ask Questions?]]></title>
      <guid>http://www.phpdeveloper.org/news/13355</guid>
      <link>http://www.phpdeveloper.org/news/13355</link>
      <description><![CDATA[<p>
<i>Mike Bernat</i> has <a href="http://www.mikebernat.com/blog/How_Do_GOOD_Developers_Ask_Questions?">a new post</a> that anyone, experienced or not in the development world, should read. The post is a good overview of how good developers (ones who really want a genuine answer and aren't just being lazy) should ask questions.
</p>
<blockquote>
First of all, let me say this. If you consider yourself a developer and don't find yourself wanting to ask questions on a daily basis, you're doing something wrong. Asking questions without being afraid of humiliating yourself is critical. 
</blockquote>
<p>
His suggestions include not being afraid to over-describe the problem, speculate on what the possible answer might be (it can help to get the thoughts flowing), providing some examples of the problem you're facing and, most importantly, don't get offended by the responses you get. Sure, some might be blatantly insulting but those aren't worth the read anyway. Find value in the answers that can help, though - no matter how simplistic the advice seems.
</p>]]></description>
      <pubDate>Thu, 08 Oct 2009 08:25:06 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Chris Shiflett's Blog: Ask Chris Is Back]]></title>
      <guid>http://www.phpdeveloper.org/news/4900</guid>
      <link>http://www.phpdeveloper.org/news/4900</link>
      <description><![CDATA[As noted in <a href="http://shiflett.org/archive/203">his latest blog entry</a>, <i>Chris Shiflett</i> and the Pro::PHP podcast are again collaborating to bring the listening community more "Ask Chris" shows.
<p>
<quote>
<i>
It's been a few months since <a href="http://shiflett.org/archive/133">Episode One</a>, but thanks to <a href="http://marcuswhitney.com/">Marcus</a>, <a href="http://shiflett.org/archive/131">Ask Chris</a> is back <a href="http://podcast.phparch.com/podcast/audio/20060224.mp3">on the air</a>. The format is a bit different - instead of doing separate shows, we'll be doing a short segment at the end of each interview.
<p>
<a href="http://podcast.phparch.com/podcast/audio/20060224.mp3">This interview</a> is with <a href="http://www.sklar.com/blog/">David Sklar</a> of <a href="http://www.ning.com/">Ning</a>. He and Marcus discuss Ning, of course, but David also provides some good perspective on the state of technology and how the definition of a programmer is becoming more and more inclusive.
<p>
This episode of Ask Chris is about email injection, a topic of growing concern for PHP developers. 
</i>
</quote>
<p>
You can find out more about this addition to the Pro::PHP lineup and how to subscribe to the podcast over on <a href="http://podcast.phparch.com">their site</a>.]]></description>
      <pubDate>Mon, 27 Feb 2006 08:20:25 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Chris Shiflett's Blog: Pro PHP Podcast]]></title>
      <guid>http://www.phpdeveloper.org/news/4687</guid>
      <link>http://www.phpdeveloper.org/news/4687</link>
      <description><![CDATA[<i>Chris Shiflett</i> has <a href="http://shiflett.org/archive/182">this post</a> today about the partnership between php|architect and the Pro PHP Podcast.
<p>
<quote>
<i>
You've probably heard the <a href="http://www.marcuswhitney.com/?p=34">good news</a> about the <a href="http://podcast.phparch.com/">Pro PHP Podcast</a>. The guys behind the show (<a href="http://marcuswhitney.com/">Marcus Whitney</a> and <a href="http://blog.phpdeveloper.org/">Chris Cornutt</a>) are joining forces with <a href="http://phparch.com/">php|architect</a> in what should be a good thing for all of us.
<p>
So, I was very happy to hear about the partnership with php|architect, because I know this will let Marcus focus on the show. There are also regular newscasts planned, and Chris is asking, <a href="http://blog.phpdeveloper.org/?p=27">What do you want out of your news</a>?
</i>
</quote>
<p>
Always good to see community support behind a project...and remember, the first show of this new partnership is happening January 27th, an interview with Andi Gutmans that will be broadcast live. <a href="http://www.phparch.com/shop_product.php?itemid=106">Click here</a> to sign up...]]></description>
      <pubDate>Thu, 19 Jan 2006 06:38:32 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[MetaFilter.com: Looking for a Secure PHP Mailer...]]></title>
      <guid>http://www.phpdeveloper.org/news/4325</guid>
      <link>http://www.phpdeveloper.org/news/4325</link>
      <description><![CDATA[On the ever-popular site <a href="http://www.metafilter.com">MetaFilter.com</a>, there's <a href="http://ask.metafilter.com/mefi/27356">this new post</a> in their "Ask MetaFilter" section from someone looking for a secure PHP-based email script.
<p>
<quote>
<i>
I need a PHP-based email script that will take the name, email, subject, and message form fields I pass to it and send them to me with the name and email used as the "From" field in the message header. I also need to put a value in the header that identifies the sender's IP address. And, of course, I need a script that is not vulnerable to header injection spam attacks. Any recommendations?
</i>
</quote>
<p>
So far, <a href="http://ask.metafilter.com/mefi/27356">the comments</a> have ranged anywhere from "just use mail()" to <a href="http://phpmailer.sourceforge.net/">PHPMailer</a>. What do you think? Have an opinion on what would make for a good secure mailer for a PHP application?]]></description>
      <pubDate>Thu, 17 Nov 2005 06:21:39 -0600</pubDate>
    </item>
  </channel>
</rss>

