<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: SalesForce Development ARGH!</title>
	<atom:link href="http://www.preludeinteractive.com/2009/01/salesforce-development-argh/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.preludeinteractive.com/2009/01/salesforce-development-argh/</link>
	<description>Nonprofit technology in the trenches</description>
	<lastBuildDate>Mon, 09 Aug 2010 20:31:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Chris</title>
		<link>http://www.preludeinteractive.com/2009/01/salesforce-development-argh/comment-page-1/#comment-159</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 28 Jul 2009 02:45:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.preludeinteractive.com/?p=102#comment-159</guid>
		<description>If you think this is difficult, wait until you encounter the &quot;governor&quot; in apex (see http://www.salesforce.com/us/developer/docs/apexcode/Content/apex_gov_limits.htm).  That&#039;s my nightmare.  Again, I don&#039;t think evil was SFDC&#039;s intent, but the end result of the governor&#039;s draconian enforcement methodology is pure evil.  There are many other nightmares, like table relationships limiting out at one level, unique keys restricted to one field, and so on.

When I see the circle/slash/software logo, I often think it symbolizes how difficult they make life for those who have to write software for their platform.</description>
		<content:encoded><![CDATA[<p>If you think this is difficult, wait until you encounter the &#8220;governor&#8221; in apex (see <a href="http://www.salesforce.com/us/developer/docs/apexcode/Content/apex_gov_limits.htm)" rel="nofollow">http://www.salesforce.com/us/developer/docs/apexcode/Content/apex_gov_limits.htm)</a>.  That&#8217;s my nightmare.  Again, I don&#8217;t think evil was SFDC&#8217;s intent, but the end result of the governor&#8217;s draconian enforcement methodology is pure evil.  There are many other nightmares, like table relationships limiting out at one level, unique keys restricted to one field, and so on.</p>
<p>When I see the circle/slash/software logo, I often think it symbolizes how difficult they make life for those who have to write software for their platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Kraybill</title>
		<link>http://www.preludeinteractive.com/2009/01/salesforce-development-argh/comment-page-1/#comment-11</link>
		<dc:creator>Jeremy Kraybill</dc:creator>
		<pubDate>Tue, 13 Jan 2009 05:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.preludeinteractive.com/?p=102#comment-11</guid>
		<description>Hard to tell without seeing your controller code if this would work, but did you try the with sharing option on your controller? I have used that in several places to get SF to enforce current user permissions for querying etc.</description>
		<content:encoded><![CDATA[<p>Hard to tell without seeing your controller code if this would work, but did you try the with sharing option on your controller? I have used that in several places to get SF to enforce current user permissions for querying etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ehren</title>
		<link>http://www.preludeinteractive.com/2009/01/salesforce-development-argh/comment-page-1/#comment-8</link>
		<dc:creator>Ehren</dc:creator>
		<pubDate>Mon, 12 Jan 2009 20:33:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.preludeinteractive.com/?p=102#comment-8</guid>
		<description>No, I haven&#039;t actually used the API.  I suppose I should bias my expectations by what I&#039;ve found in other parts of the platform.  

I guess what it comes down to is that if I had an open development environment, I could code around these problems, but I would also have a lot more total code to write (and make my own mistakes with).</description>
		<content:encoded><![CDATA[<p>No, I haven&#8217;t actually used the API.  I suppose I should bias my expectations by what I&#8217;ve found in other parts of the platform.  </p>
<p>I guess what it comes down to is that if I had an open development environment, I could code around these problems, but I would also have a lot more total code to write (and make my own mistakes with).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AT</title>
		<link>http://www.preludeinteractive.com/2009/01/salesforce-development-argh/comment-page-1/#comment-7</link>
		<dc:creator>AT</dc:creator>
		<pubDate>Mon, 12 Jan 2009 17:00:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.preludeinteractive.com/?p=102#comment-7</guid>
		<description>Not sure if you have done any SF API development. That too is very &quot;obtuse&quot; especially when there are no simple interfaces (i.e. REST or JSON, etc). SOAP is really unclean and not necessary at all as the one and only SF interface! 

I&#039;ve been wondering why the technical team at SF made some of these choices. They appear to really know what they are doing when you look, as you alluded, to how complex that whole thing is to run, maintain, and grow.</description>
		<content:encoded><![CDATA[<p>Not sure if you have done any SF API development. That too is very &#8220;obtuse&#8221; especially when there are no simple interfaces (i.e. REST or JSON, etc). SOAP is really unclean and not necessary at all as the one and only SF interface! </p>
<p>I&#8217;ve been wondering why the technical team at SF made some of these choices. They appear to really know what they are doing when you look, as you alluded, to how complex that whole thing is to run, maintain, and grow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SalesForce Development ARGH! &#124; PHP-Blog.com</title>
		<link>http://www.preludeinteractive.com/2009/01/salesforce-development-argh/comment-page-1/#comment-6</link>
		<dc:creator>SalesForce Development ARGH! &#124; PHP-Blog.com</dc:creator>
		<pubDate>Mon, 12 Jan 2009 11:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.preludeinteractive.com/?p=102#comment-6</guid>
		<description>[...] is the original: SalesForce Development ARGH!     Related ArticlesBookmarksTags      PHP Development Tools - Keeping it Simple and Mostly Fre If [...]</description>
		<content:encoded><![CDATA[<p>[...] is the original: SalesForce Development ARGH!     Related ArticlesBookmarksTags      PHP Development Tools &#8211; Keeping it Simple and Mostly Fre If [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
