Salesforce

We are terminal junkies at CloudSpokes so we were really excited when the Force.com CLI was announced. One of our favorite command line tools is .jq, a lightweight and flexible command-line JSON processor. My buddy and terminal Yoda, Kyle Bowerman, turned me on

For the past few years, the salesforce.com mantra has been “Chatter”. Everything was Chatter and everything connected to Chatter. Chatter was the way, the truth and the life. If you’ve been watching salesforce.com recently you may have noticed a lot of

Busy, busy week right before Dreamforce! With our acquisition of TopCoder, the CloudSpokes team is part of the TopCoder Open (TCO), an annual event which features algorithm, design, and development competitions in a tournament format. We've brought in nearly 125 of the best developers

Docker is an open-source engine that automates the deployment of any application as a lightweight, portable, self-sufficient container that will run virtually anywhere. The great thing about these containers is that they encapsulate any payload and runtime dependencies, and will run consistently on and

I spent the better part of two days early this month hanging out with Pat Patterson at the Monktoberfest conference talking about beer, technology and kids. If you don't know Pat Patterson, I highly encourage you to find him at Dreamforce this year (you

At CloudSpokes.com we wrap a lot of the challenge process functionality into Chatter. So when we started to add more functionality to our site and org we naturally wanted to leverage the new Chatter in Apex functionality. However, it was a little more

I love APIs. I love to build them, cURL them, read their source code and talk about them. One of the aspects that I haven't loved so much is debugging them. That is until I found Runscope. We've been using the service for a

Fun stuff coming out of Salesforce as we ramp up to Dreamforce! I had the opportunity to sit in on the "Intro to Aura" webinar a few hours ago and I thought I would blog on some key points that I came

Logging in Force.com can be somewhat of a challenge. Since there's no log file you can write to, we need to develop another mechanism to record events and exceptions that we can inspect later. Sending emails with exceptions information is fine, but it

Roughly two years ago we wrote our CloudSpokes API on the Force.com platform. It’s evolved of course and the current version is a Ruby application that proxies calls to Force.com via Apex REST Services. Recently we’ve had a number of

Salesforce Junction objects are a convenient way to create a many-to-many relationship in your data model. Accourding to the docs, a many-to-many relationship allows each record of one object to be linked to multiple records from another object and vice versa. For example, you

I just published a port of my Forcifier Ruby gem to Node.js. You can find the package on npm and the source on github. So why should you use forcifier for your Node.js application? Well, if you are using the awesome nforce

The Summer '13 release for Salesforce.com included an awesome feature that many developers were clamoring for. When refreshing a sandbox, the platform (pre-Summer 13) simply copied the metadata for custom settings. With Summer '13 you also got the data! I just refreshed one

First of all I love asynchronously processing in Salesfoce. We use it all the time at CloudSpokes. I don't actually mean that the @future annotation should die, per se, but I think there is a better approach. I see the annotation rising from the

It's an understatement to say that I'm a fan of Code School. I love the way they've blended professional video screen casts, live coding in the browser, and gamification to make learning fun again. The music is a little campy sometimes but overall I'm

Continuous Integration (CI) for Force.com projects has been a popular topic lately. There are a number of blog post that describe the benefits and how you should go about doing it. However, after we discussed it on our #DifferentSpokes podcast last week, we

So I ran across this issue a couple of months ago and forgot to blog about it for my reference and anyone else that runs across this problem. So here's the issue, I have an Apex class scheduled in production that runs another Apex