<?xml version="1.0" encoding="UTF-8"?>
			<rss version="2.0"
				xmlns:content="http://purl.org/rss/1.0/modules/content/"
				xmlns:wfw="http://wellformedweb.org/CommentAPI/"
				xmlns:dc="http://purl.org/dc/elements/1.1/"
				xmlns:atom="http://www.w3.org/2005/Atom"
				xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
				xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
				xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
				>

				<channel>
					<title>Matt Walters</title>
					<atom:link href="http://mattwalters.net/rss.xml" rel="self" type="application/rss+xml" />
					<link>http://mattwalters.net</link>
					<description>Senior Web &amp; PHP Developer in Richmond, VA</description>
					<lastBuildDate>Wed, 22 Feb 2012 15:44:47 +0000</lastBuildDate>
					<language>en</language>
					<sy:updatePeriod>hourly</sy:updatePeriod>
					<sy:updateFrequency>1</sy:updateFrequency>
					<generator>markd</generator>
						<item>
							<title>Potluck PHP Framework</title>
							<link>http://mattwalters.net/2012/potluck-php-framework.html</link>
							<pubDate>February 12th, 2012</pubDate>
							<dc:creator>Matt</dc:creator>
							<guid isPermaLink="false">http://mattwalters.net/2012/potluck-php-framework.html</guid>
							<description><![CDATA[<p>In my free time I've been playing around with some different tools for development and I've sort of come up with a Potluck PHP Framework of sorts.  It's actually not bad and stays pretty lightweight while giving some decent functionality.  Keep in mind, I've not spent extensive time with this setup, but I am liking what I'm encountering so far.  Here's what I've pieced together:</p>

<h3><a href="http://www.slimframework.com/">Slim</a>: PHP5 Micro Framework</h3>

<p>It's pretty lightweight and you're not going to find tons of functionality built into it.  But don't let it fool you.  It is pretty easy to extend or build upon and has some important pieces of functionality that a framework should have already built in.</p>

<p>My only "beef" with Slim is probably that it doesn't give a great Controller structure if you're going to take an MVC approach to things.  But I'm still just starting to play with the framework so I might find a way to build in something more like what I'm expecting.  I typically like the CodeIgniter approach on controllers/routes.  I'd like to see if I can figure out a way to minimally recreate that functionality so I can make a new route just by dropping a file/class/method into the appropriate place(s).  For a small site this would be a non-issue anyhow.</p>

<h3><a href="http://twig.sensiolabs.org/">Twig</a>: Template Engine</h3>

<p>This is rather <a href="https://github.com/codeguy/Slim-Extras/blob/master/Views/TwigView.php">easily integrated</a> into Slim and gives you a nice template engine for your views.  I'm typically not a fan of mustache templating systems but Twig is a pretty robust engine.  In my playing around with it, I am finding myself willing to deal with the mustaches in order to gain the advantages Twig is providing.</p>

<h3><a href="http://phpdatamapper.com/">phpDataMapper</a></h3>

<p>phpDataMapper is more or less a port of the <a href="http://datamapper.org/">Ruby DataMapper</a> project.  This is the one I've had the least time spent with of the 3 items on this list.  But I definitely enjoy not having to worry about escaping things for the database, etc., and being able to quickly establish a database back end for the app I'm using this setup with.  I went from no database connection to pulling data out and displaying it on my page in about 5 minutes with phpDataMapper.</p>

<hr />

<p>Could I have done all of this with something like CodeIgniter?  Sure.  I'm a big fan of CodeIgniter so I'm not making this list as an argument against CI or other PHP frameworks.  I will say that I was able to integrate Slim, Twig, and phpDataMapper in about 15 minutes of Googling and typing.</p>

<p>One advantage I could see to using a setup like this is that you get to very explicitly choose where you want to put weight into the framework you're piecing together for your application.  I'm not sure how light-weight Twig and phpDataMapper would be considered, but Slim is definitely light-weight.  Database interactions and rendering are areas that I was ok with adding weight to the application for because of what they provide me.</p>]]></description>
							<content:encoded><![CDATA[<p>In my free time I've been playing around with some different tools for development and I've sort of come up with a Potluck PHP Framework of sorts.  It's actually not bad and stays pretty lightweight while giving some decent functionality.  Keep in mind, I've not spent extensive time with this setup, but I am liking what I'm encountering so far.  Here's what I've pieced together:</p>

<h3><a href="http://www.slimframework.com/">Slim</a>: PHP5 Micro Framework</h3>

<p>It's pretty lightweight and you're not going to find tons of functionality built into it.  But don't let it fool you.  It is pretty easy to extend or build upon and has some important pieces of functionality that a framework should have already built in.</p>

<p>My only "beef" with Slim is probably that it doesn't give a great Controller structure if you're going to take an MVC approach to things.  But I'm still just starting to play with the framework so I might find a way to build in something more like what I'm expecting.  I typically like the CodeIgniter approach on controllers/routes.  I'd like to see if I can figure out a way to minimally recreate that functionality so I can make a new route just by dropping a file/class/method into the appropriate place(s).  For a small site this would be a non-issue anyhow.</p>

<h3><a href="http://twig.sensiolabs.org/">Twig</a>: Template Engine</h3>

<p>This is rather <a href="https://github.com/codeguy/Slim-Extras/blob/master/Views/TwigView.php">easily integrated</a> into Slim and gives you a nice template engine for your views.  I'm typically not a fan of mustache templating systems but Twig is a pretty robust engine.  In my playing around with it, I am finding myself willing to deal with the mustaches in order to gain the advantages Twig is providing.</p>

<h3><a href="http://phpdatamapper.com/">phpDataMapper</a></h3>

<p>phpDataMapper is more or less a port of the <a href="http://datamapper.org/">Ruby DataMapper</a> project.  This is the one I've had the least time spent with of the 3 items on this list.  But I definitely enjoy not having to worry about escaping things for the database, etc., and being able to quickly establish a database back end for the app I'm using this setup with.  I went from no database connection to pulling data out and displaying it on my page in about 5 minutes with phpDataMapper.</p>

<hr />

<p>Could I have done all of this with something like CodeIgniter?  Sure.  I'm a big fan of CodeIgniter so I'm not making this list as an argument against CI or other PHP frameworks.  I will say that I was able to integrate Slim, Twig, and phpDataMapper in about 15 minutes of Googling and typing.</p>

<p>One advantage I could see to using a setup like this is that you get to very explicitly choose where you want to put weight into the framework you're piecing together for your application.  I'm not sure how light-weight Twig and phpDataMapper would be considered, but Slim is definitely light-weight.  Database interactions and rendering are areas that I was ok with adding weight to the application for because of what they provide me.</p>]]></content:encoded>
						</item>
				
						<item>
							<title>Scaling Startups</title>
							<link>http://mattwalters.net/2012/scaling-startups.html</link>
							<pubDate>February 17th, 2012</pubDate>
							<dc:creator>Matt</dc:creator>
							<guid isPermaLink="false">http://mattwalters.net/2012/scaling-startups.html</guid>
							<description><![CDATA[<p>Pretty good article about things over at Etsy.  I particularly liked this quote.</p>

<blockquote>
  <p>If you’re building a technology-driven company, you better have 
  a culture that loves engineers, and I mean love. All too often, 
  I see entrepreneurs who say they "just need engineers" to "bang 
  out the code" for this great idea of theirs. If you view 
  engineers as interchangeable factory workers instead of partners 
  and creative people, you’re in for a tough time getting huge in 
  a world driven by technology.</p>
</blockquote>]]></description>
							<content:encoded><![CDATA[<p>Pretty good article about things over at Etsy.  I particularly liked this quote.</p>

<blockquote>
  <p>If you’re building a technology-driven company, you better have 
  a culture that loves engineers, and I mean love. All too often, 
  I see entrepreneurs who say they "just need engineers" to "bang 
  out the code" for this great idea of theirs. If you view 
  engineers as interchangeable factory workers instead of partners 
  and creative people, you’re in for a tough time getting huge in 
  a world driven by technology.</p>
</blockquote>]]></content:encoded>
						</item>
				
						<item>
							<title>Vagrant and Puppet are pretty fun</title>
							<link>http://mattwalters.net/2012/vagrant-and-puppet-are-pretty-fun.html</link>
							<pubDate>February 10th, 2012</pubDate>
							<dc:creator>Matt</dc:creator>
							<guid isPermaLink="false">http://mattwalters.net/2012/vagrant-and-puppet-are-pretty-fun.html</guid>
							<description><![CDATA[<p>I had some good times with <a href="http://vagrantup.com/">Vagrant</a> and <a href="http://puppetlabs.com/">Puppet</a> this week.  I would easily recommend checking it out if you typically develop <em>for</em> *nix based systems as it can make setting up a local dev environment pretty nice and easy to manage.  Not only that, but you can then share the dev environment with other developers on your team which is great news for folks that play well with others.</p>

<p>You will probably find it to be a bit of a "slow down in order to speed up" routine.  I had previously played with it a little so I was able to dive in pretty fast this time around and found it pretty straight forward after having wrapped my head around it the first time several weeks back.</p>

<p>I originally found out about it by reading the article "<a href="http://phpadvent.org/2011/facilitating-development-environment-consistency-by-jeff-loiselle">Facilitating Development Environment Consistency</a>" over on the <a href="http://phpadvent.org">PHP advent</a> site.  So that might be a good place for you to start if you're interested in the approach.</p>

<p>If you're not already subscribed to PHP Advent or following them on Twitter, I'd highly recommend it.  New articles only come in December of each year but some of them can be pretty stellar.</p>]]></description>
							<content:encoded><![CDATA[<p>I had some good times with <a href="http://vagrantup.com/">Vagrant</a> and <a href="http://puppetlabs.com/">Puppet</a> this week.  I would easily recommend checking it out if you typically develop <em>for</em> *nix based systems as it can make setting up a local dev environment pretty nice and easy to manage.  Not only that, but you can then share the dev environment with other developers on your team which is great news for folks that play well with others.</p>

<p>You will probably find it to be a bit of a "slow down in order to speed up" routine.  I had previously played with it a little so I was able to dive in pretty fast this time around and found it pretty straight forward after having wrapped my head around it the first time several weeks back.</p>

<p>I originally found out about it by reading the article "<a href="http://phpadvent.org/2011/facilitating-development-environment-consistency-by-jeff-loiselle">Facilitating Development Environment Consistency</a>" over on the <a href="http://phpadvent.org">PHP advent</a> site.  So that might be a good place for you to start if you're interested in the approach.</p>

<p>If you're not already subscribed to PHP Advent or following them on Twitter, I'd highly recommend it.  New articles only come in December of each year but some of them can be pretty stellar.</p>]]></content:encoded>
						</item>
				
						<item>
							<title>New job</title>
							<link>http://mattwalters.net/2012/new-job.html</link>
							<pubDate>February 6th, 2012</pubDate>
							<dc:creator>Matt</dc:creator>
							<guid isPermaLink="false">http://mattwalters.net/2012/new-job.html</guid>
							<description><![CDATA[<p>Today I started a new job with <a href="http://www.macrumors.com/">MacRumors</a> where I'll be working on that site and others.</p>

<p>It was a tough decision to leave Snagajob.  I got to do a lot of fun things there and helping folks find jobs definitely felt nice.  I was doing a <strong>lot</strong> of WordPress work there along with a healthy serving of straight up front end web development.  </p>

<p>Those are good lead-in's to what I'm excited about with MacRumors.  I'll still be doing some WordPress work I'm sure, and I'm fairly certain I'll be doing plenty of front end web development as well.  But it also sounds like there will be a good bit of opportunity for me to get back to my roots as a PHP developer.  Rather than working primarily in a niche of PHP (e.g. WordPress), I'll get the opportunity to branch back out into more general PHP applications as well as wear many other hats I'm sure.</p>

<p>So here's to new beginnings and the opportunities they bring.</p>]]></description>
							<content:encoded><![CDATA[<p>Today I started a new job with <a href="http://www.macrumors.com/">MacRumors</a> where I'll be working on that site and others.</p>

<p>It was a tough decision to leave Snagajob.  I got to do a lot of fun things there and helping folks find jobs definitely felt nice.  I was doing a <strong>lot</strong> of WordPress work there along with a healthy serving of straight up front end web development.  </p>

<p>Those are good lead-in's to what I'm excited about with MacRumors.  I'll still be doing some WordPress work I'm sure, and I'm fairly certain I'll be doing plenty of front end web development as well.  But it also sounds like there will be a good bit of opportunity for me to get back to my roots as a PHP developer.  Rather than working primarily in a niche of PHP (e.g. WordPress), I'll get the opportunity to branch back out into more general PHP applications as well as wear many other hats I'm sure.</p>

<p>So here's to new beginnings and the opportunities they bring.</p>]]></content:encoded>
						</item>
				
						<item>
							<title>Scrollorama</title>
							<link>http://mattwalters.net/2012/scrollorama.html</link>
							<pubDate>January 31st, 2012</pubDate>
							<dc:creator>Matt</dc:creator>
							<guid isPermaLink="false">http://mattwalters.net/2012/scrollorama.html</guid>
							<description><![CDATA[<p>If you ever need to do some crazy scrolling affects as the user scrolls down a web page … this is definitely worth checking out.</p>]]></description>
							<content:encoded><![CDATA[<p>If you ever need to do some crazy scrolling affects as the user scrolls down a web page … this is definitely worth checking out.</p>]]></content:encoded>
						</item>
				
				</channel>
			</rss>
