A Few Tips on Getting Started with

Mar 9, 2013 | 2 minutes read

Today I got the opportunity to attend a “hack day” in San Francisco. Quite fun, and I learned a lot from Adam Seligman, Dave Carroll, Pat Patterson, and Akhilesh Gupta. This is a great team: extremely personable, clearly excited about their platform and the technology, and willing to pull up their sleeves and write some code. My kind of people.

During the hack day I acquired a few tips for getting started. Nothing earthshattering but useful nonetheless.

  1. Setup a developer account. It’s quick, easy, and free. You can get a lot of them.

  2. Don’t use your production account for development. This may sound trite but I can tell you from first-hand experience that you don’t want to start hacking in production. The development lifecycle has process for deploying from one environment to another. Use it. Today I didn’t follow this advice and it cost me quite a bit of time. See tip #1 for getting a proper developer account.

  3. Simplify the password requirements for your developer account. First, under your name, choose Setup.


    Then type “password” in the search box and click Password Policies.


    Choose some less restrictive policies. It’s up to you – personally, I don’t want my developer account password expiring all the time. Note: I do not recommend you do this on your production account.


  4. Change the default IP Restrictions. Again, for my developer account, I don’t want the platform continually challenging me if I log in from different places. After you browse to Setup search for Profile. Click on Profiles.


    Scroll down until your see System Administrators and select it.


    Scroll down to IP Address Ranges and click New. Enter default ranges to and click Save.


That’s all for now. For those of you who are pro’s on the platform this is likely not new or exciting. I’m sure there are more tips I’ll learn over time and, when I do, I’ll try to update this list.

I hope this helps!

comments powered by Disqus