Wow, every day we learn something new so It seems like I'll never run out of material for my list of commandments! Here's the continuation of my previous list, it's important to point out that some of these might not be valid for future releases but people should be careful for now when dealing with some of the current limits. So here we go... Thou shall not: Assume that standard objects in destination orgs don't have any validation rules/trigger logic that will cause your package's test units to fail, place your catch blocks and take actions accordingly Assume your custom settings will be initialized when running test units in a destination org , make sure you validate null values or set the values for custom settings Give end-users credentials to test your app and go on vacation leaving the user wondering what the heck is a verification code. Make sure you change the f$!@#%^ email address! Leave out apex:pageMessages component from your VF page to display

I've been working a lot with rails and force.com during the last months, rails is awesome however getting all of the plumbing to work is a real pain. I'm working on a template app that might be helpful for anyone that's trying to build a rails app that interacts with force.com. This app template uses: Databasedotcom gem Bootstrap framework Application template Basic chatter components (more info below) I decided to use cells for creating reusable components and it's looking very promising. I created a few chatter-related components and got it to a point were the following code: Renders the following page: I'm no expert in ruby or rails so I hope that with the help of other developers we can improve the template and expand the components library. Also, i'm planning to provide some libraries to access the metadata api from ruby but this is still a work in progress. You can checkout the github project here .